Dave wrote: > On 10/4/06, Allen Gilliland <[EMAIL PROTECTED]> wrote: >> The #showTagCloud() macro is slightly leaning toward the path of being >> too complex in my mind, and things that are not going work is including >> those "center" tags and hardcoding the min & max values. I also think >> that a tag cloud is not necessarily the kind of thing that we expect to >> go on every weblog, so I don't think it would be bad if we expect users >> to do this work in their templates if they really want it. > > +1 for including a Tag Cloud macro. Folks are definitely going to want > it, so we should figure out how to do it as generically as possible -- > i.e. figure out the right parameters and the right combination of HTML > and CSS classes. >
I agree with Allen's comments that <center> is just not right and I need to fix it. The mix & max values could easily be parameterized as well. I'm not sure whether the tag clould will go on every weblog but I do know that unlike categories, it's lame to display tags in a bulleted list. The macro can be re-used for mini-tag clouds in the weblog sidebar to nagivate people's entries. I'd suggest we keep it. > >> The #showEntryTags() macro is fairly reasonable, but in my opinion is >> probably so simple that we may be better off forcing users to do that >> one as well. The one thing you can't do is put the "Tags: " line >> in there, because that's not i18ned and we would much rather just not >> put any text in the macros moving forward. In any case, I don't think >> it's a big deal to ask users to do as simple for loop in their templates >> and that way they can create their own <a> html rather than relying on >> ours which would have its own styling conventions. I definitely understand that having un-i18ned text is just bad and that the for-loop is simple. We can definitely remove it. > > +0 to the showEntryTags() macro. > > We should think about what to do in the core themes. Should the _day > templates include category information, tag information, both or > should it be determined by configuration? I think it should be defined > by configuration. > > And how should tags be configured? Weblog level, site-wide level or > both? I'd like tags and categories to be enabled/disabled at the > weblog level. On my blog, I plan on using both -- but some bloggers > might want to turn either tags or cats off. Either way, ConfigModel > should include tagsEnabled and categoriesEnabled flags for use in > templates. > > - Dave > We would definitely support this work (hopefully in 3.1) because our site only uses tags and bringing categories again would be too chaotic. -Elias
