[pmwiki-users] It's time to change pmwiki default skin!
paulgiacherio at gmail.com
Wed Sep 21 09:43:59 CDT 2011
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.
On Wed, Sep 21, 2011 at 6:45 AM, Ville Takanen <ville.takanen at iki.fi> wrote:
> Echo John on the div.vspace. I do like the .vspace, but additional divs
> seem a bit overkill.
> On Wed, Sep 21, 2011 at 11:03 AM, John Rankin <john.rankin at affinity.co.nz>wrote:
>> > On 9/20/11, Petko Yotov <5ko at 5ko.fr> wrote:
>> >> On Wednesday 21 September 2011 00:40:16, Carlos AB wrote :
>> > Good points.
>> Agreed. There appears to be a good convergence of views on the
>> requirements for a new default skin, although there will no doubt be
>> devils in the detail.
>> This is not quite on-topic, but I'd like to re-visit the discussion from
>> July on class='vspace'. Is <div class='vspace'></div> the tidiest way to
>> control vertical space between lines? If not, is lifting the default skin
>> also a good time to tweak the html?
>> There is a markup rule that produces <p class='vspace'> instead of <div
>> class='vspace'></div><p>. Perhaps this could be generalised to produce,
>> for example, </li><li class='vspace'> instead of <div
>> class='vspace'></div></li><li>, and so on. As far as I can see, all
>> occurrences of <div class='vspace'></div> can be replaced by
>> class='vspace' on the following element. Is there a reason *not* to do
>> John Rankin
>> pmwiki-users mailing list
>> pmwiki-users at pmichaud.com
> Ville Takanen
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pmwiki-users