I cannot tell about details since it is the first time I hear about it. I just had a quick look. There are many philosophical differences:
1) In page http://glashammer.org/gettingstarted.html#gettingstarted the app calls the libraries, while in web2py, the libraries call the app 2) they have no admin nor appadmin 3) they use jinja2 which means no arbitrary code in templates (they say it is a good think I do not because I like to use recursion to generate menus and js code in views). 4) they live the user the choice of database engine (sqlalchemy storm, etc) which means they'll never create a market for the apps (as Django has succeeded in doing and we hope to do too), they are going to have too many dependencies. 5) they do no have a database abstraction layer that works on GAE and SQL databases. 6) no ticketing system I can go on but it is basically very similar to pylons except with a different code base. Massimo On Jul 4, 4:58 am, Tim Michelsen <[email protected]> wrote: > Hello Massimo, > where do you see the main difference design of your framework to > Glashammerhttp://glashammer.org/documentation.html? > > Best regards, > Timmie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
