These are kinda needed for enhanced recentchanges to make sense:
-rwxr-xr-x 1 apache wikidev 289 Jan 6 2003 Arr_d.png
-rwxr-xr-x 1 apache wikidev 918 Jan 7 2003 Arr_.png
-rwxr-xr-x 1 apache wikidev 282 Jan 6 2003 Arr_r.png
a) Who made them?
b) Are they GPL-compatible?
c) If a) and b) are satisfactory, any objection to adding them to CVS?
(They have to be marked as binary files in some way if so. I don't know
the option offhand.)
-- brion vibber (brion @ pobox.com)
OK. My Wikiholism is advancing to the next level and
to feed that I would like to consolidate MediaWiki's
documentation on meta. The reasons are two-fold; 1)
there are already forks in documentation development
between meta, SourceForge, Lee's webpages, and various
Wikipedia namespace pages (not to mention other
duplication; such as in other Wikimedia projects) 2) I
would like to understand the beast known as MediaWiki
so that after I learn PHP I can advance to
uber-Wikiholic and port over the WikiBook
functionality from PyWiki and tweak it for use in
Wikibooks.
I don't want to step on anybody's toes, so I would
like to know who is currently involved with creating
documentation? Is there anybody working on
coordinating documentation efforts? If so, then I
could work with that person instead of leading this
effort on my own. It would also be helpful to know
where current documentation resides.
Currently on meta:
MediaWiki
How to become a MediaWiki hacker
Running MediaWiki on Windows
Database queries on MediaWiki
Text in MediaWiki
MediaWiki math markup
RDF spool
Wiki markup tables -- proposals
Wiki markup syntax - see Wikipedia DTD
meta.wikipedia.org technical issues
Sites using MediaWiki
Wikitax
On en.wikipedia:
Wikipedia:MediaWiki
Wikipedia:Software Phase III
Wikipedia:TeX markup
Wikipedia:Software Phase IV
Wikipedia:TeX markup
Wikipedia:GNU LilyPond support
Wikipedia:Edit summary
Whole bunch of how to use Wikipedia's software pages
(this will take some time since many of them have
Wikipedia-specific references).
I'm thinking about organizing all this between actual
documentation vs ideas about how MediaWiki should
work. Documentation can be further subdivided between
stuff for developers vs stuff for users. When we do
finally have the WikiBook functionality, then an
actual users guide and developer documentation guides
can be organized on meta (complete with a "print this
book" feature).
This is a long term undertaking but I think it is
worth the effort.
-- Daniel Mayer (aka mav)
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
The Cunctator wrote:
>>From: Erik Moeller
>>I do not see the information
>>that deleted revisions exist as so useful as to have it on all pages,
>>primarily because there's simply a fairly large number of pages which
>>have been experimentally created at one point, deleted, and recreated.
>>How about displaying it in the top bar only for non-existing pages, and
>>otherwise displaying it only on "Page history"? This should also reduce
>>the number of checks in the ARCHIVE table needed.
>
>
> That's a good idea.
Done, checked in, and installed.
Well, that was fun! We get a lot more feedback when we just install
stuff on the live server like this. ;)
(Disclaimer: not recommended except for bug fixes and 'emergency
features' that everyone's bitching about the lack of and require only
very small code changes.)
-- brion vibber (brion @ pobox.com)
Tim Starling wrote:
> I agree with Erik that it looks too much like the "you have new message"
> notification. But it's certainly a useful feature and I think it would
> be a pity to force people disable it for aesthetic reasons. I think if
> it was not bold, it would blend in to the other top links and you'd
> barely notice it unless you were looking for it. Plus it would look like
> "delete this page" and "protect this page", so it would be reasonably
> consistent also.
Fair enough. For the moment I've dropped the <strong> but left it
otherwise intact.
(I also fixed it so it produced a correct link on pages in namespaces.
Oops!)
-- brion vibber (brion @ pobox.com)