Thanks for asking, Marcin. This project started back in 2009 because at that time there was not even a single js mvc framework around that I liked ( at that time the only ones around were JavascriptMVC, Jamal and another one, can't remember the name ). That's the main reason behind this project but there are plenty more than that.
What I essentially ported to js is the philosophy that we all love and care for, from Django and a feeling that this is missing on the js communities. It's like when Django started: why didn't they use Rails? Same reasons here. Cheers! Davide Il giorno giovedì 5 aprile 2012 08:36:03 UTC+2, Marcin ha scritto: > > What's the motivation for this project? Who (especially already being > familiar with python and django) would want to use this, and for what? > > On Thu, Apr 5, 2012 at 07:22, DvD <[email protected]> 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/-/nXspKySFAhQJ. >> 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/django-users?hl=en. >> > > > > -- > Marcin Tustin > Tel: 07773 787 105 > > -- 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/-/X3MyD7pFJhAJ. 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/django-users?hl=en.
