[pmwiki-devel] current font sizes

[michael paulukonis]

Look at how Wordpress has vastly improved the look of the default skins it
provides over its lifetime.

However, it also has explicitly changed the name of the skins, and provided
version numbers for them.

Could we give an explicit version number to the default PmWiki skin going
forward, and separate the skin from the wiki itself? They shouldn't be
tightly bound (perhaps they are, but I would hope not).


While we're on the subject of consistency -- how about moving all of the
styles used in a default install into the css files?
There are still wiki-style definitions (eg,
http://www.pmwiki.org/wiki/PmWiki/GroupHeader) that can't be easily
obviously targeted by a skin because they're hidden in header files, etc.

While it is important to show markup examples in action, perhaps they could
be limited to their own pages, so that something like PmWiki/BasicEditing
is not dependent upon them.



-Michael Paulukonis
http://www.xradiograph.com
<http://goog_2112721603>Interference Patterns (a
blog)<http://www.xradiograph.com%5Cinterference>
@XraysMonaLisa <https://twitter.com/XraysMonaLisa>
http://michaelpaulukonis.com
<http://www.BestAndroidResources.com>

Sent from somewhere in the Cloud
(hearthrug, by the fender)


On Mon, Jan 13, 2014 at 10:10 AM, V.Krishn <vkrishn4 at gmail.com> wrote:

> On Monday, January 13, 2014 05:44:25 AM Petko Yotov wrote:
> > Patrick R. Michaud writes:
> > > On Mon, Jan 13, 2014 at 11:38:53AM +1300, Simon wrote:
> > > > I would be reluctant to see this changed back.
> > > > I consider it more problematical having a mixture of fixed and
> variable
> > > > width spacing for "font-size" (the only CSS attribute we are
> discussing
> > > > here).
> > >
> > > IMO, it's definitely more problematical for a PmWiki upgrade to do
> things
> > > that break existing sites.
> >
> > I have reverted the changes in the pmwiki.css file and released 2.2.60.
>
> >
> > > Since there's a way to get to the desired result (improved CSS for new
> > > sites, easy for existing sites to switch to the cleaner design if
> > > desired) by simply including a new skin (or even just an improved CSS
> > > file) in the distribution, we should do that.
> >
> > If we add a new skin or even a new css file, in the same logic we
> shouldn't
> > change it later. For that reason, before adding it to the core, let's
> agree
> > on what it should contain. Besides font-size units, any other changes
> that
> > are required (tableless? RWD?).
> >
>
> If improved CSS, responsive design... etc are being considered,
> can we start with pmwiki-exp skin and add features gradually.
> This could well become pmwiki3 skin.
>
> --
> Regards.
> V.Krishn
>
> _______________________________________________
> pmwiki-devel mailing list
> pmwiki-devel at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pmichaud.com/pipermail/pmwiki-devel/attachments/20140114/c5824ebc/attachment.html>