I know I keep saying this, but FarCry requires the implementing CF programmer to PLAY with the product. Look at the schema, look at the underlying FourQ database kernel, look (primarily) at the code in farcry_core/tags/webskin and farcry_core/tags/navajo.
This probably means that - as the developer - you need to have a fairly good grounding in CFMX (and I mean the MX bit because FarCry uses CFMX features extensively). Not everything is documented (quite a lot is not - and it would be a waste of time to do so because the product evolves too rapidly and documentation maintenance is costly). As members of the list we all end up contributing something. Documentation is something we can all contribute to as well. > I would still like to know how their(FarCry) documents pages were done ! > Can we have a look at the code !!! please :) Do you means pages like the walkthroughs ? Or do you mean the index pages to the walkthroughs/documents ? If you mean the actual pages, they are just input using the HTML editor for page (Daemon have a standard for how they are produced). If you mean how they produce the indexes for all the document pages.... The index page is the main page in a navigation. They would be using a derivative of the multiPageTOC webskin tag that comes with FarCry to produce the index. All the document pages are stored in the same navigation node as the index page and would just be "normal" dmHTML elements edited with the WYSIWYG editor. You can have as many pages as you like under a navigation node. When the node is navigated to the first available page under the node is always displayed. The designer is responsible for providing a mechanism (e.g. the farcry multiPageTOC webskin tag) to navigate to other sibling documents in the same navigation node. So, instead of what you would see in a template like displaypageStandard.cfm which primarily just does a: <cfoutput>#stObj.body#</cfoutput> to display the content of the object. To get a brief index, you would add underneath that: <skin:multiPageTOC objectID="#stObj.objectID#"> multiPageTOC is not a fully fledged indexing tag - it just displays enough. But if you copy that to your own <your app>/tags/webskin directory, add in your own <CFIMPORT> to load the tag and call it, then you can change the code to suit what you want to do. Regards, Gary Menzel --- 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
