As code development has ground to a frustrating halt, I turned over to the documentation. I realized that even though I seem to have a good lot of things jotted down, not everything I've envisioned is black-on-white.
One question that I always get, when I try to get people excited of LightFrame (and people indeed seem interested - once it's ready, that is), is: "How does it differ from the rest of them out there?" Usually I mention the compatibility of virtually any Apache-enabled hosting, MCV-like operation, the ubiquitous PHP, etc...
But one feature that I'm sort of excited about is the native support of internationalization (i18n), both in templates and models. That's one thing that I actually felt missing in Django. Sure, Django seems to have some kind of i18n for models, but from what I can gather, the translations are located in a static file, which needs to be updated manually (do tell me if I'm wrong). LightFrame will incorporate them directly to SQL, natively, intuitively and with great scalability.
More about the i18n plans at the dev wiki
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment