We have gotten into the practice for many clients of just copying all the core components over and then extending them. Under this scenario the options to customize FC are limitless. In dmNav we have done everything from adding color pickers to associating nav nodes with emails addresses for routing forms.

So I would ask that the core is left generic enough to still allow developers to do what they need by extending the core.

Just my 2 cents.



Michael



Geoff Bowers wrote:

Folks,

I'm not sure what generic purpose a hidden attribute would be used for. Can someone outline a couple of case studies for such an attribute and why it would be useful?

-- geoff
http://www.daemon.com.au/


Beth Bowden wrote:

We're looking at implementing a "hidden" option also on dmNavigation.
Any possibility that this feature could be added to core?


On Tue, 22 Feb 2005 16:10:41 +0800, Chris Bauer <[EMAIL PROTECTED]> wrote:

It sounds like extension of the core component - eg, I've got a "hidden"
flag in my navs' Advanced Options section that prevents _primaryNav from
placing the nav node in a generated menu. Is this the kind of thing you
mean?

Brendan did a walkthrough on extending core components:
Page: http://farcry.daemon.com.au/go/documentation/developers/how-to
Document:
http://farcry.daemon.com.au/go/objectid/2B8CC3BC-D0B7-4CD6-F9525292C5BC6A4E



It only touches on what can be achieved, but I think it's a good primer to
get you thinking about it. I'll post my rather simple extension if that's
any use.


Chris




--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to