Hi All! Jesus, help us to find right solution.
Simply I think every new frontend should use much of existing source code and existing standards. If there would be bookmark framework in Sword i used it. Karl Kleinpaste:
Xiphos has implicitly extended the semantic of that bookmark format, simply by allowing a single bookmark to contain a fully general verse listing. Now, what will happen when I re-sync my Xiphos bookmarks back to any other app which uses putatively the same format? /oops/
Simply every bookmark entity should have unique attribute "id", it is bridge between local file and bookmarks data in program memory. All work user do with bookmarks should be performed on program cleanup phase and only changes (addition/edition/deletion) should be brought into local file. So verse listing stored in metadata should stay. I would like to implement such bookmark framework using xbel format and ideas from wiki and using any simple open xml parser, and upload on Crosswire svn server maybe not as part of Sword Project but some could use and contribute it. I think the framework also should do analysis of uri. P.S. It's hard to read, understand and reply large messages for me, sorry. _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
