On Sep 30, 8:20 pm, Colin Jones <[email protected]> wrote: > > On Sep 29, 10:02 pm, Colin Jones <[email protected]> wrote: > > > -> packages -> webskins -> > > > displaySearchForm.cfm - Display the search and call the > > > searchParser.cfc on submit. > > > The view should be placed in ./webskins/searchparser/ > > displaySearchForm.cfm > > OK - I take it this is still "webskins" within the plugin folder > though? Is there a specific reason for using the searchParser > subfolder (or is it just for tidyness and the fact that these are used > with that CFC?)
Views or webskins are always executed in the context of a content type or "form" type. The framework requires that all webskins be placed in a folder that corresponds to the name of the content type (or form type). At application initialisation, each folder is scanned and the views (or webskin templates) are automatically registered for the relevant content type. If you put the view anywhere else the framework will not recognise it. The only quasi exception are webskins associated with an abstract class such as ./webskins/types -- which are effectively views that are attached to all content types exending the ./packages/types/types.cfc ie. all content types. The framework essentially aggregates the views from core, all plugins and your project -- each location has exactly the same directory format ie. ./webskins/*yourcontenttypename* Hopefully that makes sense :) -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
