On Nov 2, 6:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
>
> Learning the handful of constructs is the same as learning a handful of
> API calls. The same goes for idiosyncrasies of e.g. inserting
> sub-templates or dealing with repeating content.
I'm not sure I agree with you.
1 - the c
On approximately 11/3/2008 2:51 PM, came the following characters from
the keyboard of has:
On 3 Nov 2008, at 18:18, Glenn Linderman wrote:
On approximately 11/3/2008 12:20 AM, came the following characters
from the keyboard of has:
On 2 Nov, 14:06, Tino Wildenhain <[EMAIL PROTECTED]> w
On Nov 5, 6:03 am, lkcl <[EMAIL PROTECTED]> wrote:
>
> * pyjamas (http://pyjs.org) - this is treating the web page and the
wow. I had never heard of it, but it is _damned_ impressive. THANK
YOU. I'm joining the club for my next webdev project!
rock on.
--
http://mail.python.org/mailman/listinfo/
On Nov 2, 11:19 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> Push-style though enhances the risk of mixing program logic with
> presentation-logic (as simple print-statements do), and makes it a
> precondition that anybody who's supposed to tinker with the softare
> needs to be knowledgable
In article <[EMAIL PROTECTED]>,
Tino Wildenhain <[EMAIL PROTECTED]> wrote:
.
.
.
>Mini languages is the correct term. And yes they have their
>purpose. (Think of SQL for example).
.
On 3 Nov 2008, at 18:18, Glenn Linderman wrote:
> On approximately 11/3/2008 12:20 AM, came the following characters
> from the keyboard of has:
>> On 2 Nov, 14:06, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
>>
>>> "$attr.title$
>>> $if(attr.active)$
>>> $attr.submenu:menuItem()$
>>> $endif$"
>>>
On approximately 11/3/2008 12:20 AM, came the following characters from
the keyboard of has:
On 2 Nov, 14:06, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
An opposite approach to this form of dynamic HTML production is called
push-style templating, as coined by Terence Parr:
Hm.
"$att
On 2 Nov, 14:06, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
> > An opposite approach to this form of dynamic HTML production is called
> > push-style templating, as coined by Terence Parr:
>
> Hm.
>
> "$attr.title$
> $if(attr.active)$
> $attr.submenu:menuItem()$
> $endif$"
>
> This looks ugly to m
In article <[EMAIL PROTECTED]>,
Terrence Brannon <[EMAIL PROTECTED]> wrote:
>
>The most common way of dynamically producing HTML is via template
>engines like genshi, cheetah, makotemplates, etc.
>
>These engines are 'inline' --- they intersperse programming constructs
>with the HTML document itse
Hi,
first a bit of background: I've been using push-style templating in the
form of XMLC before. Actually, I've been a core-developer of
BarracudaMVC, a java web-framework that for rendering massively relied
on XMLC and has been driving XMLC's development (at least used to).
And I liked it.
Tino Wildenhain wrote:
Terrence Brannon wrote:
Tino Wildenhain wrote:
An opposite approach to this form of dynamic HTML production is called
push-style templating, as coined by Terence Parr:
Hm.
"$attr.title$
$if(attr.active)$
$attr.submenu:menuItem()$
$endif$"
This looks ugly to me
On 2 Nov, 15:25, Terrence Brannon <[EMAIL PROTECTED]> wrote:
>
> I like the approach of my own HTML::Seamstress --- object-oriented Perl
> and knowledge of an object-oriented tree-rewriting library is all you need:
> http://search.cpan.org/~tbone/HTML-Seamstress-5.0b/lib/HTML/Seamstres
The Pyt
Terrence Brannon wrote:
Tino Wildenhain wrote:
An opposite approach to this form of dynamic HTML production is called
push-style templating, as coined by Terence Parr:
Hm.
"$attr.title$
$if(attr.active)$
$attr.submenu:menuItem()$
$endif$"
This looks ugly to me.
It looks ugly to me too
Tino Wildenhain wrote:
An opposite approach to this form of dynamic HTML production is called
push-style templating, as coined by Terence Parr:
Hm.
"$attr.title$
$if(attr.active)$
$attr.submenu:menuItem()$
$endif$"
This looks ugly to me.
It looks ugly to me too.
Why not just using wel
Terrence Brannon wrote:
Hello,
The most common way of dynamically producing HTML is via template
engines like genshi, cheetah, makotemplates, etc.
These engines are 'inline' --- they intersperse programming constructs
with the HTML document itself.
An opposite approach to this form of dynamic
Hello,
The most common way of dynamically producing HTML is via template
engines like genshi, cheetah, makotemplates, etc.
These engines are 'inline' --- they intersperse programming constructs
with the HTML document itself.
An opposite approach to this form of dynamic HTML production is called
16 matches
Mail list logo
