[Seaside] WATask, or almost.

[Sebastian Sastre]

Hi Esteban,

	what about making aFooParameters to be the model of the task? If you
instantiate it outside the task (before it exists) then you can pass it as
model ala seting a model in Dolphin?. No matter how many components are
created to edit that model it is allways the same.

	I do this all the time.

	cheers,

Sebastian Sastre


 

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Esteban A. Maringolo
> Enviado el: Viernes, 08 de Febrero de 2008 16:15
> Para: Seaside - general discussion
> Asunto: [Seaside] WATask, or almost.
> 
> Hello,
> 
> I have doubts about whether to use a task or not.
> 
> The "use case" is the following, the user first selects the 
> "parameters", once the parameters are selected, it goes to 
> the next step, and does whatever, using such parameters.
> 
> That would be simple using a task:
> MyTask>>#go
>   parameters := self call: (FooParametersComponent new). 
> "answer aFooParameters"
>   self call: (FooEditComponent using: parameters)
> 
> But I'm wondering how to handle the situation if the user 
> wants to "go back" to change the parameters and then again, 
> always working over the same FooParameters instance.
> 
> What would be the best way to do it?
> 
> Regards,
> 
> --
> Esteban A. Maringolo
> eMaringolo at gmail.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside