On Sat, Jul 4, 2009 at 7:37 PM, Aaron Watters<[email protected]> wrote: > >> Just curious as to why you had invent another templating language when >> there are already existing ones that you can extend? SimpleTAL is >> pretty popular: >> >> http://www.owlfish.com/software/simpleTAL/about.html > > I have nothing against other template languages and you can use other > template languages with WHIFF. > > The WHIFF configuration template interpreter has the advantages > > 1) It is tightly bound to WSGI features. > 2a) A configuration template defines a WSGI app with > any number of named arguments. > 2b) It permits "includes" for WSGI middlewares and apps > with any number of named arguments which may be > defined by other templates either embedded or included. > 3) It doesn't overload the HTML <tag> syntax which always > leads to unreadable catastrophe in my experience.
I like the Django templating system for pretty much the same reasons you enumerated above. I used to use Zope, hated it but loved TAL and METAL. Tried using SimpleTAL with Django but #3 was definitely the clincher for me. It's just really hard on the eyes having to sort out your template tags from the rest of the HTML soup even with syntax highlighting. -- Best Regards, Nimrod A. Abing W http://arsenic.ph/ W http://preownedcar.com/ W http://preownedbike.com/ W http://abing.gotdns.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
