On 6/21/2011 6:02 PM, Alyaxey Yaskevich wrote:
I'm not sure that this problem is reason to move the plugin from the core. Users should think by themselves, and it's not very comfortable without of the list of existing tags when one creates new post. Also I should mention that first experience of new Habari user is based on core package, and lack of usual tools is undesirable. Maybe maximum of tags should be in the settings of the plugin (to notice user if he picks too many tags), and default number may be set to 3-4.
It wasn't a matter of the number of tags used in the post, it was a matter of the number of tags displayed as available options that made the interface unusable. Many new users were importing old databases with many tags, rendering the software non-functional.
In my opinion, rendering the post editing interface non-functional was a good reason to remove this functionality from core. Combined with the idea of ultimately improving the way tags worked, while offering a way for plugins to provide a competing alternative to this core functionality without having to first remove it seemed like a natural evolution.
It's true that the lack of typical tools is undesirable, but functional tools are required as part of the core package. Even if this functionality was to be included, it would be better included as a core plugin, not native core functionality.
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
