Since "RFC" stands for "Request For Comments", my comment would be "Good
On Tue, 2007-09-04 at 20:29 -0700, Brian Matherly wrote:
> Lately I have felt inspired to try to make it easier to write new reports=
. One thing that I find cumbersome is adding options to a report. To me, it=
doesn't make sense for a report plug-in to require GTK. Douglas Blank insp=
ired me with his widgets in the calendar report. So I'm trying something ou=
t that I think will make things easier:
> Fundamentally, I have created a new options class called MenuOptions. It =
inherits from ReportOptions but does all the work of generating the graphic=
al elements and parsing them out. The report writer just has to implement t=
he add_menu_options() function and add the appropriate options to the menu.
> Here is the _MenuOptions.py file which includes the MenuOptions class and=
all the types of options that can be added:
> Here is an example of how the AncestorChart report changed when using the=
> I don't see this as a final solution. I see it as a phase in a master pla=
n to clean up the report interface. If this works out, the goal would be fo=
r all reports to eventually use this interface and do away with the old way=
> So I'm looking for feedback. Is this a good idea? Any ideas of how to do =
it better? All comments are welcome.
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> Gramps-devel mailing list