Re: Choosing a JS framework to go together with Django
In the end, my project stalled due to lack of resources. We might pick it up but it's been abandoned for quite some time. I haven't had any django projects since. Hence, I can't make any recommendations. DjangoAjax looks promising but might lack the community support you expect. It is however based on jQuery and ASP.NET MVC, so if you can see past the M$ cruft, some guides etc are available. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: Choosing a JS framework to go together with Django
@Kelly Nicholes In backbone.js everything is in JS, meaning that there could be no conflict between declarative code and Django handled templates. If I can expose my python models, through auto serialization (JSON) from Django, I can see a productivity win. But I'm a little afraid of the tight coupling in data models between back-end and front-end. My main concern is that I'll have to rewrite large parts of JS if/when the models change. Have you any experience ironing out these issues? Maybe it's not a problem but I lack experience with both frameworks. I'll look more into backbone.js :) Den onsdag den 5. september 2012 16.34.29 UTC+2 skrev Kelly Nicholes: > > It would be a travesty to not mention backbone.js. > > On Tuesday, September 4, 2012 7:39:49 AM UTC-6, dotnetCarpenter wrote: >> >> Hi all. >> >> I'm new here and just took over a Django project for the first time. I'm >> still getting to grip with Django but as a front end dev for the past 5 >> years, I'm also looking for a client-side library/framework to go together >> with my project. >> My requirements for a JS framework is that it: >> >>1. is unobtrusive (Django rendered HTML will be shown to scraper bots >>like google) >>2. provides some sort of structure (MVC, MVP, MVVM ect.) >>3. embraces standards >>4. doesn't conflict with Django templates or does so intentionally >>5. ideally uses the same template language as Django >> >> In the ideal world a request/response scenario would look like this: >> >>1. A client make a (HTTP) request to the (django powered) web site >>with (HTTP) Accept header text/html >>2. Django response in the usual way by rendering the assign View >>(django template) >>3. The view figure out if JS is supported (implemented in JS). If no, >>this scenario stays in loop 1-3. If yes, then 4. >>4. The client (usually a browser) wire up the client-side app >>structure, hook in to URI links, add transitions between views, >>data-bindings ect. >>5. Subsequent request are now handle by the JS framework, either user >>initiated (e.g. clicking a link) or app initiated (e.g. pulling extra >>data), that will modify the request header to Accept header >>application/json or application/django-template. >>6. If django receive a request with an application/django-template >>header it will serve the view as plain text. E.g. Content-type: >> text/plain. >>On the other hand if django receive a request with application/json, it >>will send the object model defined in the view as JSON. >>7. The client-side JS framework will receive a template to render in >>the first request and the data to render in the template in the second >>request. A promise object could be used to synchronize the two calls. >> >> This way django will work as intended for non JS clients and silently >> convert to a RIA in clients that supports JS, with minimal double work for >> the two execution contexts. >> A big pro in this is the fact that both django and the JS framework share >> template and data (only has to defined once - in django) - we'll duck type >> all the way. But does this JS framework exist? Does anyone have any >> experience with working with django and JS frameworks? Is there any obvious >> pitfalls in my ideal world scenario in regard to Django? And finally, is it >> possible to serve templates as plain text with django? >> >> >> Cheers, Jon and thanks in advance >> >> PS. I accidentally cross-posted this to the Django Developers group >> before realizing it was the wrong forum. Sorry about that. >> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/eGLc5LTL5_sJ. 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.
Re: Choosing a JS framework to go together with Django
@Peith Yes, I can see the advantage of not having to spend time working out template conflicts. But you'll have to write two sets of template code, right? One for Django and one for KnockoutJS. Or am I missing something? Cheers, Jon Den tirsdag den 4. september 2012 16.38.29 UTC+2 skrev Peith: > > i've been playing with KnockoutJS lately. one thing i like about it is > that it's built-in templating engine has a different syntax than Django's, > so there shouldn't have any conflict. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/ZK2mKn3Gb54J. 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.
Re: Choosing a JS framework to go together with Django
Hi vicherot. I'm interested to know how you made the distinction between your dhtml/ part of your site to the shtml/ part. It looks like you pretty much used the same code base to generate the 2 versions. Can you elaborate on the Django specific parts of your implementation? Cheers, Jon Den tirsdag den 4. september 2012 16.55.40 UTC+2 skrev vicherot: > > men, i use Jquery on www.expoferiasg.com.ar and works quite well.. with > any problem. > > 2012/9/4 Peith Vergil > > >> i've been playing with KnockoutJS lately. one thing i like about it is >> that it's built-in templating engine has a different syntax than Django's, >> so there shouldn't have any conflict. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To post to this group, send email to django...@googlegroups.com >> . >> To unsubscribe from this group, send email to >> django-users...@googlegroups.com . >> For more options, visit this group at >> http://groups.google.com/group/django-users?hl=en. >> > > > > -- > Rafael E. Ferrero > Claro: (03562) 15514856 > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/kWCYgpb5cWYJ. 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.
Re: Choosing a JS framework to go together with Django
Wow - a lot of answers. Great community! First of all, just to clearify. My aim is to have smooth user experience while utilizing Django and replicate as little code as possible on the client and the server. Think, reuse of server code on the client. I've looked at AngularJS and it has a rendering layer that doesn't work without JS. Hence, no google support since google still requires us to deliver HTML snapshot<https://developers.google.com/webmasters/ajax-crawling/docs/getting-started>. Which means it violate my first requirement. AngularJS doesn't seem to offer help in this regard.https://groups.google.com/forum/?fromgroups=#!topic/angular/yClOeqR5DGc Almost all JS frameworks in the wild, violate simple SEO rules, so it's not confined to AngularJS at all. jQuery doesn't dictate client-side rendering. but doesn't offer any structure at all. Albeit it's great to build your own structure on top of. Thanks for the list of frameworks. I haven't look at Knockout yet but it seems to require JS to do it's data bindings. Cheers, Jon. Den onsdag den 5. september 2012 20.14.29 UTC+2 skrev Amyth: > > I am not sure what you are exactly trying to achieve. A more issue > specific topic would have been easy to understand though i can suggest you > following frameworks (in particular order): > > 1. KnockoutJS > 2. BackboneJS > 3. Cappucino > 4. Ember.Js > 5. Sammy.JS > 6. Spine.JS > 7. JavascriptMVC > > On Wed, Sep 5, 2012 at 8:04 PM, Kelly Nicholes > > > wrote: > >> It would be a travesty to not mention backbone.js. >> >> >> On Tuesday, September 4, 2012 7:39:49 AM UTC-6, dotnetCarpenter wrote: >>> >>> Hi all. >>> >>> I'm new here and just took over a Django project for the first time. I'm >>> still getting to grip with Django but as a front end dev for the past 5 >>> years, I'm also looking for a client-side library/framework to go together >>> with my project. >>> My requirements for a JS framework is that it: >>> >>>1. is unobtrusive (Django rendered HTML will be shown to scraper >>>bots like google) >>>2. provides some sort of structure (MVC, MVP, MVVM ect.) >>>3. embraces standards >>>4. doesn't conflict with Django templates or does so intentionally >>>5. ideally uses the same template language as Django >>> >>> In the ideal world a request/response scenario would look like this: >>> >>>1. A client make a (HTTP) request to the (django powered) web site >>>with (HTTP) Accept header text/html >>>2. Django response in the usual way by rendering the assign View >>>(django template) >>>3. The view figure out if JS is supported (implemented in JS). If >>>no, this scenario stays in loop 1-3. If yes, then 4. >>>4. The client (usually a browser) wire up the client-side app >>>structure, hook in to URI links, add transitions between views, >>>data-bindings ect. >>>5. Subsequent request are now handle by the JS framework, either >>>user initiated (e.g. clicking a link) or app initiated (e.g. pulling >>> extra >>>data), that will modify the request header to Accept header >>>application/json or application/django-template. >>>6. If django receive a request with an application/django-template >>>header it will serve the view as plain text. E.g. Content-type: >>> text/plain. >>>On the other hand if django receive a request with application/json, it >>>will send the object model defined in the view as JSON. >>>7. The client-side JS framework will receive a template to render in >>>the first request and the data to render in the template in the second >>>request. A promise object could be used to synchronize the two calls. >>> >>> This way django will work as intended for non JS clients and silently >>> convert to a RIA in clients that supports JS, with minimal double work for >>> the two execution contexts. >>> A big pro in this is the fact that both django and the JS framework >>> share template and data (only has to defined once - in django) - we'll duck >>> type all the way. But does this JS framework exist? Does anyone have any >>> experience with working with django and JS frameworks? Is there any obvious >>> pitfalls in my ideal world scenario in regard to Django? And finally, is it >>> possible to serve templates as plain text with django? >>> >>
Choosing a JS framework to go together with Django
Hi all. I'm new here and just took over a Django project for the first time. I'm still getting to grip with Django but as a front end dev for the past 5 years, I'm also looking for a client-side library/framework to go together with my project. My requirements for a JS framework is that it: 1. is unobtrusive (Django rendered HTML will be shown to scraper bots like google) 2. provides some sort of structure (MVC, MVP, MVVM ect.) 3. embraces standards 4. doesn't conflict with Django templates or does so intentionally 5. ideally uses the same template language as Django In the ideal world a request/response scenario would look like this: 1. A client make a (HTTP) request to the (django powered) web site with (HTTP) Accept header text/html 2. Django response in the usual way by rendering the assign View (django template) 3. The view figure out if JS is supported (implemented in JS). If no, this scenario stays in loop 1-3. If yes, then 4. 4. The client (usually a browser) wire up the client-side app structure, hook in to URI links, add transitions between views, data-bindings ect. 5. Subsequent request are now handle by the JS framework, either user initiated (e.g. clicking a link) or app initiated (e.g. pulling extra data), that will modify the request header to Accept header application/json or application/django-template. 6. If django receive a request with an application/django-template header it will serve the view as plain text. E.g. Content-type: text/plain. On the other hand if django receive a request with application/json, it will send the object model defined in the view as JSON. 7. The client-side JS framework will receive a template to render in the first request and the data to render in the template in the second request. A promise object could be used to synchronize the two calls. This way django will work as intended for non JS clients and silently convert to a RIA in clients that supports JS, with minimal double work for the two execution contexts. A big pro in this is the fact that both django and the JS framework share template and data (only has to defined once - in django) - we'll duck type all the way. But does this JS framework exist? Does anyone have any experience with working with django and JS frameworks? Is there any obvious pitfalls in my ideal world scenario in regard to Django? And finally, is it possible to serve templates as plain text with django? Cheers, Jon and thanks in advance PS. I accidentally cross-posted this to the Django Developers group before realizing it was the wrong forum. Sorry about that. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/WrIx5DWqCVgJ. 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.
