mplates, django
>>>>>>>>> cached loader
>>>>>>>>>will have to get 3 templates (from cache). With my proposal your
>>>>>>>>> view
>>>>>>>>>render on
years ago I requested a feature related with templates
>>>>>>>>
>>>>>>>
>>>>>>> [6]
>>>>>>>
>>>>>>>
>>>>>>> , now I have a new request :-) 8 years ago I trie
d
>>>>>>> 2.
>>>>>>> https://code.djangoproject.com/query?status=assigned&status=closed&status=new&reporter=~pmartin&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id
&g
>>>>>
>>>>>>> 1.
>>>>>>> https://github.com/django/django/pulls?q=is%3Apr+author%3Agoinnn+is%3Aclosed
>>>>>>> 2.
>>>>>>> https://code.djangoproject.com/query?status=assigned&status=closed&status
ify_templates-py-L58
>>>>>> 6. https://code.djangoproject.com/ticket/15053
>>>>>>
>>>>>>
>>>>>> Best,
>>>>>>
>>>>>>
>>>>>> El vie., 18 ene. 2019 a las 14:11, Jani Tiainen ()
>>> external package?
>>>>>>
>>>>>> Also you should release it as a package so people can start using it,
>>>>>> also preferably releasing it with BSD license like Django itself is.
>>>>>> Otherwise there are very little
AM J. Pablo Martín Cobos <
>>>>> goi...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> From one year ago, I am using an own command for Django templates
>>>>>> that unify them. With an exa
>>>>> {% for news_item in news %}
>>>>> {{ news_item.title }}
>>>>> {{ news_item.subtitle }}
>>>>> {% endfor %}
>>>>> {% endblock %}
>>>>>
>>>>> 2. base.ht
/www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
>>>> http://www.w3.org/1999/xhtml"; lang="{{
>>>> LANGUAGE_CODE|default:"en-us" }}" {% if LANGUAGE_BIDI %}dir="rtl"{% endif
>>>> %}>
>>>>
>>
>
>>>
>>>
>>> 3. inc.news.title.html
>>> News
>>>
>>> With this command I preproces every template of a settings variable and
>>> I get something like this:
>>>
>>> news.unify.html
>>
w.w3.org/1999/xhtml"; lang="{{
>> LANGUAGE_CODE|default:"en-us" }}" {% if LANGUAGE_BIDI %}dir="rtl"{% endif
>> %}>
>>
>> News
>>
>>
>> {% for news_item in news %}
>
{{ news_item.title }}
> {{ news_item.subtitle }}
> {% endfor %}
>
>
>
> So I have a two improves:
>
>1. It is more fast. And in a real project a view can render easyly 50
>templates
>2. I use news.html to develo
{{ news_item.title }}
> {{ news_item.subtitle }}
> {% endfor %}
>
>
>
> So I have a two improves:
>
> 1. It is more fast. And in a real project a view can render
&
gt; I get something like this:
>>>
>>> news.unify.html
>>>
>>> >> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
>>> http://www.w3.org/1999/xhtml"; lang="{{
>>> LANGUAGE_CODE|default:"en-us" }}" {%
%}dir="rtl"{% endif
>> %}>
>>
>> News
>>
>>
>> {% for news_item in news %}
>> {{ news_item.title }}
>> {{ news_item.subtitle }}
>> {% endf
;> %}>
>>
>> News
>>
>>
>> {% for news_item in news %}
>> {{ news_item.title }}
>> {{ news_item.subtitle }}
>> {% endfor %}
>>
>>
le }}
> {% endfor %}
>
>
>
> So I have a two improves:
>
>1. It is more fast. And in a real project a view can render easyly 50
>templates
>2. I use news.html to develop and news.unify.html to production. So I
>don't lose legilib
tle }}
> {{ news_item.subtitle }}
> {% endfor %}
>
>
>
> So I have a two improves:
>
>1. It is more fast. And in a real project a view can render easyly 50
>templates
>2. I use news.html to develop and news.unif
1. It is more fast. And in a real project a view can render easyly 50
templates
2. I use news.html to develop and news.unify.html to production. So I
don't lose legilibility.
What do you think about "unify templates feature"? Do you know if exists a
similar public
19 matches
Mail list logo
