From: Tim W. <tw...@re...> - 2003-06-09 17:01:15
|
Hi, So I'm fairly happy with the output from my XSL stylesheet now, but since support for XSL stylesheets for generating reports is quite a way off in the future I would quite like to make a version of it in Python. For reference, here is some sample output: http://cyberelk.net/tim/gramps/xsl/example The example database doesn't show it, but for people who married a picture of their partner appears on the right-hand side. Should I modify one of the existing Python reports, or start a new one? Tim. */ |
From: Alex R. <sh...@al...> - 2003-06-09 17:20:52
|
On 2003.06.09 12:00, Tim Waugh wrote: > So I'm fairly happy with the output from my XSL stylesheet now, but > since support for XSL stylesheets for generating reports is quite a > way off in the future I would quite like to make a version of it in > Python. [ snip ] > Should I modify one of the existing Python reports, or start a new > one? Tim, I think starting a new one should be a good idea. We could start the whole new category of the reports that use XSL stylesheets. That would be different from the existing reports in some aspects: 1. XSL way creates great XHTML, but what about other formats (pdf?) Existing reports have support for several formats. I guess XHTML could be eventually converted to these, but until this works it'd be nice to keep the old framework intact. 2. XSL way assumes that the data is store in XML. It makes great sense to store data in XML and I'm all for it, but there are some scenarios where this is not guaranteed: (1) existing ZODB database, (2) prospective gnome-db--mysql backends, and (3) a simple case of importing gedcom and writing a report without saving XML datafile. These are just a few concerns that come to mind, there may be more. On the other hand, it makes perfect sense to enable stylesheet-based reports when XML data exists and XHTML output is desired. So I would add new XSL reports and keep the old-style reports. Just MHO :-) Alex -- Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |
From: Tim W. <tw...@re...> - 2003-06-09 17:41:36
|
On Mon, Jun 09, 2003 at 12:19:48PM -0500, Alex Roitman wrote: > I think starting a new one should be a good idea. We could start the=20 > whole new category of the reports that use XSL stylesheets. That would=20 > be different from the existing reports in some aspects: I don't mean to use the XSL stylesheet I've already written, just to create a Python report module that creates similar output. My immediate goal is to get good print output, and I haven't found a good way of getting that from XHTML. So I was going to make a Python report module that uses the current TextDoc stuff for several different output formats. Things I want it to include: - Omitting 'x married y' if the fact has already been stated - Omitting details person descriptions if they have already been described - Optionally including photos of people and their spouses - Listing children and (briefly) grandchildren - Better description of events (there are bugs in the FTM ancestor report here: for example if a place is known for an occupation the output is off) - Where someone has married several times, use 'later married' appropriately They are all enhancements really, which is why I'm not sure whether to start with an existing report and make it better, or if the full set of enhancements really makes it a different type of report. ------ Now the points you raise about the experimental XSL approach to reports: > 1. XSL way creates great XHTML, but what about other formats (pdf?)=20 > Existing reports have support for several formats. I guess XHTML could=20 > be eventually converted to these, but until this works it'd be nice to=20 > keep the old framework intact.=20 This is the problem. I haven't got a solution I'm afraid. There is always XSL-FO I suppose, or else perhaps there is a solution to be found by making an XSL version of TextDoc. > 2. XSL way assumes that the data is store in XML. It makes great sense=20 > to store data in XML and I'm all for it, but there are some scenarios=20 > where this is not guaranteed: (1) existing ZODB database, (2)=20 > prospective gnome-db--mysql backends, and (3) a simple case of=20 > importing gedcom and writing a report without saving XML datafile.=20 > These are just a few concerns that come to mind, there may be more. On=20 > the other hand, it makes perfect sense to enable stylesheet-based=20 > reports when XML data exists and XHTML output is desired. So I would=20 > add new XSL reports and keep the old-style reports.=20 Well here my plan was to hook into the python bindings for libxslt and just build a temporary XML file. Tim. */ |
From: Don A. <don...@at...> - 2003-06-09 17:27:15
|
I would recommend starting a new report. A lot of what is in the current reports probably wouldn't apply. The current reports work on abstracting the target format (such as OpenOffice.org, Abiword, PDF). It seems as if the XSL implementation is a different path, and wouldn't use this abstraction. Fortunately, the report plugin system is not dependent on the report abstraction framework, so by starting a new report would eliminate all the stuff you wouldn't need. Don Tim Waugh wrote: >Hi, > >So I'm fairly happy with the output from my XSL stylesheet now, but >since support for XSL stylesheets for generating reports is quite a >way off in the future I would quite like to make a version of it in >Python. > >For reference, here is some sample output: >http://cyberelk.net/tim/gramps/xsl/example > >The example database doesn't show it, but for people who married a >picture of their partner appears on the right-hand side. > >Should I modify one of the existing Python reports, or start a new >one? > >Tim. >*/ > > |
From: Tim W. <tw...@re...> - 2003-06-09 17:42:56
|
On Mon, Jun 09, 2003 at 11:22:32AM -0600, Don Allingham wrote: > I would recommend starting a new report. A lot of what is in the current= =20 > reports probably wouldn't apply. The current reports work on abstracting= =20 > the target format (such as OpenOffice.org, Abiword, PDF). It seems as if= =20 > the XSL implementation is a different path, and wouldn't use this=20 > abstraction. Yes, although it's a very nice abstraction to have. It would be a shame if XSL-based reports could only output XHTML. Anyhow, see my other message for what I really meant to ask. Tim. */ |
From: Don A. <don...@at...> - 2003-06-09 18:15:27
|
Okay. I think I understand what you are attempting. Sorry for being a little slow:-) The FTM style reports were created by request to try to mimic the layout created by a popular Windows-based program. I kind of want to keep this format intact (however, I would definitely like to have some clean up on them). Creating a new report gives a lot more flexibilty, and doesn't need to be held back by try to preserve an old layout format. For ease of development, however, it might be a good idea to use an existing report as a starting point. I haven't had time to really document the details of the report dialogs and text doc classes. Don Tim Waugh wrote: >On Mon, Jun 09, 2003 at 11:22:32AM -0600, Don Allingham wrote: > > > >>I would recommend starting a new report. A lot of what is in the current >>reports probably wouldn't apply. The current reports work on abstracting >>the target format (such as OpenOffice.org, Abiword, PDF). It seems as if >>the XSL implementation is a different path, and wouldn't use this >>abstraction. >> >> > >Yes, although it's a very nice abstraction to have. It would be a >shame if XSL-based reports could only output XHTML. > >Anyhow, see my other message for what I really meant to ask. > >Tim. >*/ > > |
From: Tim W. <tw...@re...> - 2003-06-13 17:08:35
|
On Mon, Jun 09, 2003 at 12:09:18PM -0600, Don Allingham wrote: > For ease of development, however, it might be a good idea to use an=20 > existing report as a starting point. I haven't had time to really=20 > document the details of the report dialogs and text doc classes. Okay, I've done this. My report code, which is a rough approximation to the ancestors.xsl stylesheet I posted earlier, is here: http://cyberelk.net/tim/gramps/python/Ancestors.py It requires current CVS to display correctly in HTML. What do you think? Tim. */ |
From: Alex R. <sh...@al...> - 2003-06-13 17:24:34
|
On 2003.06.13 12:08, Tim Waugh wrote: > Okay, I've done this. My report code, which is a rough approximation > to the ancestors.xsl stylesheet I posted earlier, is here: [snip] > What do you think? Looks pretty good if you ask me. I would suggest naming it something less generic than just Ancestors report, but this is not too important I guess. The contents looks great! Alex -- Alexander Roitman http://ebner.neuroscience.umn.edu/people/alex.html Dept. of Neuroscience, Lions Research Building 2001 6th Street SE, Minneapolis, MN 55455 Tel (612) 625-7566 FAX (612) 626-9201 |