[Seaside] Re: Refactoring menu bar code for Seaside App..

TimM tamackinnon at gmail.com
Thu Aug 19 07:14:50 UTC 2010

Rick Flower wrote:

> to not be viewable.  Each time the user clicks on a link it sends a
> #Announcement_MenuSelect to the UI_Menu class which squirrels away a bunch
> of info -- the code will then turn around and send another announcement
> (#Announcement_SetMenuBody) to the MyApplicationRoot class which will 
> save the
> new object as the "body" to be displayed. 

As an initial fist scan impression - do you need the second 
announcement? Could the UI subscribe, and when receiving it, dispatch 
back to the announcement and ask it (as they are objects) do what UIMenu 

Like you said, there are many ways - but it really sounds like one 
operation going on.


More information about the seaside mailing list