Some thoughts

[Robby Stephenson]

On Wednesday 07 March 2007, you wrote:
> > > * 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.
> >
> > I plan to use SQL for version 2.
>
> If this will be not sqlite then there will be some inconveniences to
> deploy my data in new quickly.

It'll be similar to how amarok works, with a choice of backends. sqlite, 
MySQL, etc.

> > > * 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".
> >
> > If you need that, then using a real DB frontend is a better idea. MySQL
> > or PostgreSQL or anything "stores structured data" by design. Kexi
> > would probably work well for you.
>
> Tellico and treeline have to great advantages:
> 1. simple hierarchic viewing of data
> 2. all [meta]data in one file

I'm afraid I'll have to disappoint you. I don't have plans to move to a 
separated architecture. The fact that the data is in XML means it can be 
read and parsed rather easily, so you view it without using Tellico itself. 
The same will be true, although a bit more difficult, when the data is in a 
SQL database.

And there's no way I'm touching XUL. Tellico is a KDE app. Far, far in the 
future, perhaps it'll run on windows with KDE 4. We'll see.

Robby