Re: What if "Page" was removed from page names?
Hi there -- Extending what Andy is talking about - the reason I like the Tacos solution is: 1. Developers can refactor without breaking bookmarks 2. Managers can let developers refactor without having to *worry* that the (junior) developers are going to break bookmarks. 3. A meaningful name for the developers may be confusing to the end user. For example, "EditWebsiteMessageEndPoints" v. "EditMyPages" On Wed, Jun 25, 2008 at 10:53 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote: > Yep, uses a tiny annotation scanner lib that only scans > WEB-INF/classes (by default) at app startup time. > > Can't really tell how this messes up with synthetic pages > cause i don't quite know what you have in mind... in our > current T4 project, we've been using synthetic components > though which (i believe) is an equally powerful concept and > has the benefit of not messing with page names. > > -- Patrick Moore Amplafi 650-207-9792 "copy/paste" blog : http://www.sworddance.com/blog
Re: What if "Page" was removed from page names?
Hi Howard
I'm experimenting with this, I'm trying to get it to work for what it
could be Trails 2, and it was actually pretty easy to do.
I just needed to create a coercion for classes, and then provide
default pages: ListPage, EditPage and ViewPage. Way easier than what I
needed to do to make it work for T4.
Now I'm stuck with providing editors for relationships:
http://www.nabble.com/Contributing-to-BeanBlockSource-and-HibernateEntityValueEncoder-td17642661.html
Saludos.
Alejandro.
On Wed, Jun 25, 2008 at 8:05 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Eventually, I want tapestry-hibernate to hook in to thing such that,
> if you don't define a page named "edit/blog" (for entity Blog), it
> provides one for you. Ditto for "add/blog", 'view/blog" and
> "search/blog". But that's for 5.1 or beyond.
>
> On Wed, Jun 25, 2008 at 10:53 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
>> Yep, uses a tiny annotation scanner lib that only scans
>> WEB-INF/classes (by default) at app startup time.
>>
>> Can't really tell how this messes up with synthetic pages
>> cause i don't quite know what you have in mind... in our
>> current T4 project, we've been using synthetic components
>> though which (i believe) is an equally powerful concept and
>> has the benefit of not messing with page names.
>>
>> On 6/25/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>>> I haven't been keeping up with what's going on in T4, alas.
>>>
>>> This would imply that you must load/scan all pages at application
>>> startup? Otherwise, how could you know which aliases exist for which
>>> pages? This is something I've been trying to avoid for T5, as it will
>>> ultimately get in the way of synthetic pages (that I have planned for
>>> more Trails-like functionality in tapestry-hibernate).
>>>
>>>
>>> On Wed, Jun 25, 2008 at 7:16 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
>>> > I'd really like to suggest an approach similar to the UriTemplate
>>> annotation for
>>> > T4 pages that's included in tacos...
>>> >
>>> > See
>>> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
>>> >
>>> > It even supports aliases, so, no worries if you decide to change names
>>> > and still want to old bookmarks - just use:
>>> >
>>> > @UriTemplate(value="index", alias = {"home", "default"})
>>> > public class Home { ... }
>>> >
>>> >
>>> > On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
>>> >> Shouldn't that be up to the developer (or whoever decides on the
>>> >> URLs)? If you don't want the page suffix, why not just name the page
>>> >> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
>>> >> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
>>> >> convention over configuration, but here I feel some arbitrary rule
>>> >> would be unnecessarily imposed on the developer.
>>> >>
>>> >> Just my two cents,
>>> >>
>>> >>
>>> >> Lutz
>>> >>
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
>>> > Tapestry / Tacos developer
>>> > Open Source / JEE Consulting
>>> >
>>> > -
>>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> > For additional commands, e-mail: [EMAIL PROTECTED]
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>>
>>> Howard M. Lewis Ship
>>>
>>> Creator Apache Tapestry and Apache HiveMind
>>>
>>> -
>>>
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
>> Tapestry / Tacos developer
>> Open Source / JEE Consulting
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> -
> 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]
Re: What if "Page" was removed from page names?
Eventually, I want tapestry-hibernate to hook in to thing such that,
if you don't define a page named "edit/blog" (for entity Blog), it
provides one for you. Ditto for "add/blog", 'view/blog" and
"search/blog". But that's for 5.1 or beyond.
On Wed, Jun 25, 2008 at 10:53 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
> Yep, uses a tiny annotation scanner lib that only scans
> WEB-INF/classes (by default) at app startup time.
>
> Can't really tell how this messes up with synthetic pages
> cause i don't quite know what you have in mind... in our
> current T4 project, we've been using synthetic components
> though which (i believe) is an equally powerful concept and
> has the benefit of not messing with page names.
>
> On 6/25/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>> I haven't been keeping up with what's going on in T4, alas.
>>
>> This would imply that you must load/scan all pages at application
>> startup? Otherwise, how could you know which aliases exist for which
>> pages? This is something I've been trying to avoid for T5, as it will
>> ultimately get in the way of synthetic pages (that I have planned for
>> more Trails-like functionality in tapestry-hibernate).
>>
>>
>> On Wed, Jun 25, 2008 at 7:16 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
>> > I'd really like to suggest an approach similar to the UriTemplate
>> annotation for
>> > T4 pages that's included in tacos...
>> >
>> > See
>> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
>> >
>> > It even supports aliases, so, no worries if you decide to change names
>> > and still want to old bookmarks - just use:
>> >
>> > @UriTemplate(value="index", alias = {"home", "default"})
>> > public class Home { ... }
>> >
>> >
>> > On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
>> >> Shouldn't that be up to the developer (or whoever decides on the
>> >> URLs)? If you don't want the page suffix, why not just name the page
>> >> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
>> >> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
>> >> convention over configuration, but here I feel some arbitrary rule
>> >> would be unnecessarily imposed on the developer.
>> >>
>> >> Just my two cents,
>> >>
>> >>
>> >> Lutz
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> > --
>> > Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
>> > Tapestry / Tacos developer
>> > Open Source / JEE Consulting
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>>
>>
>> --
>>
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> -
>>
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
Yep, uses a tiny annotation scanner lib that only scans
WEB-INF/classes (by default) at app startup time.
Can't really tell how this messes up with synthetic pages
cause i don't quite know what you have in mind... in our
current T4 project, we've been using synthetic components
though which (i believe) is an equally powerful concept and
has the benefit of not messing with page names.
On 6/25/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> I haven't been keeping up with what's going on in T4, alas.
>
> This would imply that you must load/scan all pages at application
> startup? Otherwise, how could you know which aliases exist for which
> pages? This is something I've been trying to avoid for T5, as it will
> ultimately get in the way of synthetic pages (that I have planned for
> more Trails-like functionality in tapestry-hibernate).
>
>
> On Wed, Jun 25, 2008 at 7:16 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
> > I'd really like to suggest an approach similar to the UriTemplate
> annotation for
> > T4 pages that's included in tacos...
> >
> > See
> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
> >
> > It even supports aliases, so, no worries if you decide to change names
> > and still want to old bookmarks - just use:
> >
> > @UriTemplate(value="index", alias = {"home", "default"})
> > public class Home { ... }
> >
> >
> > On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
> >> Shouldn't that be up to the developer (or whoever decides on the
> >> URLs)? If you don't want the page suffix, why not just name the page
> >> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
> >> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
> >> convention over configuration, but here I feel some arbitrary rule
> >> would be unnecessarily imposed on the developer.
> >>
> >> Just my two cents,
> >>
> >>
> >> Lutz
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
> > Tapestry / Tacos developer
> > Open Source / JEE Consulting
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
>
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> -
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
I have a slightly clumsy way of accomplishing what I want today,
without changing the framework.
Instead of creating BlogPage, I create class blog.BlogIndex and
blog/BlogIndex.tml. I can then refer to this page as "blog/index" and
it appears as "/blog" in URLs, which is what I want.
On Wed, Jun 25, 2008 at 9:56 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> I haven't been keeping up with what's going on in T4, alas.
>
> This would imply that you must load/scan all pages at application
> startup? Otherwise, how could you know which aliases exist for which
> pages? This is something I've been trying to avoid for T5, as it will
> ultimately get in the way of synthetic pages (that I have planned for
> more Trails-like functionality in tapestry-hibernate).
>
> On Wed, Jun 25, 2008 at 7:16 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
>> I'd really like to suggest an approach similar to the UriTemplate annotation
>> for
>> T4 pages that's included in tacos...
>>
>> See
>> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
>>
>> It even supports aliases, so, no worries if you decide to change names
>> and still want to old bookmarks - just use:
>>
>> @UriTemplate(value="index", alias = {"home", "default"})
>> public class Home { ... }
>>
>>
>> On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
>>> Shouldn't that be up to the developer (or whoever decides on the
>>> URLs)? If you don't want the page suffix, why not just name the page
>>> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
>>> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
>>> convention over configuration, but here I feel some arbitrary rule
>>> would be unnecessarily imposed on the developer.
>>>
>>> Just my two cents,
>>>
>>>
>>> Lutz
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>
>>
>> --
>> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
>> Tapestry / Tacos developer
>> Open Source / JEE Consulting
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
I haven't been keeping up with what's going on in T4, alas.
This would imply that you must load/scan all pages at application
startup? Otherwise, how could you know which aliases exist for which
pages? This is something I've been trying to avoid for T5, as it will
ultimately get in the way of synthetic pages (that I have planned for
more Trails-like functionality in tapestry-hibernate).
On Wed, Jun 25, 2008 at 7:16 AM, Andreas Andreou <[EMAIL PROTECTED]> wrote:
> I'd really like to suggest an approach similar to the UriTemplate annotation
> for
> T4 pages that's included in tacos...
>
> See
> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
>
> It even supports aliases, so, no worries if you decide to change names
> and still want to old bookmarks - just use:
>
> @UriTemplate(value="index", alias = {"home", "default"})
> public class Home { ... }
>
>
> On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
>> Shouldn't that be up to the developer (or whoever decides on the
>> URLs)? If you don't want the page suffix, why not just name the page
>> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
>> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
>> convention over configuration, but here I feel some arbitrary rule
>> would be unnecessarily imposed on the developer.
>>
>> Just my two cents,
>>
>>
>> Lutz
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: What if "Page" was removed from page names?
+1 for this keep it simple and clear! Max -Ursprüngliche Nachricht- Von: Don Ryan [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 25. Juni 2008 13:08 An: Tapestry users Betreff: Re: What if "Page" was removed from page names? On 25 Jun 2008, at 01:12, Filip S. Adamsen wrote: > As long as it's configurable, I'm fine with it. :) Except you lose some of the intrinsic simplicity of convention over configuration when you decide to offer both. Note that, depending on how it's implemented, this change need not break any existing Tapestry 5 applications. If the page class has a -Page suffix, then Tapestry would map to that. (You might have to throw an exception if Foo and FooPage both existed under the pages package hierarchy.) On the naming issue itself, I think it would be a positive development. I think the historical convention of using entity-like names for pages is a regrettable fuzziness. I've shown Tapestry to some undergraduate students and a common beginner's mistake is to put code in a page class that really belongs in an entity class. The naming didn't help there. I'm sure something similar would apply with junior developers in a software house. There's very little point in making the hurdles any higher for people learning their craft. To really set the cat amongst the pigeons (and infuriate the keystroke tax collectors), I think a similar mapping of a -Component suffix would be good for components (again optional). Although it's unfortunately a longer suffix, the conceptual clarity would probably be worth it. (Why refer to something as, say, an "account component" when discussing it but refuse to actually call it that. Because it's too long?) Lastly, I don't think I would go along with Hugo's idea of list of optional suffixes. I can't imagine any sensible suffix for pages and components other than -Page and -Component. (Although that could just be my limited imagination.) :-) Don. This message has been scanned for content and viruses by the DIT Information Services E-Mail Scanning Service, and is believed to be clean. http://www.dit.ie - 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]
Re: Re: What if "Page" was removed from page names?
Hi list,
to answer Howard´s question, yes I would like that feature. Exactly as
described. At the moment I prefix my page class names with the package name. I
am not happy with that. I´d prefer to suffix them with "Page".
And my opinion to the discussion whether generation of urls should be
configurable. I think it should NOT be configurable. The mechanism is good as
it is.
1.) The generated urls serve the important purposes like being bookmarkable, no
request-parameters etc. That is what is important about an url.
2.) I could imagine matching a class name to a small set of predefined values
might be a bit easier than to something dynamically configurated. This might
even ipmacht performance. Although surely not much and only at startup time. I
haven´t looked into that part of the source code though.
3.) None of my customers really cares about how urls look like. Let it be
"blogger", "myblogger" or "mybloggerpage". I am sure if you asked your
customers, they would not be able to tell what the url is. If we are honest,
the desire to make url generation configurable ist to give us developers
something else to play with.
Regards, nillehammer
- original Nachricht ----
Betreff: Re: What if "Page" was removed from page names?
Gesendet: Mi, 25. Jun 2008
Von: Andreas Andreou<[EMAIL PROTECTED]>
> I'd really like to suggest an approach similar to the UriTemplate annotation
> for
> T4 pages that's included in tacos...
>
> See
> http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations
> /src/java/net/sf/tacos/rest
>
> It even supports aliases, so, no worries if you decide to change names
> and still want to old bookmarks - just use:
>
> @UriTemplate(value="index", alias = {"home", "default"})
> public class Home { ... }
>
>
> On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
> > Shouldn't that be up to the developer (or whoever decides on the
> > URLs)? If you don't want the page suffix, why not just name the page
> > "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
> > "mypage"? Would I have to name the page "MyPagePage"? I'm all for
> > convention over configuration, but here I feel some arbitrary rule
> > would be unnecessarily imposed on the developer.
> >
> > Just my two cents,
> >
> >
> > Lutz
> >
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--- original Nachricht Ende
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
I'd really like to suggest an approach similar to the UriTemplate annotation for
T4 pages that's included in tacos...
See
http://fisheye3.atlassian.com/browse/tacos/tacos-4.1/trunk/tacos-annotations/src/java/net/sf/tacos/rest
It even supports aliases, so, no worries if you decide to change names
and still want to old bookmarks - just use:
@UriTemplate(value="index", alias = {"home", "default"})
public class Home { ... }
On 6/25/08, Lutz Hühnken <[EMAIL PROTECTED]> wrote:
> Shouldn't that be up to the developer (or whoever decides on the
> URLs)? If you don't want the page suffix, why not just name the page
> "Blogger" instead of "BloggerPage"? What if I wanted a url that reads
> "mypage"? Would I have to name the page "MyPagePage"? I'm all for
> convention over configuration, but here I feel some arbitrary rule
> would be unnecessarily imposed on the developer.
>
> Just my two cents,
>
>
> Lutz
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
Shouldn't that be up to the developer (or whoever decides on the URLs)? If you don't want the page suffix, why not just name the page "Blogger" instead of "BloggerPage"? What if I wanted a url that reads "mypage"? Would I have to name the page "MyPagePage"? I'm all for convention over configuration, but here I feel some arbitrary rule would be unnecessarily imposed on the developer. Just my two cents, Lutz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
On 25 Jun 2008, at 01:12, Filip S. Adamsen wrote: As long as it's configurable, I'm fine with it. :) Except you lose some of the intrinsic simplicity of convention over configuration when you decide to offer both. Note that, depending on how it's implemented, this change need not break any existing Tapestry 5 applications. If the page class has a -Page suffix, then Tapestry would map to that. (You might have to throw an exception if Foo and FooPage both existed under the pages package hierarchy.) On the naming issue itself, I think it would be a positive development. I think the historical convention of using entity-like names for pages is a regrettable fuzziness. I've shown Tapestry to some undergraduate students and a common beginner's mistake is to put code in a page class that really belongs in an entity class. The naming didn't help there. I'm sure something similar would apply with junior developers in a software house. There's very little point in making the hurdles any higher for people learning their craft. To really set the cat amongst the pigeons (and infuriate the keystroke tax collectors), I think a similar mapping of a -Component suffix would be good for components (again optional). Although it's unfortunately a longer suffix, the conceptual clarity would probably be worth it. (Why refer to something as, say, an "account component" when discussing it but refuse to actually call it that. Because it's too long?) Lastly, I don't think I would go along with Hugo's idea of list of optional suffixes. I can't imagine any sensible suffix for pages and components other than -Page and -Component. (Although that could just be my limited imagination.) :-) Don. This message has been scanned for content and viruses by the DIT Information Services E-Mail Scanning Service, and is believed to be clean. http://www.dit.ie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
I also agree. Maybe this could take the form of a configuration property. You could specify a list of optional suffixes for page/component names. When configured, you could either access the page/component by it's complete name or by it's stripped version. Geoff Callender wrote: Agreed. Don't make it a default. On 25/06/2008, at 12:05 PM, Chris Lewis wrote: I heartily agree with Filip. Even though the page name 'optimization' is documented, I loathe the fact that I can do nothing to stop it. Please, if this is implemented at least allow users the power to say 'yay' or 'nay' in our apps. Filip S. Adamsen wrote: As long as it's configurable, I'm fine with it. :) -Filip On 2008-06-25 01:53, Howard Lewis Ship wrote: I think it's common that you have an entity type, say Blog or Blogger, and a corresponding page for viewing or editting that type. A natural name might be BlogPage or BloggerPage ... but that creates ugly URLs. What if Tapestry stripped off a "Page" suffix from page names? Thus you might have a BloggerPage class and BloggerPage.tml template, but the page name would be "Blogger" and the URL would be "/blogger". Peeking over people's shoulders at Formos, I've been seeing people using the -Page suffix already. I just want to neaten up the URL related to that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://thegodcode.net - 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]
Re: What if "Page" was removed from page names?
Agreed. Don't make it a default. On 25/06/2008, at 12:05 PM, Chris Lewis wrote: I heartily agree with Filip. Even though the page name 'optimization' is documented, I loathe the fact that I can do nothing to stop it. Please, if this is implemented at least allow users the power to say 'yay' or 'nay' in our apps. Filip S. Adamsen wrote: As long as it's configurable, I'm fine with it. :) -Filip On 2008-06-25 01:53, Howard Lewis Ship wrote: I think it's common that you have an entity type, say Blog or Blogger, and a corresponding page for viewing or editting that type. A natural name might be BlogPage or BloggerPage ... but that creates ugly URLs. What if Tapestry stripped off a "Page" suffix from page names? Thus you might have a BloggerPage class and BloggerPage.tml template, but the page name would be "Blogger" and the URL would be "/blogger". Peeking over people's shoulders at Formos, I've been seeing people using the -Page suffix already. I just want to neaten up the URL related to that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://thegodcode.net - 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]
Re: What if "Page" was removed from page names?
I heartily agree with Filip. Even though the page name 'optimization' is documented, I loathe the fact that I can do nothing to stop it. Please, if this is implemented at least allow users the power to say 'yay' or 'nay' in our apps. Filip S. Adamsen wrote: > As long as it's configurable, I'm fine with it. :) > > -Filip > > On 2008-06-25 01:53, Howard Lewis Ship wrote: >> I think it's common that you have an entity type, say Blog or Blogger, >> and a corresponding page for viewing or editting that type. A natural >> name might be BlogPage or BloggerPage ... but that creates ugly URLs. >> >> What if Tapestry stripped off a "Page" suffix from page names? Thus >> you might have a BloggerPage class and BloggerPage.tml template, but >> the page name would be "Blogger" and the URL would be "/blogger". >> >> Peeking over people's shoulders at Formos, I've been seeing people >> using the -Page suffix already. I just want to neaten up the URL >> related to that. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://thegodcode.net - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What if "Page" was removed from page names?
As long as it's configurable, I'm fine with it. :) -Filip On 2008-06-25 01:53, Howard Lewis Ship wrote: I think it's common that you have an entity type, say Blog or Blogger, and a corresponding page for viewing or editting that type. A natural name might be BlogPage or BloggerPage ... but that creates ugly URLs. What if Tapestry stripped off a "Page" suffix from page names? Thus you might have a BloggerPage class and BloggerPage.tml template, but the page name would be "Blogger" and the URL would be "/blogger". Peeking over people's shoulders at Formos, I've been seeing people using the -Page suffix already. I just want to neaten up the URL related to that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What if "Page" was removed from page names?
I think it's common that you have an entity type, say Blog or Blogger, and a corresponding page for viewing or editting that type. A natural name might be BlogPage or BloggerPage ... but that creates ugly URLs. What if Tapestry stripped off a "Page" suffix from page names? Thus you might have a BloggerPage class and BloggerPage.tml template, but the page name would be "Blogger" and the URL would be "/blogger". Peeking over people's shoulders at Formos, I've been seeing people using the -Page suffix already. I just want to neaten up the URL related to that. -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
