On Wed, Sep 1, 2010 at 1:24 AM, stefanw wrote:
> Hello,
>
> I guess the most interesting point in this discussion is:
>
>> After a while that I spent time to develop new tags and filters
>> especially for
>> new projects, I began to think a way to implement a template engine
>> that
>> would let m
Yep, and encourage new people to the list to actively contribute!
One thing springs to mind, an agile / crystal process 'game', which
encourages all parties to contribute ideas within a time frame
(usually half an hour to a hour), without prejudice or discouragement.
This gets lots of good
Hello,
I guess the most interesting point in this discussion is:
> After a while that I spent time to develop new tags and filters
> especially for
> new projects, I began to think a way to implement a template engine
> that
> would let me no more write sort of "plugins" like tags and filters, a
On Aug 31, 10:20 am, Luke Plant wrote:
> On Tue, 2010-08-31 at 10:52 +0700, burc...@gmail.com wrote:
I guess Luke is right. I needed something and I implemented it because
I
couldn't find it done as I wanted by no others. A priority was Python
on linux
system (so no windows, .NET, ...) and t
Hi,
On Aug 31, 5:52 am, "burc...@gmail.com" wrote:
> Why you patched Django instead of making a connector so everyone would
> be able to use your template engine without patching django?
This is how the whole thing started. I started a new job and the one
that was
in charge of the projects befor
On Tue, 2010-08-31 at 10:52 +0700, burc...@gmail.com wrote:
> >From the engineering point of view, you did nothing important. In
> fact, I think, you did a bad thing to Django:
> By increasing the number of incompatible template engines for django,
> you fraction the user base of each one, so you
On Sat, Aug 28, 2010 at 10:47 PM, Gabriele Fantini
wrote:
> Hi,
>
> I've just joined this group. The reason is that I've recently
> developed a new django template system (and I'm still working on it)
> and I'm currently using it for my new sites.
> I hope this is the right place to discuss of suc
On Mon, Aug 30, 2010 at 7:31 PM, gabriele wrote:
> At first let me say that I really appreciate your reply! Thanks.
>
> On Aug 30, 6:48 pm, Tim wrote:
> > Alex briefly mentioned the design decision of the template system, but
> > I think it'd be good to emphasize his point-- Django was designed t
At first let me say that I really appreciate your reply! Thanks.
On Aug 30, 6:48 pm, Tim wrote:
> Alex briefly mentioned the design decision of the template system, but
> I think it'd be good to emphasize his point-- Django was designed to
> have various layers, such as the urls, the views, the t
> Pros of this solution:
> * The implementation is clear and short; 250 lines of code do the magic
> All the statements are exactly the python statements
Alex briefly mentioned the design decision of the template system, but
I think it'd be good to emphasize his point-- Django was designed to
> I've just joined this group. The reason is that I've recently
> developed a new django template system (and I'm still working on it)
There's only one Django template system, but there is a lot of others
excellent python template engines (Jinja, Genshi, Mako, etc.), you can
release yours (which l
2010/8/28 Alex Gaynor :
> With all due respect: no. The template system is intentionally not
> Python, this is a strong design decision and I see no compelling
> argument against it here. If you're just generally interested in the
> compilation of Django templates to PYthon (without changing the
On Sat, Aug 28, 2010 at 11:47 AM, Gabriele Fantini
wrote:
> Hi,
>
> I've just joined this group. The reason is that I've recently
> developed a new django template system (and I'm still working on it)
> and I'm currently using it for my new sites.
> I hope this is the right place to discuss of suc
13 matches
Mail list logo
