OpenEdit Includes and ComponentsI've been doing some thinking and comparison of other frameworks there and I think there is only one problem that we've got with the include system in the OEF currently - we don't execute path-actions when we include a file. If we did (even if we only went from the depth that we're requesting down the tree) then we wouldn't have to tailor specific pages with page-actions to include the blog on the main page of a site for example. This could lead to all sorts of neat ideas - we could much more easily include one plugin within another for potential mutual benefit. Image the tracker having access to a archive category for storing it's files - a match made in heaven that wouldn't be that hard to implement - just include a specific category based on the job id. It could even auto create it if it doesn't already exist, bringing all of the functionality, thumbnails etc of the archive into the files section of the tracker. If the archive doesn't exist - no big deal. We simply fall back to the system we're using now. Interesting idea.
Another thought - what about conditional fallbacks? Fallback to archive if it exists, else fallback to file management.
|

