We use a very new framework called Shipyard
https://github.com/seanmonstar/shipyard at Mozilla to build
http://builder.addons.mozilla.org/. The goal is to have a nice framework
working well with Django. MooTools style (classes etc.).
A lot of requests on dev site, one file per project on production
zalun
On 04/18/12 02:13, br wrote:
We have an extremely javascript& ajax heavy application. To put it
one way, we have blatently disregarded graceful degradation in order
to build the type of application we want to build. We're finding that
as the thing grows, the interactions between the front end javascript
and django are becoming more and more painful, mostly due to the
contortion we have to put django through to make it work with our
design philosophy. (examples: tons of dynamic list filtering,
tagging, object cloning, saving state across multi-page forms, etc.).
This isn't a post to criticize Django, I love it. Nor am I inviting a
critique of the way we build software. I'm just looking for a way to
make Django work better for us and am considering switching to a model
where we use a javascript MVC on top of Django, with JSON bridging the
in-between. We probably should have gone that route to begin with.
Has anyone had good success with any of them? Backbone.js seems to be
the most popular. Although, based on this:
http://codebrief.com/2012/01/the-top-10-javascript-mvc-frameworks-reviewed/
I may check out ember.js.
Thanks,
Ben
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
