--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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/b45a3224-e8bc-481b-97a3-d8aa554b3dd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Something you may want to consider is web2py. It has a lot out of the box.
http://www.web2py.com/
-----Original Message-----
From: django...@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Jamesie Pic
Sent: Monday, April 17, 2017 9:58 AM
To: django...@googlegroups.com
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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.
Well, since web2py is in Python, you might find some inspiration there for any extensions or improvements to Django that you would like to see. Why reinvent the wheel, you know?
-----Original Message-----
From: django...@googlegroups.com [mailto:django-users@googlegroups.com] On Behalf Of Jamesie Pic
Sent: Monday, April 17, 2017 10:19 AM
To: django...@googlegroups.com
Subject: Re: Django forks
Matthew, using another framework for new projects would be a tempting solution, if I was not already maintaining god knows how many Django apps and projects, and basically had not been capitalizing on Django itself for the last decade.
Vijay, that RoR failed at it, fails to scare me out, and does not look like a logic argument *for me*. I'm a lot more comfortable with failing than with not trying. And even if it was really "impossible"
and that I fail to understand it, I'm not saying it would be better for you anyway, I'm just looking for other people who think it would serve them too, hence my initial questions, where are forks ?
--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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_4skkvV0PVxAxjsShG%3DD5ryF6uYypwtL2v2UhN8ZGMSw%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 django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
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/ab7afe0af29e4d57bcf6724aa81517ea%40ISS1.ISS.LOCAL.
On Mon, Apr 17, 2017 at 5:47 PM, Vijay Khemlani <vkhe...@gmail.com> wrote:
> If you need particular form widgets or fields not readily available in
> Django I would prefer to write an app that includes them instead of forking
> the whole framework.
That's why I've been writing AND maintaining apps such as
django-autocomplete-light and like, a lot, lot, lot of others[...]
On Monday 17 April 2017 16:37:19 Matthew Pava wrote:
> Django 1.11 made a major change to widget rendering. I am wondering
> if this would help you significantly in your quest. The widget is
> rendered with a template. It would seem you could include the
> JavaScript in that template.
You can.
What I don't get is that the label is still coupled with the field instead of the widget. This would've been a chance to move it, so that we can render proper form groups for custom widgets.
Oh well.
--
Melvyn Sopacua