[CompStrm Wiki] forms

[Bill la F. <laf...@ya...>]

OK, so application API is implemented in a rolon class
(a data proxy). And simple operations are implemented
in a command class. What about interaction?

Interaction is handled by forms, which must implement
the abstract class, org.agilewiki.framework.Form.

Forms are invoked by a command, so there is no special
mechanism required for extensibility.

Some important methods on a form are:

1. initForm --called when a user first starts
interacting with a form.

2. displayForm --called to generate an event tree for
the first and successive responses to the user.

3. evaluateForm --called when the user responds with
form input.

Forms are normal objects--they hold data! An active
form is part of the user's session. They are NOT
thread safe.

Forms are treated like commands, they either database
updaters or not. Updaters are invoked within a
transactional context. Multiple non-updaters can
execute at the same time on different threads.

And right now, for an application, that's pretty much
it. Yes, we can--as needed--define new kinds of
application logic. I'd like to do wizards at some
point when the complexity merits it.

But for now, all the business logic is either in a
rolon class, a command class or a form class.

Bill


		
__________________________________________________________ 
Yahoo! India Answers: Share what you know. Learn something new. 
http://in.answers.yahoo.com