Hi Neal, Thanks for your question.
On Thu, Jun 18, 2009 at 2:49 AM, NealWalters <[email protected]> wrote: > > Can you please tell us the features and benefits of your framework? > I don't Jinja2 or Werkzeug - so what's in it for developers? Werkzeug has a powerful debugger. Kay contains a bit modified version of Werkzeug's debugger. So you can use the most of the features of this debugger. When an unhandled exception occurs, the debugger will activate and be displayed on your browser window. In this window, you can explore the local namespace at the time when the exception occured. It will help you debug easily. Though the debugger only runs on dev server, it doesn't matter in most cases. Jinja2 is very similar to Django's template system. In my opinion, Jinja2 is more flexible and easier to use. The defferences of the both is on the Jinja2's website. Please check the URL bellow for more details. http://jinja.pocoo.org/2/documentation/switching#django Let's talk about Kay itself. Kay has these features: * A middleware mechanism same as Django's * Full stack i18n feature * powerfull Werkzeug's debugger * powerfull shell tools * easy to start (see README) Having said that, as Ritesh said, it might be a better option for you to look into Glashammer for now if you're looking for a framework for production use. Because Kay is still under beta release, Glashammer has a longer history than Kay, and it is well documented etc.. Regards, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
