[PythonReports-users] Suggestion for PythonReport.editor.editor
Brought to you by:
a1s
From: Werner F. B. <wer...@fr...> - 2012-12-05 10:20:54
|
Hi Alex, I am using it with wxPython 2.8, at least for the next few days to get more familiar with it. 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. >>> data [Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None), Cellarbook(storagelocation=None)] >>> data[0].drinkinfo.name u'Goldwater Esslin' - 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) Using the sakila template to get a better idea what needs to go where. Do I need to do an install/setup of PythonReport if I like to use rev 225? Or can I just do a checkout? Best regards Werner |