On 26 Dez., 19:10, "Dave Smith" wrote:
> There are several use cases that an 'else' simplifies.
> Seehttp://code.djangoproject.com/ticket/4534
> andhttp://code.djangoproject.com/changeset/8095for the patch.
I included it, might make things easier..
I just saw:
{% cycle "foo","bar" as foocy
On Fri, Dec 26, 2008 at 9:54 AM, James Bennett wrote:
>
> On Fri, Dec 26, 2008 at 11:36 AM, Maluku
> wrote:
> > Kind of different question: Why is there no {% else %} in {% ifchanged
> > %}, I think it might be a help to some people.
>
> Because it wouldn't make any sense; the point of 'ifchanged
On Fri, Dec 26, 2008 at 11:36 AM, Maluku wrote:
> Kind of different question: Why is there no {% else %} in {% ifchanged
> %}, I think it might be a help to some people.
Because it wouldn't make any sense; the point of 'ifchanged' is to say
"I have a special thing which only needs to happen when
On 26 Dez., 08:54, "Adam Findley" wrote:
> The real tragedy here is that the Django Template system is great, but
> it's name is "tightly coupled" to the Django Project.
>
> I think DTL is a great and common standard and what people will be looking
> for.
>
> What's wrong with template::dtl o
On Mon, Dec 22, 2008 at 10:50 AM, Maluku wrote:
>
> On 22 Dez., 17:11, Barry Peder
>> In addition to DojoX DTL, there's an Erlang library: ErlyDTL
>> (http://code.google.com/p/erlydtl/), and a PHP library: Calypso DTL
>>
>> just an FYI that there are at least three other "DTL"s out there, so
>>
On 22 Dez., 17:11, Barry Peder
> In addition to DojoX DTL, there's an Erlang library: ErlyDTL
> (http://code.google.com/p/erlydtl/), and a PHP library: Calypso DTL
>
> just an FYI that there are at least three other "DTL"s out there, so
> DTL would have some company.
>
It would certainly produce
Maluku wrote:
> DTL seems to be too short...
In addition to DojoX DTL, there's an Erlang library: ErlyDTL (
http://code.google.com/p/erlydtl/ ), and a PHP library: Calypso DTL
just an FYI that there are at least three other "DTL"s out there, so
DTL would have some company.
Barry
--~-
Name it whatever you want. It's your bikeshed.
Eric
On Sun, Dec 21, 2008 at 11:55 PM, Maluku wrote:
>
> DTL seems to be too short...
>
> What about "Dotiac" (DjangO Template Interpreter And Compiler), which
> works as a name and an abbreviation.
>
> Maluku
>
>
> >
>
--
Eric Holscher
Web Devel
DTL seems to be too short...
What about "Dotiac" (DjangO Template Interpreter And Compiler), which
works as a name and an abbreviation.
Maluku
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
On Wed, Dec 17, 2008 at 7:25 PM, Maluku wrote:
> So how about the legal side of it? Do I have to include the source
> code for Django in every distribution, since my work is derived from
> your documentation or is just a link enough?
A link is fine.
Jacob
--~--~-~--~~~-
Ok, there is no other module called anywhere like that and even
wikipedia has entry for DTL that comes close.
I have requested to rename the module to DTL or DTL::Template, will
tell you what happens after I hear back.
So how about the legal side of it? Do I have to include the source
code for Dj
On Tue, Dec 16, 2008 at 11:04 PM, Eugene Lazutkin
wrote:
> Some people are blessed with being naturally confused without external
> factors.
Indeed. Documenting that something implements the same format as
Django templates will only confuse people who were already going to be
confused anyway (e.
flo...@gmail.com wrote:
>> Actually, they call their package "dojox.dtl". Their documentation
>> explains that it implements the Django template language.
Yep: http://dojotoolkit.org/book/dojo-book-0-9/part-5-dojox/dojox-dtl
> Even still, at a local Python meetup a little over a month ago,
> som
On 17 Dez., 05:46, "flo...@gmail.com" wrote:
> > Actually, they call their package "dojox.dtl". Their documentation
> > explains that it implements the Django template language.
>
> Even still, at a local Python meetup a little over a month ago,
> someone raised their hand and asked a question
Am 17.12.2008 um 04:11 schrieb Maluku:
> It called it that, because it provides a template language like
> Django, but if this is a problem I will call it something else.
> Apache is a bad example, since many modules that _use_ Apache are also
> in the Apache:: Namespace, like Apache::Template a
> Actually, they call their package "dojox.dtl". Their documentation
> explains that it implements the Django template language.
Even still, at a local Python meetup a little over a month ago,
someone raised their hand and asked a question that went something
like this: "I saw that Django switche
On Tue, Dec 16, 2008 at 10:32 PM, alex.gay...@gmail.com
wrote:
> I am not a legal expert(that's Justin's job ;-) ), but there is a
> precedent for a derivative template language going by the same name,
> Dojo also implements the Django template language and calls it just
> that. That being said,
I am not a legal expert(that's Justin's job ;-) ), but there is a
precedent for a derivative template language going by the same name,
Dojo also implements the Django template language and calls it just
that. That being said, that, amongst other things preceded the
existence of the DSF.
Alex
On
On 17 Dez., 04:23, Malcolm Tredinnick
wrote:
> So the problem that you are now mentioning is that you registered the
> name first and decided to ask check if there might be a problem only
> afterwards. I'm really not trying to be a hard-ass here, but that's not
> a motivating factor. The soluti
I find it interesting that no one has brought up jinja. They did
something that follows django's template syntax, and have still built
up a community. There is also the ruby version which is called liquid
iirc that borrows heavily from django's syntax. Basically, it doesn't
need django in
On Dec 16, 9:32 pm, Justin Bronn wrote:
> > I'm not sure if I work is derived from yours, since I only used the
> > documentation (http://docs.djangoproject.com/en/dev/ref/templates/builtins/)
> > for my work, but I thougt I would better just ask:
>
> > Would you please allow me to use the name D
On Tue, 2008-12-16 at 21:18 -0600, Arien wrote:
> On Tue, Dec 16, 2008 at 8:36 PM, Malcolm Tredinnick
> wrote:
> >
> > All of this is predicated on using the word "Django" in the name, which
> > is the bit I have a problem with.
>
> How is this different from, e.g., any of these?
>
> http://co
Call it Reinhardt, like the surname of Django :-)
On Dec 17, 2008, at 11:18 AM, Arien wrote:
>
> On Tue, Dec 16, 2008 at 8:36 PM, Malcolm Tredinnick
> wrote:
>>
>> All of this is predicated on using the word "Django" in the name,
>> which
>> is the bit I have a problem with.
>
> How is this di
On Tue, 2008-12-16 at 19:11 -0800, Maluku wrote:
> On 17 Dez., 03:36, Malcolm Tredinnick
> wrote:
> > It's very easy: you just don't call it that. Why does it require
> > "change"?
>
> I have discussed this with the perl naming people here:
> http://www.nntp.perl.org/group/perl.modules/2008/12/
On Tue, Dec 16, 2008 at 8:36 PM, Malcolm Tredinnick
wrote:
>
> All of this is predicated on using the word "Django" in the name, which
> is the bit I have a problem with.
How is this different from, e.g., any of these?
http://code.google.com/hosting/search?q=django-
> Choose a different name f
On 17 Dez., 03:36, Malcolm Tredinnick
wrote:
> It's very easy: you just don't call it that. Why does it require
> "change"?
I have discussed this with the perl naming people here:
http://www.nntp.perl.org/group/perl.modules/2008/12/msg63533.html
> Choose a different name for it. If you
> implem
Hi,
> Changing the namespace is not that easy, sadly. But I can make a
> statement that this has nothing to do with the Djangoproject into the
> namespace description. That one can be seen everywhere the name is
> displayed.
Um... I know you registered your namespace with CPAN, but as far as I
ca
On Tue, 2008-12-16 at 18:28 -0800, Maluku wrote:
>
>
> On 17 Dez., 03:15, Malcolm Tredinnick
> wrote:
> > Legalities aside, I'd prefer this wasn't done. It will induce confusion
> > as there will be some people who think it's associated with the Django
> > project. Having a description that sa
> I'm not sure if I work is derived from yours, since I only used the
> documentation (http://docs.djangoproject.com/en/dev/ref/templates/builtins/)
> for my work, but I thougt I would better just ask:
>
> Would you please allow me to use the name Django for my project?
I'm not the one with the f
On 17 Dez., 03:15, Malcolm Tredinnick
wrote:
> Legalities aside, I'd prefer this wasn't done. It will induce confusion
> as there will be some people who think it's associated with the Django
> project. Having a description that says it implements the same
> templating language as XYZ is simply
On Wed, 2008-12-17 at 01:49 +0100, Marc Lucksch wrote:
> I'm currently working on a port of the django template system to perl.
> It is going to be called Django::Template, and it is almost finished,
> some filters missing, cleaning up the documentation and writing tests.
>
> My problem is now:
I'm currently working on a port of the django template system to perl.
It is going to be called Django::Template, and it is almost finished, some
filters missing, cleaning up the documentation and writing tests.
My problem is now:
By calling it Django::Template I'm using your name "Django" to prom
32 matches
Mail list logo
