Freddy and Evgeny:
One of the main features in Stripes is that is a pretty neat framework, put more
features that the needed or impose some style will be harmful for the framework
and the community.
So whatever we make to extends the framework, must be do it as extensions, not
in the core.
In my past work, we create a MethodNameResolution that use the "Convention over
Configuration" paradigm, as far as we progress in our app, we need both Forward
and Redirect Resolution types (MethodNameResolution use a ForwardResolution
under the cover) so I drop this approach. In a good designed plugin we need
DefaultViewResolutions of both types. (or a similar mechanism, something like
"new DefaultViewResolution(ResolutionType.REDIRECT)")
In defense of people using s:useActionBean, This approach was considerate a good
practice in early versions of the framework (circa 1.4.2 version) and In some
cases is a good option, for example: a layout in CMS or Shopping cart App that
generate dynamically links from information in the database, So you can put the
logic in a s:useActionBean inside a s:layout-definition and forget about that in
the rest of the application
The idea of Freddy's plugin seems very good, and Evgeny and I are cheerful too
add support (In the past Evgeny add support to Freddy's Stripes-Reload
extension). The idea of Evgeny's navigation are very good too and will provide a
quantum leap in usability.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
Stripes-users mailing list
Stripes-users@...
https://lists.sourceforge.net/lists/listinfo/stripes-users
