Django is essentially a backend development framework (essentially receive
http request, make http response)

Ruby on Rails tried to integrate with a javascript "framework" in its time
(Prototype / Scriptaculous if I remember correctly) and it exploded on
their faces in my humble opinion.

On Mon, Apr 17, 2017 at 12:01 PM, Matthew Pava <[email protected]> wrote:

> Something you may want to consider is web2py.  It has a lot out of the box.
> http://www.web2py.com/
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Jamesie Pic
> Sent: Monday, April 17, 2017 9:58 AM
> To: [email protected]
> Subject: Re: Django forks
>
> Dear Andréas,
>
> During the past decade, I have fought that model fields do not have usable
> form fields out of the box.
>
> "Django doesn't want to couple a JS framework", is what I remember from
> discussions. For me, having JS enabled form fields does not mean
> **removing** support for pure-HTML form fields, so, nobody would be
> actually "coupled with a JS framework". And, supporting one JS framework
> doesn't mean Django couldn't support other framework neither.
>
> I'd like to try a Django fork that LOVES javascript and out of the box
> experience. Currently, the philosophy in Django is "if it can be in an app
> then it should be in an app", which opposes what "improving ootb
> experience" means for me.
>
> Also, I'd like it to make it easier for newbies to install Django
> projects, I've posted about this in a thread about DJANGO_SETTINGS_FILE on
> django-dev.
>
> And of course, I'd like a fork that's easy to contribute to, iterate with,
> so that features can mature outside of Django before being proposed
> upstream. I'm up for helping others on their features too of course ;)
>
> Best,
> Jamesie
> <3
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/CAC6Op1_TS58kQUnDv0_3vXtF%3DbnsUaqtOe7zq2f8kKe4XBsssw%
> 40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/622fa051501f48bd9dc72865ca42c8d4%40ISS1.ISS.LOCAL.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CALn3ei2J8miNWupexEEADOq5uz0axSOiOZ%2BomWUxAmA3zXhjBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to