Hello,
I've started sketching the API, but I would like to have a chat on IRC
with the developers who are working on the new base classes. Should I
use your branch or start a new one? When can I find you online, guys?
Perhaps I can find you on Jabber? Ottavio? David? Friedle?
I think that we are rolling now, except that, if we want to start
with the DB as soon as possible, somebody else -other than Gintautas,
who will be busy with the API- should start looking into the design
of the DB, and then adapt to the API that Gintautas will develop. It
would be great if we can find somebody who has the right expertise
and is already involved in Debian.
I would suggest to wait until the API works with the file-based backend
before starting work on an RDB binding.
Designing the DB schema should not be difficult here, because we will
have the object model in the API and we will only need to do a direct
translation "OO model" -> "RDB schema", which is a mechanical task.
What is needed here is experience of engineering components that use an
RDB, and admittedly I don't have much of that.
This is probably correct. At the end the editor will have to work
with files. In the Pootle server interface, the translator will first
identify the files that (s)he wants to work in, and then will decide
if (s)he want to translate them online or download them. The editor
is called from the server. I would like to have Friedle's or David's
opinion on this.
I'm not Friedle or David ;) but I think that this is not conceptually
sound. In the online editor the user is not editing a "file", s/he is
editing translations. That's the whole point: if they want a file,
they use the "file server" frontend, and if they want to change a single
string through-the-web, they use a web-based frontend built directly on
our backend which will have a specific operation for changing a single
string. Would you agree?