On Thu, May 27, 2010 at 4:36 PM, Tom X. Tobin wrote:
> On Thu, May 27, 2010 at 7:36 AM, Tom Evans wrote:
>> Most PHP templating languages allow you to do things that are by
>> design not in django's templating, for example in Smarty, one can
>> assign new variables on the fly in the template, and
On Thu, May 27, 2010 at 7:36 AM, Tom Evans wrote:
> Most PHP templating languages allow you to do things that are by
> design not in django's templating, for example in Smarty, one can
> assign new variables on the fly in the template, and even do crazy
> stuff like call functions that take argume
My apologies, I did not intend to trigger an offtopic discussion, even
a semi-related one. My intent was merely to point out that Django's
templating system is far from perfect, and that improving it is
definitely a goal of Django, even if we reject a particular change
that may appear to be for th
On Thursday 27 May 2010 13:33:10 Tom Evans wrote:
> I never claimed it wasn't; it was stipulated that Django's template
> system wipes the floor with all others, and it is inconceivable to
> think more favourably of a different system.
I never said that Django wipes the floor with "all others" - I
I never claimed it wasn't; it was stipulated that Django's template
system wipes the floor with all others, and it is inconceivable to
think more favourably of a different system.
I was trying to point out that there are features which are available
in other template languages, which people may co
The inability to assign variables is an intentional design decision; one of
Django's core tenets is that business logic and presentational logic should
be separated. The template language was crafted to provide non-programmers
(front-end developers and designers) the ability to work directly on
tem
On Thu, May 27, 2010 at 12:20 PM, Luke Plant wrote:
> On Thursday 27 May 2010 03:21:43 Charlie Nolan wrote:
>
>> I'm all for streamlining the template system, because I think it's
>> one of the less-intuitive aspects of Django at the moment (I think
>> PHP has us beat, and that's really sad)
>
> C
On Thursday 27 May 2010 03:21:43 Charlie Nolan wrote:
> I'm all for streamlining the template system, because I think it's
> one of the less-intuitive aspects of Django at the moment (I think
> PHP has us beat, and that's really sad)
Care to elaborate? From my perspective Django's templates wipe
We're not changing the template syntax. Full stop.
If you don't like Django's syntax, I'm sorry. There are literally
dozens of other template languages; I'm sure one will fit anyone's
personal needs and style.
Jacob
--
You received this message because you are subscribed to the Google Groups
"
Lazy *is* good. We're too lazy to change the template system without
a good reason, and so far, I haven't heard one. The current syntax is
terse and not really any more difficult to type than the
alternative(s) you've proposed. And it's not likely to appear in the
templated document, which is a
@Luke: I haven't used custom template tags, so I don't know the effect
that switching to {{}} would do to that. this sounds like the first
real issue that could just kill it.
@Josh: it's true that my fingers won't wither away from typing {%
stuff %}.
i guess i'll spend more time studyin' pydev.
I'm mostly just a user, and maybe I'm being dense, here, but I just
don't see the point of this change. Why is {%%} any harder a syntax
than {{{}}} is? Is it an issue of key placement (% is shift-5 for US
keyboards)? And why would you type {%%} and then go back to insert
the keyword when you can
Why not just type the opening {%, then the stuff that goes inside, then the
closing %}. Seems like that would be easier for everybody (baring using a
reasonable editor or learning how to use yours properly).
--
Josh Ourisman
j...@joshourisman.com
301-244-9674
On May 26, 2010 3:27 PM, "Daniel" w
Hello,
Also keep in mind that the triple brackets introduce their own set of
issues. For example, in LaTeX templates I've seen::
\title{{{ publication.title }}}
Which works perfectly fine right now. Would this work under your proposal?
Cheers,
Mike
On Wed, May 26, 2010 at 6:28 PM, Daniel w
Hello Gregor,
Thanks for taking a look. My rationale is, "Why change all the
editors in the world for something that can be simplified with an
easier syntax?"
All of the previous code using the curly-modulo syntax -- {%%} would
still be functional for as long as the core developers chose to
supp
On Wednesday 26 May 2010 20:24:31 Daniel wrote:
> Hi, I was just referred here with a suggestion I posted on the
> django ticket tracker. I've been studying the way we do template
> tags, and had a suggestion for how to revise them to make them a
> bit easier. I was thinking that out of the tags, I
Hi Daniel,
I think your suggestion might make sense for some people using
autoclosing brackets etc. But having better support for writing
templatetags is just an issue with a text editor which might be
configurable and easy to write a plugin or using a snippet completion
to make life easier for yo
Hi, I was just referred here with a suggestion I posted on the django
ticket tracker. I've been studying the way we do template tags, and
had a suggestion for how to revise them to make them a bit easier. I
was thinking that out of the tags, I like the variable syntax the best
-- {{ variable.attrib
18 matches
Mail list logo
