Hi, Damn, you really kept busy over the weekend. It's great to see such activity in the project.
I'm not sure if I can add much to the already in-depth discussion... In terms of interface, i think it's really important to keep a non-tech savvy user in mind (the wp free field is starting to push it for some clients). Drag and drop seems like a good solution, quick and intuitive (most people have at some stage dragged files or folders in their finder/explorer/thing-for-files). I'm looking forward to see the taxonomy system in action in 0.7. This discussion is making me feel I really should study the plugin architecture in the mean time :) Cheers, Ben Michael C. Harris wrote: > 2009/5/23 Owen Winkler <[email protected]>: > >> 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. >> > > [snip] > > >> 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. >> > > After having worked on and thought about the taxonomy system and a > subpages plugin for a while now, I agree with Owen. A generic 'Manage > Vocabularies' page wouldn't be useful, because in and of themselves > vocabularies aren't useful, they need something extra. The appropriate > place for that extra is in a plugin, which needs to supply its own UI. > > As things stand, the subpages plugin doesn't use a UI at all, there's > simply a drop-down in a Page's settings tab where you can choose a > parent. I can see that a hierarchical drag and drop would be a useful > addition to it, but I don't think core is the place for it. > > I think with tags reimplemented as a taxonomy, and a subpages and > maybe pagemenu plugins, that would be a good suit of examples. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
