On Sat, 06 May 2000, you wrote:
> This is mostly to dave, but I'm going to make the WebMacroSiteAction use
> this methodology by default (all it will have to do is extend the
> ActionEvent class instead of the Action class) if that is cool with you. If
> it can't find the "special" methods, then it will roll back to the
> doPerform() method as a default so it should be fairly transparent if you
> don't want to write your code that way.
Cool! Along these same lines, what about a way for template authors to
specify required fields. Maybe some type of object in the context that
could be used.
Like this: <input type="text" name="$required("fname")">
then Turbine could have a standard way of dealing with this.
Sorry to get of track from your suggestion, you just got me thinking.
--
dave
[EMAIL PROTECTED]
----------------------
< your inspirational quote here >
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
