Are CamelCase page names and URLs the standard with Tapestry applications? I'm used to doing more lowercase things, for example:
http://server/app/userList.html I'm even starting to warm up to doing things all lowercase: http://server/app/userlist.html However, according to HLS, CamelCase is the recommended (and preferred) way of doing things w/in the Tapestry community. http://server/app/UserList.html Is that true? This seems odd to me. I can understand that using an uppercase first letter makes everything match, but it leads to non-standard URLs, no? I guess Tapestry has never been too keen on pretty URLs, so maybe this isn't an issue for most users? Background: ---------------------- Howard did a thorough review of the Tapestry code in AppFuse about 6 months ago. He sent me a private e-mail, which I posted as a JIRA issue: http://issues.appfuse.org/browse/APF-404 We've since broken up this issue into several subtasks, and the one I'm referring to in particular can be found at: http://issues.appfuse.org/browse/APF-499 <description> In Tapestry, the established convention is that page names are CamelCase. Further, the XML specification (.page file), HTML template and Java class should all be named the same. Likewise for components. </description> If UserList.html is the preferred standard among Tapestry users, we'll follow it - I just want to make sure that Howard and the community agree on this one. Thanks, Matt -- View this message in context: http://www.nabble.com/CamelCase-page-names-URLs-in-Tapestry-tf2893433.html#a8083998 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
