Allen Gilliland wrote: > > > Dave wrote: >> On 10/4/06, Allen Gilliland <[EMAIL PROTECTED]> wrote: >>> I don't understand what you guys mean by this. How are tags and >>> categories going to be "configured"? Shouldn't it just be up to the >>> template author to decide if they display categories, tags, or both? >>> >>> I don't really see how you would plan to disable one or the other on a >>> per weblog basis. Would that mean all of the editing UI would remove >>> any references to them? Would all of the rendering have to be sensitive >>> to the fact that weblog XXX doesn't support categories? That sounds >>> very confusing to me. >> >> >> If categories are disabled then: >> - do not show category combo box on weblog edit page >> - do not show category page in menu >> - do not show categories in RSS and Atom feeds >> - do not show include <categories> element for cats in APP service doc > > but category is not an optional attribute of an entry right now.
good point, but we can have a default root/general category for all posts. > >> >> If tags are disabled then: >> - do not show tags field in weblog editor page >> - do not show tags in RSS and Atom feeds >> - do not show include <categories> element for tags in APP service doc > > I don't understand the need for all of these, I think the last 2 are > implied simply by not entering any tags for an entry right? > >> >> I think that's all we'd need to do and none of those are hard to >> implement. > > Well, I think we should think about this a little bit more before we > dive in. IMO some of these things probably aren't necessary, and some > of them may just cause more confusion. I definitely agree that we need to discuss this a good bit before we do anything to make sure we are going to end up with something way too confusing and complicating the code a great deal. The reason why I'm interested is because our users always used to say: when do I use a category and when do I use a tag, so we removed categories and there was some complain at first, but I haven't heard much after that. I do think that site-level might be less confusing than site level, but it seems a bit too limiting to have to decide one-way or another, worse, can you switch back and forth? My head hurts. -Elias > > -- Allen > >> >> - Dave >
