On Tue, May 02, 2000 at 04:28:35PM -0700, [EMAIL PROTECTED] wrote:
> > Anyway I'm going to be using WebMacro, and it struck me that given Dave
> > Bryson's work with WebMacroSitePage etc it would be possible to write
> > even fewer Screens if the Action and WebMacro template shared a
> > WebContext. Then the Action could set up the WebContext and the template
> > display it.
>
> -1. That isn't what the Action modules are for. There is a clear
> description on the site that explains what Actions are for.
Fair enough - I was thinking of actions like 'admin.ChooseOrFindUser'.
The action puts the user list in the temp hash anyway, and if it were in
a shared WebContext instead a screen class wouldn't be necessary to use
a WM template to display the user list.
But I've no problem with being vetoed on this - I'm just lazy and
fancied not having to write as many Screens :)
> > I guess that given the level of integration of WebMacro that Dave has
> > been suggesting on this list it might even make sense to put the context
> > in the RunData object? Either way only the 3 WebMacroSite* classes would
> > need to know where the context comes from.
>
> -1. The RunData object should not be template language specific.
Fair enough - thought you might say that.
Dave's question about making the default install have 'WebMacroSitePage' as
the default page never got resolved... what's happening on that?
> I'm just happy someone is looking at and using the code and thinking about
> cool ways to improve things (even if I just -1'd all your ideas <smile>).
Thanks.
Whilst I'm getting ideas vetoed, here's another: (!)
I've written a utility function for myself that takes a ParameterParser
and a bean and uses introspection to set bean properties from request
parameters automatically (Yes, I really am lazy :). I'd be happy to
knock this into a patch for ParameterParser itself, but perhaps this
kind of laziness is frowned upon? At the moment it only supports the
types I need right now (int, String and Date) but I could add to this
list...
In case its not obvious, I envisage the function being used in an Action
that transfers form parameters into a bean. I got the idea from the JSP
(sorry!) <jsp:setProperty property="*"> tag.
--
Sean Legassick
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
