On May 9, 12:56 pm, Drew Smathers <[email protected]> wrote:
> On Sat, May 9, 2009 at 7:32 AM, Aaron Watters <[email protected]> wrote:
>
> [snip]
>
> > {{include "editForm"}}
> > {{set-id Name}}"{{get-cgi Name/}}"{{/set-id}}
> > {{set-id Title}}"{{get-cgi Title/}}"{{/set-id}}
> > {{set-id Summary}}"{{get-cgi Summary/}}"{{/set-id}}
> > {{set-id TextSource}}"{{get-cgi Text/}}"{{/set-id}}
> > {{/include}}
>
> I must say, that looks very much like a JSP include. In fact your
> "configuration template language" seems to be a mirror JSP with
> different syntax.
Only on the surface. Jsp include parameters are not dynamic. Whiff
include params
are completely dynamic (they are pages -- the highest level
construct).
> Even Java developers are moving away from JSP
> because it has terrible syntax (<c:var out="thingy"/>??) and it's more
> or less welded into the web server implementation making it worthless
> for general templating.
I hate jsps, but a lot of the other java based alternatives are even
worse -- jsf, rsf, etcetera. It's a nightmare. I don't see the
similarity
with whiff aside from the use of the word "include".
> Btw, why are you using the WSGI environment
> as a template context?
It's one of several approaches that are possible. There are also
"use/require/using" parameters.
-- Aaron Watters
===
ymmv rsn afaik imho fwiw (rotfl)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---
