I guess the people that don't get the point have probably never made a heavy Javascript application ... Ever used Backbone.js ?
client-side - one page - websites are much nicer to use than any website with a page load after every click. So I totally understand why you would do such a project, and I actually think it is a lovely idea !!! On the other hand, I've started to think lately that Django is not the best backend solution for building such applicatons. So, @davide, how do you plan on making sure that any weird API can be plugged-in to the system ... will you separate nicely the model layer from the "backend" (web API, or dummy data store, or whatever) ??? Cheers anyway, and I'll follow the project ! Sébastien On Thursday, April 5, 2012 9:22:13 AM UTC+3, DvD wrote: > > Hi folks, > I created a project not long ago and I'm currently maintaining it called > Broke which wants to be a porting to Javascript of Django > https://github.com/brokenseal/broke-client > You can find it featured inside the todomvc project from addy osmani > https://github.com/addyosmani/todomvc ( > https://github.com/brokenseal/todomvc for the latest updates from broke ) > > I think the project itself has a lot of potential but lacks two very > important things: a real documentation and a community. > I'm writing to you all to see if anyone could be interested in taking part > to this project. > Broke currently features a lot of cool stuff such as: > - pythonic classes and models: write stuff like > > models.Model.create({ > __name__: "todo.models.Task" > ,title: models.CharField({ max_length: 200 }) > ,is_complete: models.BooleanField({ 'default': false }) > ,update: function(kwargs){ > if('is_complete' in kwargs && kwargs['is_complete']) { > this.elements().addClass('done'); > } else if('is_complete' in kwargs && !kwargs['is_complete']) { > this.elements().removeClass('done'); > } > > return this._super(kwargs); > } > }); > > - django templating: you can basically reuse the same templates you are > currently using server side, with some limitations ( the only supported > tags are if-else, for cycles, ifequal, comment ) > - database routing: you can choose to save your object on any data source > you want ( local storage, remote server, a local json object ) > > Have a look at the code base and let me know what you think. > Anyone? :) > > Cheers, > Davide > -- 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/-/dKBwY_yj9kMJ. 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.
