On 16-10-2008 at 16:03, Levi Hoogenberg wrote:
>
> I'm having a feature request and before filing an issue, I would like to
> have other users' opinions on its necessity.
>
> Anyway, in clean URLs you can use defaults for parameter values:
>
> @UrlBinding("/members/{page=1}")
[...]
> @UrlBinding("/blog/{year=currentYear()}/{month=currentMonth()}")
>
> The currentYear/currentMonth methods could be action bean methods (which
> would be nice since in that case, the action bean context would be available
> as well). Another option could be to reuse the validation's EL support.
>
> Now my question is: does this make sense? The counterargument is that you
> can have dynamic parameters using the stripes:param tag and that in that
> case, you can supply any value you want. Does the added value compensate for
> the increased complexity? I think it does, but I'm interested in other
> points of view.
Another argument is that null values can be interpreted as "use the default".
I prefer that one actually, as it gives you the opportunity to distinguish
between "I'm using value 'x' because the user wants it" and "I'm using value
'x' because the user didn't specify".
Just my €0,02.
Oscar
--
,-_
/() ) Freedom is a willingness to accept consequences.
(__ (
=/ ()
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
