Chris J. Davis wrote: > While I agree that we need to allow the user to completely replace the > system with a custom one, I don't agree that the only UI should be > from a plugin. This is a core feature of Habari and as such there > should be a well thought out UI for interacting with it. I think that > this should be a simple system, that shows the power of the taxonomy > system. Since subpages are such an oft-used feature, I think it makes > a great deal of sense to have the core UI we build for taxonomy > implement that feature.
As with all of the features in Habari already like this (undelete, core dashboard modules, local media silo, pingback, etc.), this feature should be a plugin that the installer suggests to enable by default. I think it's sad that we've already got "tags" in core (which will use the Taxonomy API) that we can't remove that to a plugin also when Taxonomy is complete. It's a feature I'd love to implement in a different way (like, omitting the tags admin page entirely). Subpages are a mere subset of the functionality of Taxonomy. By their nature, they don't demonstrate the full force of the underlying feature. There will always be something better, or something more custom required, and I can't imagine a default UI (perhaps that's my limitation, but I suspect it's not) we could design to accommodate all of those alterations. Owen --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
