I think something as simple as
{% form your_form prefix='bootstrap' %}
and
{% field your_field prefix='bootstrap' %}
would add huge flexibility, exactly the concept I was trying to convey!
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contr
On Wednesday, February 1, 2017 at 3:28:44 PM UTC+1, Tim Graham wrote:
>
> Hi Gert, I think the renderer API could be used for this use case. Did you
> look at that?
>
>
> https://docs.djangoproject.com/en/dev/ref/forms/renderers/#the-low-level-render-api
>
What I currently miss here is that there
Hi Tim
I did, and I agree that a TemplatesSetting renderer of sorts would most
likely be the way to implement.
I also think that the use case of "*Using some CSS framework*" is common
enough to warrant giving developers a clean/standard way of doing this
rather than letting each roll their own
Hi Gert, I think the renderer API could be used for this use case. Did you
look at that?
https://docs.djangoproject.com/en/dev/ref/forms/renderers/#the-low-level-render-api
On Wednesday, February 1, 2017 at 6:05:08 AM UTC-5, Gert Steyn wrote:
>
> Hi All
>
> I got very excited when I read about t
The existing Redirect Model has no field for creation and updation
timestamp. Many Django applications use slug based urls, and a redirect is
created whenever slug changes. The redirects table will keep expanding and
there will be no way to identify or delete the old redirects later, may be
aft
Hello,
On this topic, I'm using the excellent django-appconf library
(https://pypi.python.org/pypi/django-appconf), which:
- Supports namespaced custom settings
- Handles default values natively
As far as I can tell, that solution is pretty efficient without requiring
specific Django support ;)
Hi All
I got very excited when I read about the upcoming template based widgets,
it is something that is really needed. I would like to hear your comments
on a proposal I have that should only be a couple of lines to add but would
add a massive usability boost.
I propose that we add the concep
Hi Anthony,
Two points:
1) 1.11 is feature frozen, nothing like a new subframework is likely to be
accepted to it.
2) The ticket is actually a dupe of an ancient ticket[1]. In that ticket, you
can see my own take of the subject, of several years ago.
In the years since then, I haven't felt an
Yesterday, I posted a new ticket asking about the potential for adding a
standardised approach for packages to define default settings. [0]
I was writing an app, and when looking for a way to set settings, there was
no clear solution.
Looking at what other projects do, the goto was something l
