About the efficiency part of your comment -the payload generated from something like django rest framework still requires the normal database tuning your normal html based django app would. You would get the added benefit of not making a full trip back to the server between requests (assuming you basically pull down a query set and pivot around it).
One thing I would caution is the integration with something like google maps (if I understood your comment about where you want to take the product you are working on in the future). You might spend some time spiking or playing around with a simple google maps widget + ember to be sure it's the right platform. I've found that when you need to work around the internal run loop (doing external jQuery stuff by hand essentially or 3rd part stuff like google maps) you could run into trouble because you have to work around the framework. I don't have a lot of experience doing this myself (just simple jQuery calendar stuff and that's trivial so it wasn't any issue at all). But the fact that you might be building on top of google maps leaves me unsure of the pain points you might face. If you get started and want to chat more offline => hit me up @ my gmail address Toran On Saturday, June 8, 2013 9:43:19 PM UTC-5, JJ Zolper wrote: > > First off I want to say thanks a lot to Doug and Toran, > > The wealth of information you provided is just astounding. I wish I > understood the dynamics as much as you seem to have progressed too. > > Really for me at this point I don't have much JS experience but I am under > the impression that it is very good for handling the data I would most > likely place over a google map. Since the data will update and typically > there won't be a refresh just an update (i assume ajax) i just feel a > purely JS framework hooked up with Django might be a nice solution. > > @Toran currently the project is going to be texted based because I lost > one developer and it's just me. At some point if we were to reach the point > where we move to the map and adding the more complex features I think at > that point it would be necessary to try things like you are doing with your > team. > > At this point basically I want a user to select criteria and the querysets > to be created in an effective and high performance way because there would > be a lot of entries in the db. I have to work on a good way to select a > random number of entries from the database and I'm not sure if like not > refreshing the page and handling it with ajax of sorts is a good decision. > > Thanks, > > JJ > > On Saturday, June 1, 2013 9:30:23 PM UTC-4, Toran Billups wrote: >> >> My small software company has a team of 4 python devs and we started >> using ember earlier this year (here are a few things we learned along the >> way) >> >> 1.) use a REST framework to transform your models into JSON over the wire >> >> ** We use the latest 2.x of django-rest-framework and it's been great >> ** If you are into the bleeding edge stuff you could also use ember-data >> (I have an adapter that works with both projects to reduce the $.ajax you >> normally write to communicate with your server on the backend) >> >> https://github.com/toranb/ember-data-django-rest-adapter >> >> 2.) you will need a template precompiler that can crunch down your >> handlebars templates >> >> ** We use django compressor to minify our JS and CoffeeScript so we just >> added another module called django-ember-precompile >> >> https://npmjs.org/package/django-ember-precompile >> >> 3.) If you are a unit testing shop look into ember-testing with QUnit and >> Karma >> >> ** The only down side is that Karma does not have a preprocessor built in >> so write your own or wait for my pull request (assuming the core pulls it >> in) >> >> A full example project showing a django app + django rest framework + the >> compressor / handlebars stuff mentioned above >> >> https://github.com/toranb/complex-ember-data-example >> >> Also I'm up for a pairing session or discussion over email if you decide >> to jump in and need some pointers to get started >> >> Toran >> tor...@gmail.com >> >> On Saturday, June 1, 2013 12:34:01 AM UTC-5, JJ Zolper wrote: >>> >>> Hello, >>> >>> So I'm thinking about bundling together Django and Ember. The reason is >>> my front end is going to be lots of data in realtime. Think like overlaying >>> a map with information for an example. Lots of data needs to be handled on >>> the front end. Things need to be extremely dynamic. >>> >>> I love Django and the interface with the database and all that. I'm >>> thinking a powerful solution might be tagging Django and Ember together. >>> Has anyone done this? Anyone have any advice? My questions really are (like >>> the questions on my mind are) like lets say I query the database and get >>> this resulting queryset or list in a variable. In Django you hand that list >>> off to the template. Like I'm not sure how to hand things back and forth >>> between Django and Ember. How I would hand the result from the query to >>> Ember aka JS and then display that to the front end. >>> >>> Does this sound like a powerful solution for handling large amounts of >>> data? Really any information would be wonderful, better than nothing for >>> sure... >>> >>> I need high performance and power for processing quickly and giving the >>> users a seamless experience and I'm wondering if this might be the ticket? >>> >>> Thanks so much, >>> >>> JJ Zolper >>> >> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
