[Seaside] Design question for Seaside applications

[Romain Robbes]

	Hello Damien,

	Is there something preventing you to have the content calling the  
editor?
	It would seem simpler to me, plus it enforces using call/answer.

	Romain

Il giorno Jul 10, 2006, alle ore 11:33 AM, Damien Cassou ha scritto:

> Hi,
>
> I would like to guide to reader of my Seaside Book through the  
> creation of a blog application. I need the clearest design possible  
> and something that is usually found in Seaside applications to make  
> the reader a good Seaside developer.
>
> So, the application has a title bar, a menu and a content. I would  
> like to change the content component depending on what the user is  
> currently doing (editing or viewing a blog). What is the best  
> design for this ?
>
> Currently, I have the root application that renders the title bar,  
> the menu and the content. The menu and the content know about the  
> root application. When a user click on the menu ('Create a new  
> blog' for example), the application change the content component to  
> an editor component. But, this component is just rendered as a sub- 
> component of the application, it is not called. So, to answer the  
> modified blog message, the editor can't use #answer: and directly  
> sends a message to the application : #editingDoneWithMessage:
>
> Is it a good design ? What are you advices ?
>
> Please, this is really important to teach good designed application  
> and I'm waiting for your advice. I'm sure you want this book to be  
> a good entry point to our world.
>
> Thank you
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

--
Romain Robbes
http://romain.robb.es



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20060710/167c5efd/attachment.htm