[wp-hackers] Tag cloud semantics

[Christine Davis]

Had anyone given any thought to how the content of the classes should work?

I ask, because if the intention is for people to add more classes to
style.css in their theme,  they're not going to add an infinite number of
classes <: and at some point, you could end up in a situation where you have
a tag using the class tag-cloud-item-n+1 which wouldn't be styled properly
(and you'd probably have to go back and adjust the other n styles, too.
Sucks.)

Generating the CSS based on the number of times the most popular tag is used
would be a little more practical;  but has trade-offs in that it would be an
additional CSS file that would need to be included (so themes would need
tweaking),  and you also lose a bunch of control over how it looks (unless
you add eleventy billion parameters to control everything).

(In UTW,  I did it with styles against individual items to avoid the "not
enough classes" issue,  while also skipping the linking-to-generated-CSS
issue (The alternative being, I guess, a wodge of CSS in the page;  but then
there's the issue of making sure it shows up just the once.  So many little
ways it could go wrong!).  That said, it was pretty easy to ask UTW to
generate a tag cloud with classes)

*cough*

And isn't this the kind of interface thing that widgets and plugins can deal
with, anyway?  (jus' sayin')

ch.

On 1/23/08, Otto <otto at ottodestruct.com> wrote:
>
> Agreed, we need to use classes and remove the explicit font styles
> entirely.
>
> See these:
> http://trac.wordpress.org/ticket/5171
> http://trac.wordpress.org/ticket/5172
> http://trac.wordpress.org/ticket/5191
>
>