[reportlab-users] RE: Visual editor: what are the objectives?

will at phototropia.org will at phototropia.org
Tue Dec 6 19:10:24 EST 2005

     Maybe we should get somewhere seperate than the reportlab list to
discuss this from here.  I just looked over where pyqt is at since we
wrote our pyqt app. in 2004.  However, my impressions/ideas here are
not really reportlab specific issues.  I don't know if we need
svn/wiki functionality Andy has offered yet, but a mailing list that
anyone can join for discussion/coordination might be useful now.


> will at phototropia.org wrote:
>> Friends:
>>      Cool!  We were going to use R for our graphing(with rpy as our
>> python
>> adapter and pygtk), but if we use reportlab for our graphing, I can
>> justify putting hours in this now.
>>      IMHO, it seems like this should be designed as a gui frontend to
>> reportlab2.  Reportlab developers/users pick out a subset of features
>> that the gui frontend supports for our beta release.  The debate
>> about what to use from reportlab2 might help Andy and crew to
>> galvanize/make features public.
>>      I see that others are not as interested in the graphing
>> capabilities
>> or RL.  However, I need to make this applicable to what my budget
>> demands I produce.  I will need to make a demo for my people anyway.
> Will and others, can I suggest you take a look at the manual for
> our Diagra product?
>    http://www.reportlab.com/docs/diagradoc.pdf
> and the datasheet on
>    http://www.reportlab.com/docs/diagra-ds.pdf
> This has a Tkinter GUI which is commercial code and about
> five years old.  To be honest I would love to replace it with
> something slicker, but it basically works well.  I will discuss with
> my board whether (a) we could release source generally and (b)
> we could let the community use it as is, but I can
> definitely provide it to anyone who wants to actively work on
> a replacement like Will.
> The 'strongly commercial' part to this are the Data Aware charts
> and the colour-separating EPS back end, which let publishers
> create charts on a regular basis.  But the GUI is basically a
> generic object-inspector-and-previewer.  Having something like
> this makes charts very 'discoverable'.
> Best Regards,
> Andy Robinson
> _______________________________________________
> reportlab-users mailing list
> reportlab-users at reportlab.com
> http://two.pairlist.net/mailman/listinfo/reportlab-users

More information about the reportlab-users mailing list