[Seaside] Design question

Sebastian Sastre ssastre at seaswork.com
Thu Jul 10 01:52:49 UTC 2008


Hi Bill,

	I didn't get your example but I don't see why rendering subcomponents
conditioned to model state could be a problem. Do you?

	cheers,	

Sebastian 


 

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Bill Schwab
> Enviado el: Miercoles, 09 de Julio de 2008 18:45
> Para: seaside at lists.squeakfoundation.org
> Asunto: [Seaside] Design question
> 
> Hello all,
> 
> I appear to have file uploads working, and am now trying to make it
> meaningful.  The flow is something like the following:
> 
>  * anchor/button starts upload process
>  * user saves a file locally, then invokes the upload form
>  * user includes text for a BibTeX entry in a separate field
>  * the system proposes an altered entry with additional fields
>     and lets the user preview/edit it.
>  * user finally accepts/saves the result into the server's
>     copy of the data (articles and BibTeX database).
> 
> I have probably used too many components, but my question surrounds
> "the" upload component.  There is a need to loop until things are
> correct, and I am wondering whether I should use one component with
> conditionally-rendered sub-components (e.g., once a file has been
> uploaded, stop asking for it), or if I should use another component
> class(es) for the subsequent steps?
> 
> I hope that's clear to you - I'm not sure I understand it :)
> 
> Bill
> 
> 
> 
> 
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
> 
> Email: bschwab at anest.ufl.edu
> Tel: (352) 846-1285
> FAX: (352) 392-7029
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



More information about the seaside mailing list