One way could be to use an XML file to declare the entire admin interface tab/subtab/items arrangement. Then check to see if there's a custom XML file in the project's directory and if it exists use that instead.
Another option is to use a cfm file containing the structure declared using nested custom tags. Then check to see if there's a custom cfm file in the project's directory. The custom cfm file can use the core custom tags, their own custom tags or a combination of both.
A few of my own requirements:
(1) To be able to specify URL params (or some type of params) for tab items.
(2) To be able to link to any sub-tab or tab-item directly. When visited it loads the admin page opening the relevant tab and subtabs.
(3) To be able to specific custom CSS for the whole admin section, an admin tab, an admin sub-tab and a tab-item.
I've had to use (1) when needing 3 genericadmin pages which each differed only slighty I just wanted to pass different url params for each tab-item.
I've needed (2) for when I've sent an email to an admin or approver and wanted to include a link that they could click that would go to a specific admin subtab or subtab item (which had been declarded in customadmin.xml). Remember they may first need to be forwarded to the login page.
I've needed (3) when shipping a farcry component and needed to include CSS for my admin pages and tabs.
Maybe this could coincide with the G16N of the admin interface?
-- tim
http://www.toolmantim.com
--- 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
