on 5/9/2000 5:08 AM, Maciek Kaminski [EMAIL PROTECTED] wrote:
right...i think that is taking things to far. i think it makes the code
to
complicated for others to work with. especially newer engineers...
This is a matter of taste. I can't think of any more smiple way to
express this.
I
On Mon, 8 May 2000, jon * wrote:
Personally, I just don't like code like this. I find it pretty hard to read.
People who have some experience in Swing programming find it
easy.
Bingo. I have zero swing experience (nor do i want any). :-)
Swing is worth a look.
take a look at how
For some time I have been experimenting with using component
application model with Turbine. Whole user interaction is handled
via events.
It is more radical than adding ActionEventListener to Action but
you migth find it interesting.
Example:
import org.apache.ecs.ConcreteElement;
import
On Sun, May 07, 2000 at 11:12:28AM -0700, jon * wrote:
MyObj obj = new MyObj();
data.getParameters().setProperties(obj);
if (obj.validate(data))
That is very cool! That is a really good way to separate out the business
logic very easily.
I didn't want to muddy what I was saying, but
On Sat, May 06, 2000 at 07:45:38PM -0500, dave bryson wrote:
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
On Sat, May 06, 2000 at 06:06:06PM -0700, jon * wrote:
BTW, I'm just about in testing phase of this thing ActionEvent thing...it is
like less than 30 lines of code and very easy to follow! I tested it with a
main() and it is working beautifully. Now just have to plug it into the
system and
on 5/7/2000 5:39 AM, Sean Legassick [EMAIL PROTECTED] wrote:
What I'm doing for this is using business objects with a validate method.
I pass in the RunData so it can add error messages, and validate returns
a boolean.
So then the code in my Actions goes something like:
MyObj obj = new
easy access to WebContext
method in your WebMacroSiteAction.
Oh - you _did_ implement this. Cool - although I'm sure I remember getting
a -1 for this :-)
Yea. I did -1 it didn't I? :-(
I'm sorry. I just went back and re-read your post and I think I interpreted
it wrongly the first time.
on 5/6/2000 4:06 PM, Jon Stevens [EMAIL PROTECTED] wrote:
I will do it at some later date cause I think it is a good idea. :-)
Hey all,
Sorry to reply to my email, but I just started doing some tests with
actually implementing it. It looks like it won't be that hard and is really
cool!
This
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
on 5/6/2000 5:45 PM, dave bryson [EMAIL PROTECTED] wrote:
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
On Sat, 06 May 2000, you wrote:
on 5/6/2000 5:45 PM, dave bryson [EMAIL PROTECTED] wrote:
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"
Ok,
I tested it and it now works!
check out org.turbine.modules.ActionEvent and
org.turbine.modules.actions.WebMacroSiteAction.
The javadocs are quite complete for it. Read them for more info.
This also validates the recent build()-doBuild()/doPerform() name changes.
It was SO easy to add
13 matches
Mail list logo
