Just wondering if there are any best-practices documented for mason. I use it daily and seem to end up with a relative hodge-podge (that's the technical term) of components, form handling, etc. I realize this is mostly my own fault abusing both perl and the ability to do inline logic in mason, and want to get better and make more maintainable / usable apps. I really dread going back to old projects for maintenance or updates :)
Is the mason book (in particular chapter 8) a good place to start as far as setting up best practices, or are there other / better / different ways. The varius RoR books I've seen seem to have best practices enforced by the framework itself (or at least general webapp layout), but because of Perl and Mason's ability to do things more than one way, things seem to be a bit less structured (at least for me). Thanks for any pointers you can give me. -- Alan <[EMAIL PROTECTED]> - http://arcterex.net -------------------------------------------------------------------- "Beware of computer programmers that carry screwdrivers." -- Unknown ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
