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

Rick Flower rickf at ca-flower.com
Thu Aug 19 15:36:06 UTC 2010

On Thu, 19 Aug 2010 08:14:50 +0100, TimM <tamackinnon at gmail.com> wrote:
> 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

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

Yes -- you are 100% correct.. I did that on purpose and will probably 
remove the 2nd announcer as it is more or less doing the same sort of
thing.  Thanks for the comments!

More information about the seaside mailing list