On Fr, 2006-08-11 at 03:54 -0400, [EMAIL PROTECTED] wrote: > Does page designer need to study Mason?Or the perl developer would > study Mason? > Sorry for the low-level question since I'm new to Mason and was reading > the book of 'Embedding Perl In Html With Mason' now.
That depends on how much you separate your logic and design. You could use Mason and have your layout and logic together in one file but this makes it harder for the web designer because he/she is dealing with too much Perl and it's also a bad thing for the Perl developer because he/she will interfere with the web developer. So the best way IMHO is to have your logic in standalone Perl modules (which can act on their own without the need of an Apache webserver or Mason) and Mason components with the HTML and an <%init> block in which you pull the neccessary data using your logic-containing Perl modules. In any case it won't hurt if your web designer knows a bit of Perl :) If you really want a strict separation of your model (data), logic and view (layout) without the hassle of setting up the separation glue all for yourself, I'd suggest taking the Catalyst route - maybe with Mason as your templating engine. HTH, Toby ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
