On Mar 4, 4:19 pm, AJ Mercer <[email protected]> wrote: > I have found the dmInclude a little backwards in the way it operates. > Most like because of what it was originally designed for, and that being > including external CF applications into a Farcry site.
Just trying to understand the problems you are trying to solve by improving includedObj template option of dmInclude with the wbxProcess plugin. The original dmInclude's purpose in life was to provide a hook for a chunk of arbitrary CF code to be included into the context of the site IA. In 5.1 it has been somewhat revitalised by the addition of hooking type (aka list) webskins into the IA. Generally these days we eschew the use of dmInclude for anything but type webskins, ie. we never use templates in ./includedObj These templates are about for backward compatibility and migration options. Are you familiar with the new type skins features of dmInclude? Perhaps this new feature will solve the problems you are trying to address? Anyhoot, will wait for a bit of background before trying to convince you that "type webskins" are the next best thing. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
