Hi,
I am the author of the django-formrenderingtools package, which focuses
on a template tag library to render forms.
Currently widgets and formsets are not supported, but they could be.
I guess it matches the subject of the GSoC.
So I would be glad if you had a look at my work. It is certain
On Tue, May 24, 2011 at 12:14 PM, Carl Meyer wrote:
> On 05/24/2011 11:53 AM, Jeremy Dunck wrote:
>> I was wondering how people would feel about template origin being an
>> attribute of the Template instance.
>>
>> The point to me would be to make it easier to see which location a
>> template is c
On 05/24/2011 11:53 AM, Jeremy Dunck wrote:
> I was wondering how people would feel about template origin being an
> attribute of the Template instance.
>
> The point to me would be to make it easier to see which location a
> template is coming from; I think the compile_string func could do it--
>
I was wondering how people would feel about template origin being an
attribute of the Template instance.
The point to me would be to make it easier to see which location a
template is coming from; I think the compile_string func could do it--
after constructing the template, the loader would annot
On 05/24/2011 09:35 AM, Gregor Müllegger wrote:
>> Which templates are involved in a form layout?
>
> This is not yet defined in detail. I would suggest a schema like:
>
> forms/layouts//.html
>
> Resulting in templates for the layout "table" like:
>
> forms/layouts/table/row.html
>
Hi Gregor,
On 05/24/2011 09:25 AM, Gregor Müllegger wrote:
>
> Yes, defining a global default is really useful, we shouldn't skip that.
Yep, I'm definitely converted to that position ;-)
>> For the case-by-case override, though, I'd still much rather write
>>
>> {% form "table" %}
>> {% renderf
Hi Preston,
2011/5/23 Preston Timmons :
> This looks interesting so far.
>
> How does setting the form layout affect rendering individual fields in
> a form?
>
> Is the output of {% renderform my_form "first_name" %} equivalent to
> {{ form.first_name }}, or is it more like the output of "as_p" or
2011/5/23 Carl Meyer :
> I guess I was comparing
>
> {% form %}
> {% renderform myform %}
> {% endform %}
>
> to
>
> {% form "table %}
> {% renderform myform %}
> {% endform %}
>
> and thinking the latter didn't seem too comparatively onerous, even if
> you were doing it for every form render. Bu
Hi,
The repository with my changes will be here:
https://github.com/mitsuhiko/django-template-compilation
As this proposal implements a 'newtemplates' module in Django instead
of modifying the existing one until it's proven to be compatible in
every single regard, I will have it as a separate r
On Tue, May 24, 2011 at 3:48 AM, Anshuman Aggarwal
wrote:
> Luke,
> I completely agree on the need for change and personally +1 this as
> it is a completely confusing historical annoyance.
>
> However, as in all deprecation, I would suggest that we start with a
> global setting that allows these
On Tuesday, May 24, 2011 9:48:43 AM UTC+3, Anshuman Aggarwal wrote:
>
> However, as in all deprecation, I would suggest that we start with a
> global setting that allows these links to be hidden on an installation
> by installation basis and the default made to true for now.
>
-1, if only bec
Even more confusing, but extremely great to abuse!
base.html
{% block a %}{% endblock %}
{% block b %}{% endblock %}
{% block c %}{% endblock %}
{% block d %}{% endblock %}
{% block e %}{% endblock %}
index.html
{% block a %}
{% block b %}
{% block c %}
{% blo
Hi all,
This seems like a weirdness in template inheritance...
base.html
{% block title %} ... {% endblock %}
{% block content %}... {% endblock %}
index.html
{% extends "base.html" %}
{% block content %}
{% block title %}
some text
{% endblock %}
{% endblock %}
The paragraph is sh
manage.py has an ambiguous relationship to settings.py: It requires it
to be present, imports it, passes it to core.management.setup_environ,
uses it's location to set your python path, but doesn't necessarily
use it as your settings. You can override that final part via --
settings or DJANGO_SETTI
14 matches
Mail list logo
