hm.. that's what I had in mind when I read Reinhard's proposal
I see a difference between a widget repository and a datatype repository. When presenting Woody in our company I was asked for a widget repository too. But more important is the datatype repository, the widget repository does not avoid so much typing.
+1
What I mentioned was the need for a generic flowscript wizard library,
that could allow to define "backtrack points" in the list of ancestors of the current continuation.
hm... why is backtracking needed? or what do you mean by it?
Well, "backtracking" means "go back to a previous state and restart from there". And this is what continuations allow easily.
But when I use "go back" in a wizard I don't want to loose the entries already done in the second page. So simply calling the other continuation is not good in my opinion.
That's exactly my point :) ..we would need to popluate into the data of the continuation we are coming from when going back to the one that got us there. (Hope noone got too crosseyed at that sentence ;) -- Torsten
