I don't think it's a matter of enforcement per se. If the right choices are made in development no enforcement is needed to adhere to a convention as it's just the way you do it. Not much enforcement is needed in the custom HM case - it's custom! The developer is stepping out from under the umbrella so to speak and should police themselves.
Some things I'd like to see: Auto discovery of libraries One, or maybe two but no more,ways to locate pages and components The page is the class, the class is the page (there is a common exception to this) The component is the class, the class is the component (see above) Services without HM configuration xml (bring back the <service> tag!)* ASOs without HM configuration xml (introduce an <aso> tag!)* these and perhaps more are already in the dev list in threads with subjects prepended with [T5] I don't claim to know at this time how these would be implemented. Anybody want to add to the list above? Geoff *while xml is going away (i think) for pages and components in T5 - I'm assuming that it will stay for applications and libraries On 6/15/06, James Carman <[EMAIL PROTECTED]> wrote:
So, what kind of conventions do you have in mind for Tapestry to enforce? -----Original Message----- From: Geoff Longman [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 3:48 PM To: Tapestry users Subject: Re: custom namespace Geez, I need to socialize more here. We have 14 developers. Geoff On 6/15/06, Geoff Longman <[EMAIL PROTECTED]> wrote: > I wonder how hard it is to break from the conventions in Rails. I > would expect that with Tapestry+HM it would be pretty easy. > > Tapestry, in some cases, has too many conventions. Look at the rules > for finding pages and components. If you add em all up there are more > than 10. (10!!) > > We, and I'm sure everyone does this, have chosen the case that works > best for us(plus we are using Tap 3 and have Spindle - cringe - duck) > and made that the convention in the office. All of our 9 developers do > the same thing. We have even made conventions on how we handle the > rewind, use javascript in our pages, etc. With 160+ pages it's pretty > easy for any developer to go in and fix a bug in a page they didn't > write. We had one person, who has since moved on, who decided not to > follow the office conventions and it has been a nightmare fixing > issues in that code. > > So, yes I'm very pro convention. > > Geoff > > On 6/15/06, James Carman <[EMAIL PROTECTED]> wrote: > > Nothing's wrong with conventions. Tapestry already uses them somewhat (page > > names map to classnames in the default page package). Rails gets a *lot* > > done by just using conventions. > > > > -----Original Message----- > > From: Geoff Longman [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 15, 2006 3:30 PM > > To: Tapestry users > > Subject: Re: custom namespace > > > > COP cool acronym. What is wrong with conventions? (I have never used Rails) > > > > Geoff > > > > On 6/15/06, James Carman <[EMAIL PROTECTED]> wrote: > > > So, you want Tapestry to switch to convention-oriented programming (a la > > > Rails)? > > > > > > > > > -----Original Message----- > > > From: Bryan Lewis [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, June 15, 2006 3:20 PM > > > To: Tapestry users > > > Subject: Re: custom namespace > > > > > > +1 for that rant. > > > > > > > > > Geoff Longman wrote: > > > > > > > Good God No! > > > > > > > > While I love the idea of auto discovery of libraries, every time I see > > > > a quick suggestion to use Hivemind I cringe. > > > > > > > > IMO HM is *required* to do too many everyday things in T4. HM should > > > > be relegated to use when the *implementation of the runtime* needs to > > > > be changed or enhanced because a convention doesn't handle a > > > > particular case. A normal everyday user should be able to build > > > > libraries, have full featured ASO's, and build services without ever > > > > writing a line of HM config. > > > > > > > > That puts a lot more pressure on the committers to identify the > > > > everyday tasks and find intelligent conventions for users to do > > > > something without writing HM code. That doesn't mean HM is out of the > > > > mix, it's just out of sight and available for those 1% cases where you > > > > just have to make Tap behave differently from the convention. Really, > > > > in a perfect world the Tapestry docs would make no reference to HM > > > > except in an appendix. > > > > > > > > end of rant! > > > > > > > > Geoff > > > > > > > > On 6/15/06, James Carman <[EMAIL PROTECTED]> wrote: > > > > > > > >> It would be nice if the component libraries could add themselves to > > > >> the mix > > > >> via a HiveMind contribution. Of course, they would allow "users" to > > > >> override their default namespace via a symbol override contribution or > > > >> something. That's the way I'd do it. > > > >> > > > >> -----Original Message----- > > > >> From: Norbert Sándor [mailto:[EMAIL PROTECTED] > > > >> Sent: Thursday, June 15, 2006 12:27 PM > > > >> To: Tapestry users > > > >> Subject: Re: custom namespace > > > >> > > > >> I use many such component libraries which means that because of this > > > >> issue, many libraries must be specified "by hand". > > > >> Not a big problem, just tried to avoid it :) > > > >> > > > >> Regards, > > > >> Norbi > > > >> > > > >> Geoff Longman wrote: > > > >> > Yes, that's true. But is that really a problem? Contrib has the same > > > >> > issue. > > > >> > > > > >> > Geoff > > > >> > > > > >> > On 6/15/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: > > > >> >> Thanks! > > > >> >> > > > >> >> This means that I must force the user of my component library to > > > >> define > > > >> >> my library with a fix alias in the .application file. > > > >> >> > > > >> >> Regards, > > > >> >> Norbi > > > >> >> > > > >> >> Jesse Kuhnert wrote: > > > >> >> > You mean like contrib or tacos? I think the namespace name can > > > >> be tied > > > >> >> > to a > > > >> >> > .library file via your .application configuration. (this I'm > > > >> less sure > > > >> >> > of as > > > >> >> > the best solution) > > > >> >> > > > > >> >> > On 6/14/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: > > > >> >> >> > > > >> >> >> Hi, > > > >> >> >> > > > >> >> >> By default there are 2 namespaces: framework and application. > > > >> >> >> How can I define my own, custom namespace? > > > >> >> >> > > > >> >> >> Regards, > > > >> >> >> Norbi > > > >> >> >> > > > >> >> >> > > > >> --------------------------------------------------------------------- > > > >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> >> >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> >> >> > > > >> >> >> > > > >> >> > > > > >> >> > > > > >> >> > > > > >> >> > > > >> > > ------------------------------------------------------------------------ > > > >> >> > > > > >> >> > No virus found in this incoming message. > > > >> >> > Checked by AVG Free Edition. > > > >> >> > Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: > > > >> >> 2006.06.12. > > > >> >> > > > > >> >> > > > >> >> > > --------------------------------------------------------------------- > > > >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> >> > > > >> >> > > > >> > > > > >> > > > > >> > > > >> --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > >> > > > >> > > > >> --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > >> > > > >> > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > The Spindle guy. http://spindle.sf.net > > Blog: http://jroller.com/page/glongman > > Other interests: http://www.squidoo.com/spaceelevator/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > The Spindle guy. http://spindle.sf.net > Blog: http://jroller.com/page/glongman > Other interests: http://www.squidoo.com/spaceelevator/ > -- The Spindle guy. http://spindle.sf.net Blog: http://jroller.com/page/glongman Other interests: http://www.squidoo.com/spaceelevator/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- The Spindle guy. http://spindle.sf.net Blog: http://jroller.com/page/glongman Other interests: http://www.squidoo.com/spaceelevator/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
