Thanks Reuben.
Yes, I think I'll do what you suggest: just parameterize a full-dress
Navigation with a custom object, then have the controller retrieve
it. It will be make it the Navigation difficult to extend and write,
but I see no alternative for now...except maybe using a dynamic
class, and building up an object with snapped-on methods?
As for patterns--in this case, I'm definitely grasping for a
solution. But in my short experience, patterns have been hugely
useful, as well as just neat. I think I would eventually have
approximated some patterns (state, observer)..but composite,
decorator, factory? Never. I'm still excited.
>>
Why not use a initialization NavigationSettings class for your
Navigation that has its own methods that can be interrogated by your
controller? ie - new Navigation(new NavigationSettings(params));
The "controller bar" could access the NavigationSettings instance to
find out its necessary settings.
IMHO, patterns are only useful where they actually solve problems,
not create additional ones. "Pattern Fever" does no good for
anyone.If you can't find a pattern that fits your requirements, maybe
patterns are the wrong way to go about it. You shouldn't need to
twist your requirements to try and fit into a particular pattern.
Hope this helps.
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
