David M Johnson wrote:
On May 9, 2006, at 1:25 AM, Brian Blakeley wrote:
Ok, then I am glad that I was not barking up the wrong tree on this
matter.
So, what makes sense to me is that a set of macros needs to be developed
that either produces no html or that produces an xhtml framework that
the theme's CSS can style in a Zen Garden sort of way.
I think I like the second approach, but Allen's insights about MT are
probably more helpful than my thinking.
What I would like to see is that #showBlogroll producing a basic xhtml
structure such as:
<ul class="level1">
<li>Blogroll</li>
<ul class="level2">
<li><a href="">Dave Johnson</a></li>
<li><a href="">Matt Raible</a></li>
...
</ul>
<li>News</li>
<ul class ="level2">
<li><a href="">Che Nuke</a></li>
<li><a href="">LabourStart</a></li>
...
</ul>
...
</ul>
The user could then wrap this xhtml in a nice <div></div> of there
design and be on their way.
Yes. That would be *much* better.
I agree, that looks like a good way to do it. My one change would be to
use class names that a bit more relevant. "level1" and "level2" just
have no meaning.
Another thing to check on is microformats. I'm not sure if there is
anything for blogrolls, but it's worth a look.
Although, this would lead into a discussion of class attributes, etc, so
I can see the value in Allen's suggestion that no html be produced from
the macro starting to make some solid sense.
My position is that macros are needed for code re-use, which is most
definitely a good thing. However, I do agree that we went too far in
creating macros for each and every little thing.
This is also my stance. I am not against *all* use of macros, I just
think that we need to be very careful about what new macros we add
moving forward. I believe we have already got ourselves into a position
where there are too many bad macros and now we have to continue
supporting them indefinitely.
-- Allen
- Dave
