Quoting Charl van Niekerk <charlvn@...>:
> On 10/11/06, David Fraser <davidf@...> wrote:
>> Hmmm .. I can provide an installer for Kid on Windows if anyone needs
>> this while kid is still the current choice:
> Nice, can I update the wiki page to point to that?
> I have been doing a little more research, and I have to be honest that
> I am not entirely convinced anymore that Django is the way to go.
> Firstly, in order to run Django it seems that you need a DBMS
> (Postgres or MySQL). This is not unreasonable I think but the current
> Pootle doesn't require something like that.
Django is a framework made for rapid web site developement. It features
resolving, text based templating engine and "model" objects, that are
DB tables. And it has probably the most useful error pages.
Then it's up to developer to decide whether he will use django's templating
engine or genshi, django's DB mapping or SQLAlchemy.
> Secondly, other than the templating system, what will the real
> advantages of Django be? In terms of templating, there are many
> options, and outside of that, Django seems to be largely about
> information handling. I assume all the translatable/translated strings
> are now going to go into the Postgres / MySQL database?
Current Pootle code is very hard to read. Pages are classes, and there
pages, that have same methods, but those methods are intended to do completely
different things. With migration pootle would gain on code readability, since
pages are functions in Django and are far easier to track than hunting class
methods all over the code. Also, it would be nice to split code based on what
it does, eg. storage-api access in one file, common pootle settings in other,
As far as storage is concerned, that is to be handled by Gintautas' SOC
and not be held in DB.
If I make a step further, I'd make the storage-api branch a new daemon and
access all translations through it. It would make translation locking far
easier, since just the storage-api needs to know what's locked, and others get
"editing denied, locked by X Y" errors.
> This could be an interesting new move for Pootle, but it seems like
> Django will change many of the core design decisions. Is everybody in
Django is not going to change any of the design decisions. If it would,
migration would already be done.
> Personally I am starting to think that Pootle should rather be
> built around its own framework (which just needs to be cleaned out and
> documented). Will it really be easier to put Pootle on Django rather
> than to do the cleaning/documenting?
I disagree on this. Django is here, now, and all we need comes with it. We
really don't want to duplicate work.
> Just some food for thought. :)
> Charl van Niekerk
I may be a bit more words than work, let's hope that changes.