Re: [PythonReports-users] Future of PythonReports

[Werner F. B. <wer...@fr...>]

On 06/12/2012 09:48, alexander smishlajev wrote:
> On 05.12.2012 22:08, Werner F. Bruhin wrote:
>> What are your dev plans for PythonReports over the next few month - if any?
> Well, I'm about to start using PythonReports in a new project; perhaps
> that will result in some changes caused by new uses.  Version 0.6.1,
> which I plan to release really soon, would add new variable calculation
> methods "list", "set", and "chain" and support for PDF encription along
> with some rendering and compatibility fixes.
>
> Aside from that, there are no distinct plans.  Features I'd like to see
> include:
>
> - Standalone Windows binary+installer for wx-based editor that would
> allow template editing on pythonless machines.
Wouldn't the Editor need quit a bit of work before this would be useful? 
E.g. support for things like "font", "style", "group" (and others I 
haven't noticed that they are not yet supported).
>
> - HTML rendering.
I guess this would be really useful when used with web frameworks such 
as Django/Turbogears and co
>
> - Front end for DB API + PythonReprorts that would provide database
> reporting functionality found in products similar to PythonReports.
>
> - Outline tags to compose a table of contents for a report.
>
> I plan to work on that binary when I get some tuits, but it is unlikely
> that I will start implementing any other features of this list.
>
>> What are your plans with the two designers will you continue developing
>> both or .....?
> As for me, I like Tk-based designer for template debugging and preview.
>    I use simple text editor to write templates.  The WISIWYG editor was
> meant for people coming from such platforms as FoxPro, MS Access, or
> CrystalReports.  The idea was mine, but author of the UI design and
> editor code is Den Paltov.
I am coming from ReportManager and a long time ago R&R (which we used in 
hotels as the reporting tool (dbase/clipper - Fidelio) and I use the 
first for my shareware.  I have a few users who like to tweak the 
provided reports and for this a nice WISIWYG (or close) editor is just a 
must.

I like to move away from ReportManager as it is really only Windows and 
having something Python/wxPython based is very attrative for me as my 
app is done in wxPython.

If it would support all elements (font, style, group ...) then I am not 
even sure if a true Preview is that much needed, one could also just 
start a "wxprint" type script from within the designer which asks for 
the data and generates a PDF and then use the users preferred PDF viewer.

Hope that Dan will find some time to keep working on it.
>
>> Is there somewhere a list of mandatory elements?
> I don't believe there are mandatory elements other than the detail
> section (and parent elements for it: layout and report).
I looked again, the elements causing problem related to the "font" and 
"style" element, they are not created by the wx editor, nor shown if one 
loads a tk editor created template.
>
> Mandatory attributes should all be marked as such in the documentation,
> http://pythonreports.sourceforge.net/prt.shtml
Noticed those about half an hour after this - thanks.

Werner