On Jul 5, 12:41 pm, AchipA <[email protected]> wrote: > On Jul 5, 2:29 am, gert <[email protected]> wrote: > > > The difference is, my raw data coming from python never changes, if > > the client is a phone instead of a monitor or a device that blind > > people use. If you use a template language written in python, your > > application code gets multiplied by 3 and all responsibility will be > > on the python programmer for every device or client. > > I'll have to ask again, in what way is this different from using > XSLT ?
None, same principal. Python server engineer spits out raw xml data, client constructor worker display's it using his xslt tools. Engineer does not have to know anything about xslt, construction worker does not have to know anything about python. I just prefer json over xml > Besides, the 'raw data coming from python' should not change > regardless of your templating engine if the raw data is adequate - it > is the templating engine's job to convert the data to a user- > presentable format. If someone puts complex code in the templates, or > html in the code, it's the programmer's error, it just means he's > abusing the template system, not that templating is flawed. I understand wat you mean, but I stile think python should not be doing any templating, let the browser handle it. As long client browsers do not use python instead of js or xslt, python programmers should stay away and let the html or xslt pro's handle it. When the server does not produce raw xml, xslt workers are pulling there hair out. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
