Mailing List Archive: Wikipedia: Wikitech

Skins

Index | Next | Previous | View Threaded

sheldon.rampton at verizon

Mar 23, 2003, 12:59 AM

Post #1 of 24 (1297 views)
Permalink

Skins

I'd like to do some tinkering with the Wikipedia skins and maybe come
up with a couple of different layouts, but the HTML seems to be
scattered across several different PHP files. Is there a recommended
easy way to do this (ideally in a WYSIWYG HTML editor like
Dreamweaver)?
--
--------------------------------
| Sheldon Rampton
| Editor, PR Watch (www.prwatch.org)
| Author of books including:
| Friends In Deed: The Story of US-Nicaragua Sister Cities
| Toxic Sludge Is Good For You
| Mad Cow USA
| Trust Us, We're Experts
--------------------------------

lee at piclab

Mar 23, 2003, 11:45 AM

Post #2 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

> (Sheldon Rampton <sheldon.rampton [at] verizon>):
> I'd like to do some tinkering with the Wikipedia skins and maybe come
> up with a couple of different layouts, but the HTML seems to be
> scattered across several different PHP files. Is there a recommended
> easy way to do this (ideally in a WYSIWYG HTML editor like
> Dreamweaver)?

You can certainly design and lay out Wikipedia pages using any tool
you like, and just point the developers to them when you're done
with a suggestion to implement you design. If it aligns with our
goals (that is, it's conformant HTML, works across browsers and OSs,
is not a performance penalty, etc.), then we're like to do it.

--
Lee Daniel Crocker <lee [at] piclab> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

tarquin at planetunreal

Mar 23, 2003, 2:46 PM

Post #3 of 24 (1249 views)
Permalink

Re: Skins [In reply to]

Lee Daniel Crocker wrote:

>>(Sheldon Rampton <sheldon.rampton [at] verizon>):
>>I'd like to do some tinkering with the Wikipedia skins and maybe come
>>up with a couple of different layouts, but the HTML seems to be
>>scattered across several different PHP files. Is there a recommended
>>easy way to do this (ideally in a WYSIWYG HTML editor like
>>Dreamweaver)?
>>
>>
>
>You can certainly design and lay out Wikipedia pages using any tool
>you like, and just point the developers to them when you're done
>with a suggestion to implement you design. If it aligns with our
>goals (that is, it's conformant HTML, works across browsers and OSs,
>is not a performance penalty, etc.), then we're like to do it.
>
>

It would be nice if designers could simply upload an HTML template & a
CSS file.
(or CSS files plural -- I've discovered alternate stylesheets. see
devedge.netscape.com with Mozilla / Opera to see!)

The system that was set up on the test server of having the combined
HTML & CSS in a wiki pages is unfeasible. when designing by hand, one
tends to refresh the browser every minute or so. having to save the wiki
page & wait for a reload would really drag things out; plus combining
CSS & HTML in a single document means I lost 1/2 of the syntax
highlighitng in TextPad :(

brion at pobox

Mar 23, 2003, 3:28 PM

Post #4 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

> >>(Sheldon Rampton <sheldon.rampton [at] verizon>):
> >>I'd like to do some tinkering with the Wikipedia skins and maybe come
> >>up with a couple of different layouts, but the HTML seems to be
> >>scattered across several different PHP files. Is there a recommended
> >>easy way to do this (ideally in a WYSIWYG HTML editor like
> >>Dreamweaver)?

On Sun, 2003-03-23 at 13:46, tarquin wrote:
> It would be nice if designers could simply upload an HTML template & a
> CSS file.

Tarquin, Sheldon: could you create some sample HTML template files & CSS
sheets in the form you'd *like* to be able to work with? Then we can see
about making the code talk to it.

-- brion vibber (brion @ pobox.com)

Attachments:

signature.asc (0.18 KB)

l.tulipan at mpwi

Mar 24, 2003, 5:34 AM

Post #5 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

About Skins and HTML Templates (as that is what you seem to propose)
I had a few of my webpages running using Fast Template
http://www.google.com/search?q=fast+template (a few tutorial +
modifications can be seen on google)
I don't really like it anymore, but it may be worth a look.
The way you handle it is, making an external template file which is
basically html-code with {SPECIAL_TAGS} in curly brackets which you can
replace from your code.
But for REAL php-programmers (and I am not one of them) this might be to
simple/redundant so feel free to ignore this.

Cheers
Leo

magnus.manske at web

Mar 24, 2003, 6:29 AM

Post #6 of 24 (1250 views)
Permalink

Re: Re: Skins [In reply to]

Leonard Tulipan wrote:

>About Skins and HTML Templates (as that is what you seem to propose)
>I had a few of my webpages running using Fast Template
>http://www.google.com/search?q=fast+template (a few tutorial +
>modifications can be seen on google)
>I don't really like it anymore, but it may be worth a look.
>The way you handle it is, making an external template file which is
>basically html-code with {SPECIAL_TAGS} in curly brackets which you can
>replace from your code.
>
I had a very similar thing running on the test site once.

Magnus

tarquin at planetunreal

Mar 25, 2003, 3:07 AM

Post #7 of 24 (1249 views)
Permalink

Re: Skins [In reply to]

Brion Vibber wrote:

>
>Tarquin, Sheldon: could you create some sample HTML template files & CSS
>sheets in the form you'd *like* to be able to work with? Then we can see
>about making the code talk to it.
>
>
>
This is just a very rough mockup.
I've devised some substitution syntax :-) -- see the comments in the html.

couple of neat tricks:
1. the sidebar width scales with browser font size changes (we currently
don't)
2. use of a body class for article / meta namespace means we can do
things like put the header of non-article pages in italics

I'm assuming that substitutions is done in 2 phases: some of the
substitutions can be made when the template is uploaded & then cached by
the server as HTML.
This would be all the things which are language-dependent but the same
throughout a particular language, eg
* the "From Wikipedia, the free encyclopedia." text
* some of the links such as "Recent Changes"
* the GFDL notice

It's a bit messy having "{MainLinks, suffix:"<br>"}", because I can't
see what the list is going to look like in my browser. One option would
be to use the same syntax as Apache's SSI, but the (big!) downside to
that is that I have to load my page through Apache every time I make
changes, which is quite a bit slower than loading from the file direct.
I'll scratch my head & see if I can come up with something slightly
better for lists of links ...

Attachments:

tarquin.css (0.83 KB)

lee at piclab

Mar 25, 2003, 10:11 AM

Post #8 of 24 (1247 views)
Permalink

Re: Skins [In reply to]

> (tarquin <tarquin [at] planetunreal>):
>
> This is just a very rough mockup.
> I've devised some substitution syntax :-) -- see the comments in the html.

I don't see any use for a template system at all. It's just
a performance penalty for no gain in either flexibility or capability.

What I'm interested in seeing is a /complete page/, fully rendered,
with all text, markup, and style elements. We can then implement
that in the structure we already have which is quite powerful.

> couple of neat tricks:
> 1. the sidebar width scales with browser font size changes (we
> currently don't)
> 2. use of a body class for article / meta namespace means we can do
> things like put the header of non-article pages in italics

Those sound useful; if you can integrate that into the existing
stylesheets, so much the better.

--
Lee Daniel Crocker <lee [at] piclab> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

tarquin at planetunreal

Mar 25, 2003, 10:32 AM

Post #9 of 24 (1249 views)
Permalink

Re: Skins [In reply to]

Lee Daniel Crocker wrote:

>>(tarquin <tarquin [at] planetunreal>):
>>
>>This is just a very rough mockup.
>>I've devised some substitution syntax :-) -- see the comments in the html.
>>
>>
>
>I don't see any use for a template system at all. It's just
>a performance penalty for no gain in either flexibility or capability.
>
>
Suppose I'd like to make improvements to the current skins -- how do I
get HTML & CSS that I can work with?
I can find the CSS files for the existing skins in the stuff I got from
CVS, but everything else is in PHP. Where is the actual HTML made and
how can I see it?

> What I'm interested in seeing is a /complete page/, fully rendered,
with all text, markup, and style elements.

You mean a Wikipedia page that's just like one I would save from my web
browser?

>Those sound useful; if you can integrate that into the existing
>stylesheets, so much the better.
>

From what I can tell from Skin.php, the current system shoves a
"bgcolor" => "#FFFFDD" into the HTML's BODY tag
Change that to shove a class= ... as in my notes:
"class" => "article" and "class" => "meta"
presumably

lee at piclab

Mar 25, 2003, 11:22 AM

Post #10 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

> (tarquin <tarquin [at] planetunreal>):
>
> Suppose I'd like to make improvements to the current skins -- how do I
> get HTML & CSS that I can work with?
> I can find the CSS files for the existing skins in the stuff I got from
> CVS, but everything else is in PHP. Where is the actual HTML made and
> how can I see it?

Well, yeah, it's in PHP; what gets rendered within the article
text is handled by the doWikiPass2() function of OutputPage.php,
which makes calls out to the skin to render links and some other
things. The stuff before and after the article text is produced
by the skin directly.

Skin.php is subclassed by the individual skins.

> > What I'm interested in seeing is a /complete page/, fully rendered,
> with all text, markup, and style elements.
>
> You mean a Wikipedia page that's just like one I would save from
> my web browser?

Exactly. If that shows me some tricks that would useful, then I can
code them up.

> >Those sound useful; if you can integrate that into the existing
> >stylesheets, so much the better.
>
> From what I can tell from Skin.php, the current system shoves a
> "bgcolor" => "#FFFFDD" into the HTML's BODY tag
> Change that to shove a class= ... as in my notes:
> "class" => "article" and "class" => "meta"
> presumably

That (or something like it) is probably a good idea. I'm only a
bit concerned that I want to have styles that apply to the body
text of articles regardless of namespace, but I suppose I can
use the DIVs for that.

--
Lee Daniel Crocker <lee [at] piclab> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

magnus.manske at web

Mar 25, 2003, 11:22 AM

Post #11 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

tarquin wrote:
>
> Lee Daniel Crocker wrote:

> > What I'm interested in seeing is a /complete page/, fully rendered,
> with all text, markup, and style elements.

OK, a possible (and working!) *source* (template) is at
http://test.wikipedia.org/wiki/Wikipedia%3AOmniCologneBlue
which renders something very similar to CologneBlue.

To view a *rendered* page, choose the "Omni" skin in your user settings.
To change the rendereing, edit [[Wikipedia:OmniCologneBlue]] accordingly.

Magnus

tarquin at planetunreal

Mar 25, 2003, 12:37 PM

Post #12 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

Lee Daniel Crocker wrote:

>Exactly. If that shows me some tricks that would useful, then I can
>code them up.
>
>
Well if I were to design a skin from scratch, you'd code the entire
thing into PHP from my HTML?
egad!
I figured using templates would shunt part of the work onto the page
designer's lap, that's all.

>
>
>>>Those sound useful; if you can integrate that into the existing
>>>stylesheets, so much the better.
>>>
>>>
>>From what I can tell from Skin.php, the current system shoves a
>>"bgcolor" => "#FFFFDD" into the HTML's BODY tag
>>Change that to shove a class= ... as in my notes:
>>"class" => "article" and "class" => "meta"
>>presumably
>>
>>
>
>That (or something like it) is probably a good idea. I'm only a
>bit concerned that I want to have styles that apply to the body
>text of articles regardless of namespace, but I suppose I can
>use the DIVs for that.
>
??
The css has 3 blocks:
body {
/* these style rules apply to all articles */
}
body.article {
/* just sets the white colour for articles */
}
body.meta {
/* just sets the yellow colour for meta-pages*/
}

This is why it's called *cascading* stylesheets. :-D
I think we have a communication problem! You speak PHP, I don't. I speak
CSS, and I'm not sure you do.

>
>
>

lee at piclab

Mar 25, 2003, 12:46 PM

Post #13 of 24 (1247 views)
Permalink

Re: Skins [In reply to]

> (tarquin <tarquin [at] planetunreal>):
>
> The css has 3 blocks:
> body {
> /* these style rules apply to all articles */
> }
> body.article {
> /* just sets the white colour for articles */
> }
> body.meta {
> /* just sets the yellow colour for meta-pages*/
> }
>
> This is why it's called *cascading* stylesheets. :-D
> I think we have a communication problem! You speak PHP, I don't. I speak
> CSS, and I'm not sure you do.

Yes, I understand CSS just fine, I just hadn't looked specifically
at yours yet to see what you were doing. And it /is/ a nuisance that
you can't have multiple classes on a single element, even though you
can do a lot without them. I never saw a line of PHP before I wrote
the wiki code, so if I can learn it well enough to write the whole
thing, you should be able to learn enough to make modifications
without too much work.

--
Lee Daniel Crocker <lee [at] piclab> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

tarquin at planetunreal

Mar 25, 2003, 12:59 PM

Post #14 of 24 (1249 views)
Permalink

Re: Skins [In reply to]

Lee Daniel Crocker wrote:

>Yes, I understand CSS just fine, I just hadn't looked specifically
>at yours yet to see what you were doing. And it /is/ a nuisance that
>you can't have multiple classes on a single element, even though you
>can do a lot without them. I never saw a line of PHP before I wrote
>the wiki code, so if I can learn it well enough to write the whole
>thing, you should be able to learn enough to make modifications
>without too much work.
>
Sorry if I offended -- I only meant to say we have areas of knowledge

There are quite a few tricks to work around the problem of single classes.
For example, there's no need to give the "From Wikipedia, the free
encyclopedia." paragraph a class. We can access it by either:

h1 + p { /* first P after an h1 but I'm not sure how IE supports this */ }
or
div.masthead p { /* if we made a top div */ }

with E[foo="bar"] you can do matching on arbitrary tags, but again,
support is patchy.

>
>
>

lee at piclab

Mar 25, 2003, 1:21 PM

Post #15 of 24 (1250 views)
Permalink

Re: Skins [In reply to]

> (tarquin <tarquin [at] planetunreal>):
>
> Sorry if I offended -- I only meant to say we have areas of knowledge

No problem--I agree, I'm not a CSS guru by any means.

> There are quite a few tricks to work around the problem of single classes.
> For example, there's no need to give the "From Wikipedia, the free
> encyclopedia." paragraph a class. We can access it by either:
>
> h1 + p { /* first P after an h1 but I'm not sure how IE supports this */ }
> or
> div.masthead p { /* if we made a top div */ }
>
> with E[foo="bar"] you can do matching on arbitrary tags, but again,
> support is patchy.

Yep, that's another problem with CSS--I've tried to make the
stylesheets I created as simple and widely-supported as possible,
and the fallbacks reasonable. That's why I want to see a complete
working page before I think about coding anything--I want to see
exactly what it looks like on a wide set of browsers first, then
make the code produce it.

--
Lee Daniel Crocker <lee [at] piclab> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC

nick at twoevils

Mar 26, 2003, 1:55 PM

Post #16 of 24 (1248 views)
Permalink

Re: Skins [In reply to]

Speaking of skins, I've been hoping for a stylesheet that is more
suitable for the 'advanced' user - something that makes it easy to do
things as quick and efficiently as possible.

I've created a full finished page, and put it out on my webserver. All
of the CSS is in this one file (instead of linking against the standard
CSS file, which I can't edit.)

Here are some notes, but I got tired of writing them down after a while:

1) a.stub has identical elements in both the HTML and the external CSS file. [removed one]
2) #quickbar a.new is broken (CC2200 should be #CC2200) [fixed]
3) JabbaSkript is removed.
4) CSS is in alphabetical order (tons easier to read and much clearer).
5) Removed the pull-down and Go button from topbar.
6) Removed bgcolor from <body>
7) Removed Main Page, Recent changes, Edit this page, and Older versions from the topbar.
8) Removed the <p> under "From Wikipedia, the free encyclopedia."
9) Removed Wikipedia logo.
10) Abolished 'article' CSS section (the article is the content, isn't it?)
11) Moved 'footer' out of 'content' section.
...

Anyways, here is where you can take a look:
Original: http://www.twoevils.org/files/wiki/Rabbit.html
Revamped: http://www.twoevils.org/files/wiki/Rabbit-minimal.html

It uses CSS2 heavily, and so it probably won't render in any
non-compliant browser (which is fine for 'alternative' skins, I hear).

--
Nick Reinking -- eschewing obfuscation since 1981 -- Minneapolis, MN

dramatic at xtra

Mar 26, 2003, 3:43 PM

Post #17 of 24 (1247 views)
Permalink

Re: Skins [In reply to]

On Wed, 26 Mar 2003 14:55:56 -0600, Nick Reinking
<nick [at] twoevils> wrote:

> Speaking of skins, I've been hoping for a stylesheet that is more
> suitable for the 'advanced' user - something that makes it easy to do
> things as quick and efficiently as possible.
>
> I've created a full finished page, and put it out on my webserver. All
> of the CSS is in this one file (instead of linking against the standard
> CSS file, which I can't edit.)
>
> Here are some notes, but I got tired of writing them down after a while:
>
> 1) a.stub has identical elements in both the HTML and the external CSS
> file. [removed one]
> 2) #quickbar a.new is broken (CC2200 should be #CC2200) [fixed]
> 3) JabbaSkript is removed.
> 4) CSS is in alphabetical order (tons easier to read and much clearer).
> 5) Removed the pull-down and Go button from topbar.
> 6) Removed bgcolor from <body>
> 7) Removed Main Page, Recent changes, Edit this page, and Older versions
> from the topbar.
> 8) Removed the <p> under "From Wikipedia, the free encyclopedia."
> 9) Removed Wikipedia logo.
> 10) Abolished 'article' CSS section (the article is the content, isn't
> it?)
> 11) Moved 'footer' out of 'content' section.
> ...
>
> Anyways, here is where you can take a look:
> Original: http://www.twoevils.org/files/wiki/Rabbit.html
> Revamped: http://www.twoevils.org/files/wiki/Rabbit-minimal.html
>
> It uses CSS2 heavily, and so it probably won't render in any
> non-compliant browser (which is fine for 'alternative' skins, I hear).
>
Nice, but your fixed div at the top is too short for my default font size,
so the text is truncated. You probably need to set the div height in ems.
And I prefer lower contrast than black on white.

--
Richard Grevers

tarquin at planetunreal

Mar 26, 2003, 4:14 PM

Post #18 of 24 (1249 views)
Permalink

Re: Re: Skins [In reply to]

Richard Grevers wrote:

> On Wed, 26 Mar 2003 14:55:56 -0600, Nick Reinking <nick [at] twoevils>
> wrote:
>
>>
>> Anyways, here is where you can take a look:
>> Original: http://www.twoevils.org/files/wiki/Rabbit.html
>> Revamped: http://www.twoevils.org/files/wiki/Rabbit-minimal.html
>>
>> It uses CSS2 heavily, and so it probably won't render in any
>> non-compliant browser (which is fine for 'alternative' skins, I hear).
>>
> Nice, but your fixed div at the top is too short for my default font
> size, so the text is truncated. You probably need to set the div
> height in ems.

Yup.
And have you applied styling to the form buttons? I think it's best to
let the browser supply the user's OS default widgets, so they *look*
like things that perform actions.
I miss the wikipedia logo too :(

>
>
>

nick at twoevils

Mar 27, 2003, 8:28 AM

Post #19 of 24 (1248 views)
Permalink

Re: Re: Skins [In reply to]

On Thu, Mar 27, 2003 at 10:43:14AM +1200, Richard Grevers wrote:
> On Wed, 26 Mar 2003 14:55:56 -0600, Nick Reinking
> <nick [at] twoevils> wrote:
>
> >Speaking of skins, I've been hoping for a stylesheet that is more
> >suitable for the 'advanced' user - something that makes it easy to do
> >things as quick and efficiently as possible.
> >
> >I've created a full finished page, and put it out on my webserver. All
> >of the CSS is in this one file (instead of linking against the standard
> >CSS file, which I can't edit.)
> >
> >Here are some notes, but I got tired of writing them down after a while:
> >
> >1) a.stub has identical elements in both the HTML and the external CSS
> >file. [removed one]
> >2) #quickbar a.new is broken (CC2200 should be #CC2200) [fixed]
> >3) JabbaSkript is removed.
> >4) CSS is in alphabetical order (tons easier to read and much clearer).
> >5) Removed the pull-down and Go button from topbar.
> >6) Removed bgcolor from <body>
> >7) Removed Main Page, Recent changes, Edit this page, and Older versions
> >from the topbar.
> >8) Removed the <p> under "From Wikipedia, the free encyclopedia."
> >9) Removed Wikipedia logo.
> >10) Abolished 'article' CSS section (the article is the content, isn't
> >it?)
> >11) Moved 'footer' out of 'content' section.
> >...
> >
> >Anyways, here is where you can take a look:
> >Original: http://www.twoevils.org/files/wiki/Rabbit.html
> >Revamped: http://www.twoevils.org/files/wiki/Rabbit-minimal.html
> >
> >It uses CSS2 heavily, and so it probably won't render in any
> >non-compliant browser (which is fine for 'alternative' skins, I hear).
> >
> Nice, but your fixed div at the top is too short for my default font size,
> so the text is truncated. You probably need to set the div height in ems.
> And I prefer lower contrast than black on white.

I could never figure out how to set high in ems, when you were going to
have inline buttons. I would do that if I could. Maybe just set it to
like 2 or 3ems, and deal with it.

As for contrast, I will probably change that. It was just a quick
mockup. :) You can have hot pink text on a yellow background. :P
(j/k)

--
Nick Reinking -- eschewing obfuscation since 1981 -- Minneapolis, MN

nick at twoevils

Mar 27, 2003, 8:30 AM

Post #20 of 24 (1250 views)
Permalink

Re: Re: Skins [In reply to]

On Wed, Mar 26, 2003 at 11:14:23PM +0000, tarquin wrote:
>
>
> Richard Grevers wrote:
>
> >On Wed, 26 Mar 2003 14:55:56 -0600, Nick Reinking <nick [at] twoevils>
> >wrote:
> >
> >>
> >>Anyways, here is where you can take a look:
> >>Original: http://www.twoevils.org/files/wiki/Rabbit.html
> >>Revamped: http://www.twoevils.org/files/wiki/Rabbit-minimal.html
> >>
> >>It uses CSS2 heavily, and so it probably won't render in any
> >>non-compliant browser (which is fine for 'alternative' skins, I hear).
> >>
> >Nice, but your fixed div at the top is too short for my default font
> >size, so the text is truncated. You probably need to set the div
> >height in ems.
>
> Yup.
> And have you applied styling to the form buttons? I think it's best to
> let the browser supply the user's OS default widgets, so they *look*
> like things that perform actions.
> I miss the wikipedia logo too :(

Alright, I will remove styling from the buttons. I couldn't get them to
look right, anyways. As for the logo, I can put that back in, I was
just trying for a page that loads as quickly as possible. Every page
loaded without the image is one less 304 generated on the server. :)

Now, if we had a Wikipede... ;)

--
Nick Reinking -- eschewing obfuscation since 1981 -- Minneapolis, MN

qli at ica

Nov 23, 2009, 3:48 AM

Post #21 of 24 (1248 views)
Permalink

Re: skins [In reply to]

I followed the guidelines and made a special page.But I can't see it
anywhere.

Where can I see it?

Or maybe I didn't add the special page to special list? :)

vanessa lee

-----Original Message-----
From: Roan Kattouw <roan.kattouw [at] gmail>
To: Wikimedia developers <wikitech-l [at] lists>
Date: Mon, 23 Nov 2009 08:51:58 +0100
Subject: Re: [Wikitech-l] skins

2009/11/23 李琴 <qli [at] ica>:
>
> Hi
>
> I add a page to the wiki which I write by myself . And I want to use the
> wiki's skins .What can I do to resolve this problm.
>
> Use getSkin() ? Or something others?
>
You don't need to do anything special if you follow the guidelines at
http://www.mediawiki.org/wiki/Manual:Special_pages (provided making a
special page is what you want).

Roan Kattouw (Catrope)

_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

roan.kattouw at gmail

Nov 23, 2009, 3:54 AM

Post #22 of 24 (1253 views)
Permalink

Re: skins [In reply to]

2009/11/23 李琴 <qli [at] ica>:
> I followed the guidelines and made a special page.But I can't see it
> anywhere.
>
> Where can I see it?
>
> Or maybe I didn't add the special page to special list? :)
>
If you followed the instructions in
http://www.mediawiki.org/wiki/Manual:Special_pages#The_Setup_File and
put require_once("$IP/extensions/MyExtension/MyExtension.php"); in
your LocalSettings.php , your special page should show up in
Special:Specialpages.

Roan Kattouw (Catrope)

_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

qli at ica

Nov 23, 2009, 4:23 AM

Post #23 of 24 (1247 views)
Permalink

Re: skins [In reply to]

yeah,I know that ,but I didn't see it.Even I tried it again.

You know special pages has a number of categories ,such as "Maintenance
reports,Users and rights,Login / sign up" and so on .

Maybe we didn't add the special page to special list.That's why I can't see
it.

Maybe there are other problems?

Thanks

vanessa lee

-----Original Message-----
From: Roan Kattouw <roan.kattouw [at] gmail>
To: Wikimedia developers <wikitech-l [at] lists>
Date: Mon, 23 Nov 2009 12:54:48 +0100
Subject: Re: [Wikitech-l] skins

2009/11/23 李琴 <qli [at] ica>:
> I followed the guidelines and made a special page.But I can't see it
> anywhere.
>
> Where can I see it?
>
> Or maybe I didn't add the special page to special list? :)
>
If you followed the instructions in
http://www.mediawiki.org/wiki/Manual:Special_pages#The_Setup_File and
put require_once("$IP/extensions/MyExtension/MyExtension.php"); in
your LocalSettings.php , your special page should show up in
Special:Specialpages.

Roan Kattouw (Catrope)

_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

qli at ica

Nov 23, 2009, 4:26 AM

Post #24 of 24 (1246 views)
Permalink

Re: skins [In reply to]

OK, I see it Thanks

vanessa lee

-----Original Message-----
From: Roan Kattouw <roan.kattouw [at] gmail>
To: Wikimedia developers <wikitech-l [at] lists>
Date: Mon, 23 Nov 2009 12:54:48 +0100
Subject: Re: [Wikitech-l] skins

2009/11/23 李琴 <qli [at] ica>:
> I followed the guidelines and made a special page.But I can't see it
> anywhere.
>
> Where can I see it?
>
> Or maybe I didn't add the special page to special list? :)
>
If you followed the instructions in
http://www.mediawiki.org/wiki/Manual:Special_pages#The_Setup_File and
put require_once("$IP/extensions/MyExtension/MyExtension.php"); in
your LocalSettings.php , your special page should show up in
Special:Specialpages.

Roan Kattouw (Catrope)

_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l [at] lists
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads