Hi SmileChris and Lukasz:
It's true that with this proposal the load of templates depends of the order
of on which the templates are loaded. But it's is something that the project
manager should controlled. But the usual is that you only overwrite only one
time a template (although it work with an
2010/10/15 Andy McCurdy
> We are in complete agreement ;)
>
Thanks for the clarification ;)
>
> 2010/10/15 J. Pablo Martín Cobos
>
>> Hi Andrew,
>>
>>
>> I think you agree with me in all. Thank you very much for your long
>> e-mail. I think you have explain the problem better than me. To use
On Oct 16, 8:35 am, Łukasz Rekucki wrote:
> Which "x.html" should be chosen ? the one from admin or the one from
> external app "A" ? Both are valid uses. There is a dangerous
> temptation to say "next that would be loaded after this", but that
> depends on loaders and application order - lets do
We are in complete agreement ;)
2010/10/15 J. Pablo Martín Cobos
> Hi Andrew,
>
> I think you agree with me in all. Thank you very much for your long e-mail.
> I think you have explain the problem better than me. To use the urls for
> overwrite the templates "leads terrible looking URL", it's re
2010/10/15 Łukasz Rekucki
> 2010/10/15 J. Pablo Martín Cobos :
> >
> > Really the problem comes when we reuse a application: from other people,
> > from Django (i.e. django.contrib.admin), or even my own that we reuse in
> > some projects. Usually you want to change slight things and usually you
2010/10/15 J. Pablo Martín Cobos :
>
> Really the problem comes when we reuse a application: from other people,
> from Django (i.e. django.contrib.admin), or even my own that we reuse in
> some projects. Usually you want to change slight things and usually you want
> only to change the visualizatio
On Oct 16, 2:09 am, Andrew Godwin wrote:
> So, from what I can work out, this is a proposal for an {% extends %}
> tag which allows you to extend from the parent template of the same name
Just to chime in, I like this proposal.
IMO: If a designer wants to override a third party's template (by
al
Hi Dougal,
Of course this have many advantages for front end developers and designers.
But please we must not do "full copy and paste of the original template".
This is the finallity of the project.
The template code is nearly so important as view code.
Regards,
--
Pablo Martín
2010/10/15 Dou
Hi Andrew,
I think you agree with me in all. Thank you very much for your long e-mail.
I think you have explain the problem better than me. To use the urls for
overwrite the templates "leads terrible looking URL", it's really true.
If you don't think you agree with me in all, please tell me. Beca
Hi Harro,
This templatetag is different that the one you implemented. I don't feel
dirty :-P
Regards,
--
Pablo Martín
2010/10/15 Harro
> I wrote an extends tag once that changed the extending template based
> on a get variable..
> The idea was that we could then simply get a part of the web
Hi luke,
Thanks in advance, but of course I have seen this wiki, but I had wrotten in
my first e-mail I needed and wanted more funcionallity. I think we have to
change a little the inheritance of templates, this wiki is from 2008, so I
think it's possible to add new funcionality.
It would be very
%}
>
>
> To perform something like this, we should copy all the change_list template
> (i.e. 100 lines of code), in order to add this two changes. For this subject
> I created a google-code project [1], wich is working in a little project of
> Universidad de Granada [2] succesfully.
>
I can see one main use case. Front end developers and designers would be
able to extend templates without worrying about python code changes or doing
a full copy and paste of the original template (if they can find it.)
Dougal
On 15 Oct 2010 14:10, "Andrew Godwin" wrote:
> On 15/10/10 13:41, J.
On Fri, Oct 15, 2010 at 6:09 AM, Andrew Godwin wrote:
> So, from what I can work out, this is a proposal for an {% extends %} tag
> which allows you to extend from the parent template of the same name (so it
> looks back in the list of possible templates, and picks the one that comes
> before you
I wrote an extends tag once that changed the extending template based
on a get variable..
The idea was that we could then simply get a part of the website in a
lightbox popup without all the "outer content".
I removed it afterwards and we did it properly.. it felt dirty.
On Oct 15, 3:29 pm, Luke P
On Fri, 2010-10-15 at 14:41 +0200, J. Pablo Martín Cobos wrote:
> To perform something like this, we should copy all the change_list
> template (i.e. 100 lines of code), in order to add this two changes.
Have you seen http://code.djangoproject.com/wiki/ExtendingTemplates ?
Thanks,
Luke
--
"I
On 15/10/10 13:41, J. Pablo Martín Cobos wrote:
Hi,
I'm a Django developer since more or less 3 years. Some time ago I had
the need for the extends templatetag to have more funcionality.
The funcionality I mean is that a template can extends from "itself".
I'm going to try to explain it bett
be usefull
Regards,
--
REF's
1. http://code.google.com/p/django-smart-extends/
2. http://spinoff.ugr.es/
--
Pablo Martín
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegr
18 matches
Mail list logo
