Difference between revisions of "Addon:Lxml Gramplet"
(→Go further) |
|||
Line 16: | Line 16: | ||
[1] see also [http://lxml.de/objectify.html lxml.objectify] | [1] see also [http://lxml.de/objectify.html lxml.objectify] | ||
+ | |||
+ | ==Screenshots== | ||
+ | |||
+ | [[File:lxml_output.png]] | ||
+ | [[File:lxml_no_stylesheet.png]] | ||
+ | [[File:lxml_dynamic_code.png]] | ||
+ | [[File:lxml_slist.png]] | ||
+ | [[File:lxml_plist.png]] | ||
+ | [[File:lxml_hardcoded_list.png]] | ||
==Test it== | ==Test it== |
Revision as of 13:36, 7 October 2011
lxml gramplet is an experimental gramplet working under POSIX platform(s), which reads, writes, transforms our Gramps XML file on the fly without an import into our database (Gramps session).
Contents
Dependencies and file format
- lxml is a Pythonic binding for the C libraries libxml2 and libxslt. It is known for good performances by using C-level (Cython).
- Gramps XML file format is robust and well documented.
Goals
The idea of this experimental lxml gramplet is to provide a way for using basic lxml features with Gramps XML files.
XPath, Xslt, RelaxNG validation, can be used and done by lxml, which provides an API very close to etree ElementTree module from python 2.5 and later.
The experimental lxml gramplet aims to use these lxml features[1] by parsing a Gramps XML file generated by Gramps 3.3.x and to generate an output sample, using open W3C standards (XML, Web design, Web services, etc ...).
[1] see also lxml.objectify
Screenshots
Test it
You can get a copy of this draft from Addon repository:
http://gramps-addons.svn.sourceforge.net/viewvc/gramps-addons/branches/gramps33/contrib/lxml
Currently, this addon explores multiple ways. Feel free to modify for your own use.
Go further
Cherrytree gramplet ?
CherryTree is an hierarchical note taking application, featuring rich text and syntax highlighting, storing all the data (including images) in a single xml file with extension .ctd.
Comments on DB API Idea
I was basically approaching it from the leave gen.lib alone and implement a "fully blown" SimpleAccess-esque solution. At the moment I basically have a 'DB' object which represents an open database. This at the moment is populated from a Gramps XML file. This is then basically stored as lxml.objectify objects. Internally a graph structure is built to represent the linking inside the database (so relationships and ref. integrity is made easier). 'DBItem' objects consist of the 'node' data, the basic save/delete etc... Deleting an event automatically removes all other references to it (which has caught me out previously). class Person(DBItem): DBTYPE = 'person' Basically registers an object that 'wraps' a basic DBItem, but containing useful attributes/methods. So for a person, we can write attributes such as .birth, .mother, .families etc... etc... It can also over-ride how it should be saved/retrieved etc... I chose this approach because it keeps the process incremental. We can still access the 'raw' data in a DBItem for the stuff I'm not caring about at the moment, but someone can write a 'Place' class later for instance. The DB itself is an xpath queryable object (adds a bit of flexibility for selections that don't have convenient attributes as of yet). I'll see if I can get the code example out this week. Anyway, does this seem a reasonable approach?
source: Archive (Dec 07, 2009) on gramps-devel mailing list
Database compare and merge
- GrampsCompare.py, a python script for comparing data in 2 Gramps xml files.
source: Archive (Oct 02, 2011) on gramps-devel mailing list
Database backend
- DB backend for GRAMPS: SQL ?
Data transfer
Experimental phase for typeless data entry !
Interface
- Alternative interfaces with an experimental gen.lib interface.
- Gramps Mobile Interface for mobile devices.
HTML class
Libhtml is an HTML/XML class for Gramps, see API.
Web application
- GEPS 013 describes a web-based application that runs in your browser, and requires a server. A prototype is now on-line at http://gramps-connect.org/ which is running trunk on a sample database (id=admin, password=gramps).