There's no need to add a message for each
property. We have
<extensionname>.css :)
Yes. The reason why I suggested a message page to house all the properties
(not one for each, I think that would be overkill) is that CSS is the output
format in this case.
If you store the data as CSS, then the editor (gui as you suggest - which is
nice, or special page) is responsible for parsing out that CSS in a
meaningful way so as to populate the gui components.
It's the same problem as the wikitext/html dynamic. You store the wikitext
and generate the html.
As to your other ideas, like the JS/gui method of specification: very nice!
-- Jim R. Wilson (jimbojw)
On 6/16/07, Platonides <Platonides(a)gmail.com> wrote:
>
There's no need to add a message for each
property. We have
<extensionname>.css :)
>
> What could be added with an extension is a system to take the CSS
> customizing to the mere mortals:
> -Click on any part of the interface to customize it.
> -Comboboxes and textboxes for choosing different colors, sizes, styles...
> -You have chosen this code <CSS code>
> -Preview it
> -Test with article foo
> -Save to my custom stylesheet
> -Add to my custom stylesheet
>
> Per user stylesheets have a apply-on-preview feature, but even with
> that, CSS editing is hard. Lots of text, properties and values to
> mistype, with a continous need to preview how-it-goes. Overlappings,
> not-on-the-place-i-wanted, z-index it, changing this, reposisitions the
> whole layout...
>
> We should give Wikipedia in a console terminal, not in a web page :D
>
>
> Thomas Dalton wrote:
> > Any way of customising the skin without directly editing the CSS would
> > be extremely limited. If you make a list of things you would like to
> > be easily customisable, it shouldn't be difficult to knock up a
> > special page to do it. However, you would probably have to choose
> > between customising via the special page *or* by the CSS - I can't
> > think of a practical way to merge customisations from both (except for
> > using the special page as a starting point and then editing the CSS,
> > but you would lose any edits to the CSS if you changed anything on the
> > special page later on).
>
> Jim Wilson wrote:
> > It probably goes without saying that this functionality could be
> implemented
> > entirely via an extension.
> >
> > Elements:
> > 1. SpecialPage to show and process the form (locked for use only by
> Sysops)
> > 2. Storage location for values reaped form the from (probably an
> article in
> > the MediaWiki namespace)
> > 3. Hook into 'SkinTemplateSetupPageCss' to add a <style> tag with
values
> > from storage location
> >
> > So in the form you might have a textbox asking for "body color". On
> save
> > this might be stored in the Msg article as "bodycolor=#xxx".
> Finally, the
> > hook reads the Msg and renders out:
> >
> > <style type="text/css">body { color: #xxx } </style>
> >
> > Simple! Then it just becomes a matter of determining which styles
> deserve to
> > be represented in this manner.
> >
> > -- Jim R. Wilson (jimbojw)
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
>
http://lists.wikimedia.org/mailman/listinfo/wikitech-l
>