There's been some progress with the monobook skin recently, new things are basic rtl support and user styles.
You can tweak styles in the monobook skin by adding a page called 'monobook.css' as a subpage of your user page. My test css is at http://test.wikipedia.org/wiki/User:Gwicke/monobook.css for example.
Similar with js, the it's called monobook.js in that case. Other skins don't have the links in the header currently, but those are easy to add.
The css and js pages are editable only to the user and developers, they appear protected to anybody else.
The wiki src is retrived with a new method to get the raw wiki text: http://test.wikipedia.org/wiki/User:Gwicke/monobook.css?action=raw&ctype...
Allowed ctypes are text/css, text/javascript, text/x-wiki and application/x-zope-edit. Any of these return the plain wiki src, just the content header differs. A charset option is optional, e.g. &charset=utf-8.
Brion and me have added an RTL stylesheet to monobook, it seems to work fine in Opera 7.23, Mozilla/Firefox, IE5.5 and mostly IE6. Screenshots at http://wikidev.net/MonoBook_RTL.
Gabriel-
The css and js pages are editable only to the user and developers, they appear protected to anybody else.
Ah, CSS as user-subpages. Always seemed like the most natural way to customize this stuff.
IMHO normal sysop rights should apply. Sysops are trusted users, so they can be expected not to edit other people's stylesheets willy-nilly. (Mmmh .. forcing users to endure red on black text might be a nice alternative to banning ;-)
These edits currently do show up in RC. I think they should, so other users can get inspirations for their own styles. However, we should probably change the parser so that it doesn't try to render pages with titles of the pattern
User:.*.css User:.*.js
and instead displays them as raw text (maybe simply by encapsulating the loaded content in <nowiki> before entering the render stage of the parser).
Possible future innovations: * "Preview this style" -> When on a user CSS/JS subpage, set this as my style for the current session only. * "Use this style" -> when on a user CSS/JS subpage, make this my own custom style (i.e. copy the page to the top revision of my own user subpage for that skin)
Regards,
Erik
Erik Moeller wrote:
IMHO normal sysop rights should apply. Sysops are trusted users, so they can be expected not to edit other people's stylesheets willy-nilly. (Mmmh .. forcing users to endure red on black text might be a nice alternative to banning ;-)
1. Become sysop. 2. Bot-create user .js subpages to display commercial popups. 3. Profit!
;-)
On Thu, 29 Apr 2004 09:38:32 +0200, Magnus Manske wrote:
Erik Moeller wrote:
IMHO normal sysop rights should apply. Sysops are trusted users, so they can be expected not to edit other people's stylesheets willy-nilly. (Mmmh .. forcing users to endure red on black text might be a nice alternative to banning ;-)
- Become sysop.
- Bot-create user .js subpages to display commercial popups.
- Profit!
;-)
I don't think that user will stay sysop for a long time :)
In the same kind of idea, I thought about allow user to customize its toolbar via a page (we can name it [[toolbar:user_name]] or [[user:user_name/toolbar]]). The user just put there the list of link he want to have in the toolbar and then, the software check the existence of this page and choose to load it or otherwise, use default toolbar. The default toolbar should be in the MediaWiki namespace that each community may able to customize it as they wish.
Here is an example: http://test.wikipedia.org/wiki/Toolbar:Aoineko
Aoineko
----- Original Message ----- From: "Ashar Voultoiz" thoane@altern.org To: wikitech-l@wikipedia.org Sent: Thursday, April 29, 2004 7:45 PM Subject: [Wikitech-l] Re: user styles, rtl, raw text action
On Thu, 29 Apr 2004 09:38:32 +0200, Magnus Manske wrote:
Erik Moeller wrote:
IMHO normal sysop rights should apply. Sysops are trusted users, so they can be expected not to edit other people's stylesheets willy-nilly.
(Mmmh
.. forcing users to endure red on black text might be a nice alternative to banning ;-)
- Become sysop.
- Bot-create user .js subpages to display commercial popups.
- Profit!
;-)
I don't think that user will stay sysop for a long time :)
-- Ashar Voultoiz http://fr.wikipedia.org/Utilisateur:Hashar My french blog: http://twenkill.dyndns.org/plog/
Wikitech-l mailing list Wikitech-l@Wikipedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
On Thu, 2004-04-29 at 22:04 +0900, Guillaume Blanchard wrote:
In the same kind of idea, I thought about allow user to customize its toolbar via a page (we can name it [[toolbar:user_name]] or [[user:user_name/toolbar]]). The user just put there the list of link he want to have in the toolbar and then, the software check the existence of this page and choose to load it or otherwise, use default toolbar. The default toolbar should be in the MediaWiki namespace that each community may able to customize it as they wish.
Just override the toolbar stuff from you user js (/monobook.js). Get the div, replace its content with your own version and you're set. You can also attach to any event handlers from your user js- so you could add shortcurts that work in the textarea and similar.
If one of those new scripts work well across browsers, it will most likely make its way into cvs.
On Thu, 29 Apr 2004 01:55:28 +0200, Gabriel Wicke wrote:
There's been some progress with the monobook skin recently, new things are basic rtl support and user styles.
You can tweak styles in the monobook skin by adding a page called 'monobook.css' as a subpage of your user page. My test css is at http://test.wikipedia.org/wiki/User:Gwicke/monobook.css for example.
Similar with js, the it's called monobook.js in that case. Other skins don't have the links in the header currently, but those are easy to add.
The css and js pages are editable only to the user and developers, they appear protected to anybody else.
The wiki src is retrived with a new method to get the raw wiki text: http://test.wikipedia.org/wiki/User:Gwicke/monobook.css?action=raw&ctype...
Allowed ctypes are text/css, text/javascript, text/x-wiki and application/x-zope-edit. Any of these return the plain wiki src, just the content header differs. A charset option is optional, e.g. &charset=utf-8.
Brion and me have added an RTL stylesheet to monobook, it seems to work fine in Opera 7.23, Mozilla/Firefox, IE5.5 and mostly IE6. Screenshots at http://wikidev.net/MonoBook_RTL.
Thanks for all your hard work Gabriel ! :)
wikitech-l@lists.wikimedia.org