In current WebWork the main focus is on "actions". I miss the EXPLICIT implementation of the concept "dialog".
In my view a dialog is a finite state machine implementation (FSM), an action causes a state transition in the active state machine(s) (the (s) is because an application will usually contain layered state machines). I think this relates to my previous posting on "reusing actions" as current WebWork registers "actions" with their follow-up in "views.properties", in the FSM model views.properties would register "action bindings", which are unique (state machine plus action). I found an article on this topic "Interactive Web Applications Based on Finite State Machines": http://www.math.luc.edu/~laufer/papers/isas95.pdf If you agree, there will be some FSM implementation in OSWorkflow: could a light version of this serve as a basis? Of course dialogs will be XML-driven, based on "standards" as BPML or XPDL? Regards, Rob. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
