On 7/12/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> We have plans to replace the current dot ('.') seperator in component
> paths by another character. The main reason for wanting this, is to
> avoid conflicts with Ognl, and be able to use nested properties more
> easily. E.g., when that fix is done you could do:
>
> add (new RequiredTextField("company.name"));
>
> The first question is: does anyone object, and if so, why?
>
> Next question is what should our seperator be? It should be a seperator
> that can not be used as Java variable names. Here's some examples:
>
> Page.SomePanel.SomeComponent
> Page-SomePanel-Somecomponent
> Page:SomePanel:SomeComponent
> Page#SomePanel#SomeComponent
> Page$SomePanel$SomeComponent
If possible, I would prefer slash '/'. Why? Because the only reason
(from a browser's point of view) I see in having component in the
address, is to bookmark certain page layout (I do not use word
"state"). I mean, if I have /magazine and I have sports, news, cars,
ads, whatever sections. Then in cars I have recenttest, editorscolumn,
letters etc. So I would have address like /magazine/cars/recenttest.
Application first will try to get "magazine" part right. If it got it,
it tries to get "cars". If it is not there for some reason, it shows
default page for magazine. If it is there, it loads "recenttest",
again if it is not there, it loads default subcomponent for "cars".
Can this be done?
Michael.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
