[pmwiki-users] It's time to change pmwiki default skin!
john.rankin at affinity.co.nz
Thu Sep 22 01:19:14 CDT 2011
> Paul Giacherio wrote:
>>The .vspace function can be eliminated if we include a proper css reset.
>>This includes a simple reset with and no .vspace. It needs fine tuning
>> but it handles most elements pretty well.
What does "proper css reset" mean, please?
I support those who commended this design and agree with the comment that
making something happen when a visitor hovers over a link would be a Good
Thing. border-bottom 1px solid would be sufficient (following Wikipedia's
> see the "vspace revisited" discussion in this list started 2011-07-22.
> Anyway, having more paragraphs _with_ vspace than without is not
> beautiful in my opinion. Wouldn't it be more elegant to use a class
> "lessvspace" for the small number of paragraphs where the vertical
> space is not wanted?
This is a very interesting suggestion and makes good sense to me. It is
almost as easy to implement as moving class='vspace' onto every element
that can be preceded by <div class='vspace></div> in the current
environment. The code would just have to insert class='lessvspace' when
the tag isn't preceded by a vspace.
However, I would really like to understand what is meant by "proper css
reset" and how it would distinguish between:
* a list item with no vspace above
* a following item with no vspace above
* another item with vspace above
Followed by a paragraph with vspace above.
Plus all the other spaced/unspaced combinations an author may use, so
pmwiki continues to honour the author's intentions.
More information about the pmwiki-users