Hi - Dont get me wrong, I am not looking for an "out of the box" solution, that is why I have just spent a complete long weekend researching and trying to get my head around the application.

I have looked through the documentation, and the HOWTOs, but I am stumbling on the navigation part.

I am hoping to spend more time on the details of this topic this week.

I am quite familiar, and experirnced with CFMX, having written a few applications that are being used widely in our hospital environment, but I have decided to take this step, as I am interested in a standards based CMS solution.

I hope to get this sorted out and start making use of, and contributing to the farcry application.

Brant

Gary Menzel wrote:


Hi - I am just wondering what the purpose of the second level nav items
are if they dont do anything with farcry being standard. I cant find any
reference to them in the app when it is cleanly installed.


There isn't any reference to them in the sample application.

I think there is a mixup happening here.  FarCry isn't an out-of-the-box solution.  
Think of it more like a framework.  You still
have to put all the cladding on.  And a major part of the cladding is the menus.  
Everything is in there to get at all the levels
of the menus, but you do have to dig around as well as decide what "materials" you are 
going to use for the cladding (let alone
choosing the paints and trimmings).

The installed application is a "sample" only.

I have to ask this..... Have you been through all the documentation on the FarCry site?
http://farcry.daemon.com.au

There is lots of stuff there that will answer some of your questions.  But you will 
still need to look at some of the core code to
feel completely comfortable in changing the stuff in the sample application and, 
ultimately, your own extensions in your own
application.

I have personally found that having a very good understanding of CFMX is essential and 
the ability to read other peoples code a
very important bonus.


Also, in response to Gary's code, I have the demo navigation stuff
working - thank you, but only by putting the <cfcomponent> tag into the
displaypagelanding.cfm not the displaypageStandard.cfm file.


If you have not set any of your pages to use the displaypageStandard.cfm template then 
you would not see anything if you put the
code in there.

Regards,
Gary





--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to