Just a correction to my previous comments
and then I'll shut up (for a while anyway):
gert> ....I still think python should not be
gert> doing any templating, let the browser handle it....
I agree with the general principles behind gert's comments
that layout should not be mixed with logic or calculation
(within reason). You can "separate" these "concerns" using
whiff configurations generally by adding another layer
of indirection.
For example, you could take the layout out
of the "authorization" logic shown in
my previous example by adding two pages:
logged_in_salutation.whiff and
logged_out_salution.whiff
then use them as follows:
> {{include "who"}}
> {{include "onStatus"}}
> {{using loggedIn}}
> {{include "logged_in_salutation"}}
> {{/using}}
> {{using unknown}}
> {{include "logged_out_salutation"}}
> {{/using}}
> {{/include}}
> {{/include}}
Then your professional visual designers can
layout the salutation files
and the system administrators/programmers can modify the
authentication configuration without interfering
with one-another. I think this is more difficult to
do using other approaches than it is using WHIFF.
I'd also like to note that by using javascript
or XSLT you are not really making the page
language independent -- instead you are becoming
dependent on languages which are sometimes
implemented in different ways on different
browsers. And you are also usually making it harder
for search engines to scrape your pages.
-- Aaron Watters
===
"XSLT: a bad idea, poorly designed,
inconsistently implemented." -- stolen from somewhere
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
