Some thoughts
Eugene Pivnev
ti.eugene at gmail.com
Tue Mar 6 10:06:34 MST 2007
* It will be good to hadle with others data types (why not?):
. Contacts (vCard)
. Tasks (iCalendar/vCalendar)
. Notes
. Bookmarks
* In this case tellico will be like PIM or outliner :-). And...
* What about merging tellico w/ treeline? They are very similar:
. both are python apps
. both use qt
. both store data in xml
. both show data in tree view
. etc
* Berkley DB is good storage for xml - specialy via Berkley DB XML API
- because processing plain-text-xml w/ python is too hard w/ hundreds
records.
* XUL is good platform for interface layer - w/ optimized render
builtin into Gekko. There are treeview, buttons, labels etc - all
classic set of widgets - and none of GUI code.
* Next step - spliting tellico for 2 layers - core (processing data)
and frontend (standalone GUI (as now) / browser (XUL)). In this case
core part will be something like "server of storing anything
structured data".
--- and some little wishes ---
* mix catalogs (this is usual, but hard to made - I know)
* Splitting/mergin catalogs (example - merging catalogs of 2 ftp garbages)
* Listview editing of multivalue fields in Edit fields mode ("Allowed
fields"). Example - my field Vendor (of software) looks like this:
"1C; 2X; 3M; ABBYY; Acits; Acronis; ActiveState; Active Data Recovery
Software; ACV Intertrade; ...ZyXEL". It's too hard to add/edit values
in so long string :-(
That's all
More information about the tellico-users
mailing list