Wow! PreViewConfigNavigateEvent looks amazing. Thanks for your pointers, with that I am sure I can create a strong implementation.
On 13 April 2014 16:19, Gerhard Petracek <[email protected]> wrote: > hi karl, > > #1 i guess you don't mean the back-button in the browser > #2 for some projects we created a wizard-controller based on view-configs. > page-beans just called #next (or #back) on it. > (you just need a simple window-scoped controller which knows all steps and > the current position. the rest is in place already.) > #3 tracing can be done with an observer for PreViewConfigNavigateEvent > > regards, > gerhard > > > > 2014-04-13 13:46 GMT+02:00 Karl Kildén <[email protected]>: > > > well I am kind of brainstorming :-) > > > > History is the thing. Would be useful with a Stack of visited views. Both > > for the users flow control (go back to page x) and for the logical flows > so > > it can keep track of ie. resumable flows. > > > > Flows can take a long time to finish for a user and they might pause and > do > > something else because they need to search for information etc. > > > > Another thing are small subflows that are like detours in your normal > flow. > > This system fetches a lot of data automatically but for various reasons > it > > sometimes only finds say 70% of the data and a subflow is required to > fill > > in the gaps. These subflows are reused and the exit point should be the > > next page in the *previous *flow. > > > > *Flow1:Page A -> Flow1:Page B -> Incomplete data detected -> switch flow > to > > fix -> Flow2:Page A -> Finished, resume previous flow -> Flow1:Page C -> > > Finished.* > > > > I guess you could say that wee need to keep tabs on our users so we can > > help them pause and resume flows. Some of these pauses are persisted but > > not all. Some flows are only resumeable if you came "far enough" > > > > Tracing is another smaller issue that would be prettier if you had the > > visited pages as the class objects. > > > > Something like below for end usage: > > > > public interface FlowResolver { > > > > public Deque<Class<? extends ViewConfig>> getPausedFlows(); > > > > public Deque<Class<? extends ViewConfig>> getFlowHistory(); > > > > public Class<? extends ViewConfig> getPrevious(); > > > > public Deque<Class<? extends ViewConfig>> getFailedFlows(); > > > > public Deque<Class<? extends ViewConfig>> getFlowsByPriority(); > > > > } > > > > > > > > > > > > On 13 April 2014 09:53, Gerhard Petracek <[email protected]> > > wrote: > > > > > hi karl, > > > > > > please provide details about the use-case you have in mind. > > > > > > regards, > > > gerhard > > > > > > > > > > > > 2014-04-13 3:50 GMT+02:00 Karl Kildén <[email protected]>: > > > > > > > Hi, > > > > > > > > I would like to decide what to return in the navigation case with the > > > help > > > > of InvocationContext. I am interested in getting the method for > > > example... > > > > > > > > Any way to always get a callback kind of like how @Secured works? > > > > > > > > > >
