pythonreports-users

[PythonReports-users] Future of PythonReports

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

Hi Alex,

What are your dev plans for PythonReports over the next few month - if any?

What are your plans with the two designers will you continue developing 
both or .....?

Is there somewhere a list of mandatory elements?  I started doing a 
report (in the wx designer) and then tried to open it in the Tk one and 
got an error, then some others when trying to preview my report in the 
Tk designer (after I manually added what was missing).

Maybe a "New Template" could be changed so that all the mandatory 
elements are created.

I like the wx designer better, so I hope that is the "future" and if yes 
I will try and have ago and doing the change to allow to "Insert", 
"Delete" elements and maybe also to move them, unless someone is already 
working on this.

Before I start with this I am going to work on a simple report over the 
next few days when I have time and use data produced by a SQLAlchemy 
query - this is also kind of a show stopper for me.

Again thanks for the time you spend on responding my posts.

Have a nice evening.
Werner

Re: [PythonReports-users] Future of PythonReports

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

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.

- HTML rendering.

- 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.

> 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).

Mandatory attributes should all be marked as such in the documentation, 
http://pythonreports.sourceforge.net/prt.shtml

> I like the wx designer better, so I hope that is the "future" and if yes
> I will try and have ago and doing the change to allow to "Insert",
> "Delete" elements and maybe also to move them, unless someone is already
> working on this.

I wish you good luck.  If you make any progress, please keep us informed.

Best wishes,
alex.

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

Re: [PythonReports-users] Future of PythonReports

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

Werner F. Bruhin wrote, at 07.12.2012 13:24:
>
> Wouldn't the Editor need quit a bit of work before this would be useful?

Perhaps there should be reprort preview before the editor would be 
really useful.  Shouldn't be difficult to add since the renderer is 
there from the beginning of the project.  Though, as far as I remember, 
it had some glitches caused by insufficient DC resolution.

> E.g. support for things like "font", "style", "group" (and others I
> haven't noticed that they are not yet supported).

As far as I know, the editor fully supports all template elements.

"font", "style", "group" are in the "lists" category at the bottom of 
the properties pane.

Best wishes,
alex.

Re: [PythonReports-users] Future of PythonReports

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

On 07/12/2012 14:07, alexander smishlajev wrote:
> Werner F. Bruhin wrote, at 07.12.2012 13:24:
>> Wouldn't the Editor need quit a bit of work before this would be useful?
> Perhaps there should be reprort preview before the editor would be
> really useful.  Shouldn't be difficult to add since the renderer is
> there from the beginning of the project.  Though, as far as I remember,
> it had some glitches caused by insufficient DC resolution.
>
>> E.g. support for things like "font", "style", "group" (and others I
>> haven't noticed that they are not yet supported).
> As far as I know, the editor fully supports all template elements.
>
> "font", "style", "group" are in the "lists" category at the bottom of
> the properties pane.
I see, there is another little problem with 2.9.4 here as the "..." 
button to view the list doesn't show.  IIRC have seen this in other 
programs but don't recall the details.  Will try to figure it out over 
the next few days.

See you
Werner

Re: [PythonReports-users] Future of PythonReports

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

Hi Alex,

On 07/12/2012 15:14, Werner F. Bruhin wrote:
...
> "font", "style", "group" are in the "lists" category at the bottom of
> the properties pane.
> I see, there is another little problem with 2.9.4 here as the "..."
> button to view the list doesn't show.  IIRC have seen this in other
> programs but don't recall the details.  Will try to figure it out over
> the next few days.
Needed to change this to get the button in wx 2.9.4 for the "list" 
properties.

=== modified file PythonReports/editor/propertiesgrid.py

--- PythonReports/editor/propertiesgrid.py 2012-12-05 09:13:33 +0000

+++ PythonReports/editor/propertiesgrid.py 2012-12-07 14:44:24 +0000

@@ -560,6 +560,10 @@

def GetClassName(self):

return self.__class__.__name__

+

+ def GetEditor(self):

+ # Set editor to have button

+ return "TextCtrlAndButton"

def GetValueAsString(self, flags):

"""Just return property name + _list"""



Best regards
Werner