My understanding is that this is just the sort of thing that the template system was designed for. You're supposed to develop a new set of templates, put them under a different directory, and I think specify a theme in the template tags. The theme points the template mechanism to the new directory, where you can have much simpler templates optimized for WAP or whatever. Things may have changed, but that's what I remember from the original versions.
Re-doing all of the templates may be a pain but there's no other way to make sure that they're optimized. You could run some automated thing but IHMO you're better off hand-optimizing them and using them instead of the normal templates. Any other approach would lead to unpredictable results. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Samuel Mota Sent: Wednesday, January 14, 2004 5:58 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Compress output Hi ... This question is not direct related to WW but I hope find some help ... My application will be used on wireless devices, so, we are charged by traffic and I really need to compress the output ... wich is the better approach for this? the WW templates and my view are idented and organized with so many spaces and tabs, at least I'd like to remove then :) ... ideas? thanks + Samuel G. Mota + [EMAIL PROTECTED] + 55 (11) 4417 7093 + Business Application Dpt. + Netset Serviços em Tecnologia + a Hypercom Company + http://www.hypercom.com ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
