[Seaside] Seaside 2.7

[Sebastian Sastre]

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Lukas Renggli
> Enviado el: Domingo, 25 de Febrero de 2007 12:33
> Para: The Squeak Enterprise Aubergines Server - general discussion.
> Asunto: Re: [Seaside] Seaside 2.7
> 
> > > Even tough its use is very limited, I think it is quite a cool 
> > > concept. What is missing, I think, is to be able to tell 
> it go one 
> > > step forward or backward when developer tells so. I 
> observed myself 
> > > to build quite a lot of wizard like applications, but 
> since WATask 
> > > does not provide a way (except for the back button) to go 
> back I had 
> > > to connect components in different (and ugly) ways. I 
> think it makes 
> > > sense to give a bit more power to WATask, right now it doesn't do 
> > > anything more than what you can already do within a callback.
> >
> > What about making a reusable component wich renders the sub 
> component 
> > you preconfigure on it and let also programatic 
> configuration of the 
> > actions for it's buttons wich can be typically the same as 
> any wizard?
> 
> Yes, this is what I did so far, however it gets incredible 
> ugly (or even stops to work at all) when you want something 
> more sophisticated, such as conditional display/configuration 
> of certain steps and/or multiple display (loops) of the same 
> steps. This is the use-case where you can't beat a task with 
> its natural control flow ;-)

That's right I know what you mean. Now comes to my mind... what about
modeling that conditionals steps in a state-machine and delegating all to
it? Double dispatch could be useful to tell what to render.

Regards,

Sebastian


> 
> Cheers,
> Lukas
> 
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside