Wichert Akkerman wrote: > Previously cropr wrote: >> I don't use FormEncode. It is based on a very common design mistake >> made by a lot of programmers, who think one can better generate html >> from code. When a graphical artist designs the layout of a web page, >> he uses tools who speak html, css and javascript, but no python (or >> Perl, Java, C++, ...). > > While I agree FormEncode is very far from ideal, your argument does not > make sense to me. FormEncode does not generate markup at all unless > you explicitly tell it to. I do exactly what you describe: hand-written > markup written by a designer, with FormEncode on the backend only > doing decoding and validation.
Not only doesn't it generate markup unless you tell it to, it won't even generate markup if you *do* tell it to ;) -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
