I want Mason 2 to have default file extensions that it facilitates and enforces (though they can be changed via parameters). Here's what I'm thinking of going with:
.mc - top-level component A top-level component can serve as the page component in a request. .mi - internal component An internal component can only be accessed from other components. .mp - pure-perl component A pure-perl component contains only code; it is parsed as if its entire content was within a <%class> block. You do not need to (and are not allowed to) include Mason tags in this component, and it will not produce any output if called. Originally I used ".m" for top-level component, but someone was kind enough to point out that this is used for Objective-C class files, which will become ever more widely used if Apple has its way. :) I've checked all three of the above on http://www.fileinfo.com/ and they don't seem to have any strong associations. Opinions welcome before this sets into stone! Thanks Jon ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
