Re: [PythonReports-users] Suggestion for PythonReport.editor.editor

[alexander s. <al...@go...>]

On 05.12.2012 12:22, Werner F. Bruhin wrote:
>
> Following are things I notice
>
> - "Code completion" on the "expr" field to help not making stupid typos,
> e.g. I need the field "drinkinfo.name" for one field
> - if above is to much work/problem maybe use a different shell - e.g.
> PyCrust 0.9.8 - The Flakiest Python Shell which is part of the wx
> distribution, so one would get code completion on the following.
>
> - show the template file name in the title bar
> - or maybe show the template file name in a tab and allow working on
> multiple template files - I know I am pushing it:-)
> - a way to run/preview the report from within the designer
> - Persist the layout of the editor window(s) - so on next startup one
> does have to e.g. enlarge the properties section (wx.lib.agw.persist
> might be useful for this)
> - Have a Save-as and a Save option, the later should not always ask for
> the template name
> - Tooltips for the properties, in a way that it does not disturb using
> the properties editor (maybe a wx.lib.supertooltip over the layout when
> working in the property editor)

I welcome patches implementing whatever feature you find useful.  Even 
if your patch does not find it's way to the mainline sources, ir really 
helps to have a starting point to design a new feature.

I doubt I'd like to have PyCrust instead of plain shell, though.  I 
think the PyCrust notebook would eat up quite a bit of the screen space, 
and we don't have too much of that.

There is report preview feature in the Tk-based template editor.

> Using the sakila template to get a better idea what needs to go where.

Please be aware that the sample data file contains a lot of records.  In 
order to play with template, it is better to use a smaller set.  For 
example,

>>> from sakila import load
>>> data = load()[:200]

> Do I need to do an install/setup of PythonReport if I like to use rev
> 225?  Or can I just do a checkout?

For a playground, you could just add the checkout directory to the 
PYTHONPATH environment variable.  For production use, you'd better 
execute python setup.py bdist_wininst, and then run the installer to add 
the package to your system.  (I assume you are on Windows because there 
are Windows paths in your tracebacks.)

Best wishes,
alex.