[Tapestry-developer] Vote: Renames

[Howard M. Lewis Ship]

Ok, maybe I get a little crazy just before a beta, but I'm suddenly overcome with the desire to rename a few pooly named items in the Tapestry world.  I really am starting to think of 2.2 as the "ready from primetime" release, the one that's going to start getting a really big splash.  That's why I was suddenly siezed by the need to hook OGNL in.   What does the community think of the following component renames:   Page -> PageLink  a little longer, but clearly defines it as a link to a page, distinct from a different concept, page (i.e., IPage) Service -> ServiceLink Direct -> DirectActionLink Action -> DynamiclActionLink    InsertWrapped -> InsertBody  I want to get away from the awkward them "wrapped elements", it's confusing, and "body" (as in a SGML element's body) is very clear.   Obviously, I would leave the existing names in place for 2.2, for backwards compatibility.   Even beyond then, you could simply add aliases to your application specification.     ---- Howard Lewis Ship [EMAIL PROTECTED] http://tapestry.sf.net