Hi Evgeny,
I agree with most of what you've written.
Especially:
> 3. Implement some kind of Grails-like conventions for displaying views
> from Resolutions. View should be searched in
> /WEB-INF/views/actionBean/resolutionName
> file or similar structure. This can be done for example by creation new
> class DefaultViewResolution. By returning instance of this class from
> action method
> one can indicate that default view should be displayed by forwarding to
> that file.
I'm working on a Stripes plugin that does that. I don't think this
should
be part of the Stripes core, but I do find that this type of convention
is very useful.
Also influenced by Grails/Rails, my plugin does away with a
Default*Resolution
entirely and instead uses the convention automatically if you return
void
from your event handler:
public void view() {
// automatically forwards to "view" template
}
This involves accepting public void methods as event handlers, so Action
Bean methods must be written with more care.
My plugin also adopts a few more conventions, which I won't go into here
because things are still moving around. Once I've settled the code, I'll
write proper documentation and make it available.
> 2. Remove single mandatory configuraion param ActionResolver.Packages. By
> default Stripes can search for action beans in some predefined package.
> for example - stripes.action.
Well, maybe it could be a default, but you still need to be able to
specify
your own packages, in case you have a company-imposed package structure.
> 4. Stripes can impelement some kind of infrastructure scripts/ant
> tasks/etc provided with core distribution. Those tasks are similar to
> grails scripts
> and can be used by developer from command line and by IDE plugin creators
> to generate ActionBean/View/VIew Directory.
That came to mind as well while working on my plugin. Right now it is
not
a priority because I want to finish the core functionalities of the
plugin
itself. Also, there are different modules involved, and each will have a
"quickstart" to set up a project for you with everything properly
configured.
Beyond that, sure it would be nice to e.g. generate a controller, but
since
that's just creating a class and a template, I don't find it worth
putting
in the time to write the command-line tools involved.
I'll post again when the plugin is in decent shape for a test drive.
Let us know on your side what you add to IntelliStripes. And thanks!
Cheers,
Freddy
http://www.stripesbook.com
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
