From beesley at gmail.com Wed Aug 1 00:33:00 2007 From: beesley at gmail.com (Angela) Date: Wed, 1 Aug 2007 02:33:00 +0200 Subject: [Wikia-l] Requesting password to aselia-l mailing list In-Reply-To: <46AFC70B.5050003@gmail.com> References: <46AFC70B.5050003@gmail.com> Message-ID: <8b722b800707311733x3cf8590dk932b4d4663f60ce4@mail.gmail.com> On 8/1/07, Dorian Patterson wrote: > As the current founder of Aselia, I'd like to manage the mailing list > (which I just found out recently existed), but I wasn't given the password. I'll send you this offlist. Angela -- Angela Beesley Wikia.com From duncan at wikia.com Wed Aug 1 00:49:19 2007 From: duncan at wikia.com (Matthew Silvey) Date: Tue, 31 Jul 2007 17:49:19 -0700 Subject: [Wikia-l] Requesting password to aselia-l mailing list In-Reply-To: <46AFC70B.5050003@gmail.com> References: <46AFC70B.5050003@gmail.com> Message-ID: <956E8D6D-021A-42C4-AF4C-94CF69916E8D@wikia.com> I've made you the new list owner and generated a new password. Let me know if you don't receive it. Matthew On Jul 31, 2007, at 4:34 PM, Dorian Patterson wrote: > As the current founder of Aselia, I'd like to manage the mailing list > (which I just found out recently existed), but I wasn't given the > password. > _______________________________________________ > Wikia-l mailing list > Wikia-l at wikia.com > http://lists.wikia.com/mailman/listinfo/wikia-l > From johnq at wikia.com Wed Aug 1 02:17:43 2007 From: johnq at wikia.com (John Q) Date: Wed, 01 Aug 2007 10:17:43 +0800 Subject: [Wikia-l] YUI && WYSIWYG && Wikia Extensions In-Reply-To: <46AFC22A.4080103@telus.net> References: <46AFC22A.4080103@telus.net> Message-ID: <46AFED47.4070806@wikia.com> Hi DanTMan, We made a strategic decision to use YUI a while back. It's been released openly, it's supported by Yahoo, it has incredible documentation and example code, and it's tested on the core set of browsers very thoroughly. So, yes, you can count on being able to use YUI. Our servers currently compress the js files being downloaded and shortly we'll be consolidating files for less back-and-forth. For FSKEditor and MediaWiki, we took a look at that before venturing down the path of making our own. Here are some of the things I saw on the FSKEditor extension page that led us to our decision: * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an existing page which contains standard wiki syntax. The fckeditor removes line breaks which corrupts your page layout. (But don't panic, the history function is always available.)The text is stored as *HTML* in the database. * Removal of unwanted, hidden text properties can be a hard job in some cases. * Using Netscape 7.1 browser, you cannot use the "browser page-back" navigation function beyond a page, where the WYSIWYG editor was invoked for page editing. * /Paste/ function (pasting clipboard content) seems to be prohibited - at least when using Netscape 7.1 browser. * "Show preview" function does not work properly. * Templates will work if they do *only* contain wiki syntax. * Special pages cannot be included. The biggest issue for us, obviously, was that it stored data as HTML. However, I see this page created as of July 17th, 2007( http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it storing wikitext, so we need to take another look. Thanks, John Q. DanTMan wrote: > I see we're loading the entire core for the YUI into Wikia. > I'm wondering, how much of this is going to stick around? I've actually > been working on ways to use the YUI and a few other things inside of > MediaWiki. (I Got YUI Animated Tabs working, and EditArea's Syntax > Highlighting enabled editor to work via Userscript only.) It could be > nice to use the YAHOO YUI Libs to take the place of some of the existing > things such as ShowHide and the cookie's used in some things like my > CharInsert hider with cookie persistence. > > On the note of editors. What's the status of the plans for WYSIWYG? I > looked over WYSIWYG extensions, and the FCKeditor+MediaWiki looks to me > like the best done editor. Even if Wikia is going to build it's own > WYSIWYG editor for MediaWiki using WikiWYG I'm considering making > helping the FCKeditor+MediaWiki project something for Wiki-Tools to do. > Other than just the WYSIWYG functions and fixing the bugs like broken > diff previews, I'm considering attempting to add a Syntax highlighting > mode for WikiText, CSS, JS, and I suppose a few other languages. > > Looking over Wikia's extensions familiarizing myself with what there is > to code. I notice some extensions I'd love to use, and some using tricks > I'd never dare use in a thousand years... What are release plans? There > are a few that would fit will for me, but the code is all GPL licensed. > And last I remember reading the GPL, it let you keep the code to > yourself. But if you distributed it you had to freely distribute it to > everyone. So I don't believe I could just use some of the extensions. On > that note, it would be nice to tag some of those stable extensions with > the ExtensionCredits and release them. > > From janek_listy at wp.pl Wed Aug 1 07:26:25 2007 From: janek_listy at wp.pl (Janek Kozicki) Date: Wed, 1 Aug 2007 09:26:25 +0200 Subject: [Wikia-l] CategoryTree depth=0 doesn't work In-Reply-To: <5ac482150707310246g572e399fh82fecb102778b38c@mail.gmail.com> References: <20070729170218.42c28d9a@absurd> <5ac482150707310246g572e399fh82fecb102778b38c@mail.gmail.com> Message-ID: <20070801092625.6061ac9b@absurd> Florian K?utner said: (by the date of Tue, 31 Jul 2007 11:46:24 +0200) > I felt free to already apply those changes to your wiki, I hope you > aren't mad at me. And I hope I didn't get you wrong and it looks like > expected. That's great, many thanks :) -- Janek Kozicki | From bjornar.fjar at gmail.com Wed Aug 1 08:18:08 2007 From: bjornar.fjar at gmail.com (=?ISO-8859-1?Q?Bj=F8rnar_Grip_Fj=E6r?=) Date: Wed, 1 Aug 2007 10:18:08 +0200 Subject: [Wikia-l] YUI && WYSIWYG && Wikia Extensions In-Reply-To: <46AFED47.4070806@wikia.com> References: <46AFC22A.4080103@telus.net> <46AFED47.4070806@wikia.com> Message-ID: Hello, > For FSKEditor and MediaWiki, we took a look at that before venturing > down the path of making our own. Here are some of the things I saw on > the FSKEditor extension page that led us to our decision: I assume this is a typo, and it's FCKEditor being discussed? > * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an > existing page which contains standard wiki syntax. The fckeditor > removes line breaks which corrupts your page layout. (But don't > panic, the history function is always available.)The text is > stored as *HTML* in the database. If you run $wgParser->parse(...) in the getContent function under includes/EditPage.php you can give the FCKEditor HTMLcode instead of Wikicode, so it doesn't mess up anything. This ofcourse gives you a table of contents etc as well, but that's easilly removed with a couple of preg_replace. It also removes the categories, which can be gathered with a preg_match before the content is parsed and appended or prepended (whichever you preffer) after the content is parsed. There's also the issue with templates, one way to do this is when you get the content before you parse it to HTML you use: $content = preg_replace('/({{[\w\d\ ]*}})/i', '$1', $this-mArticle->getContent()); > * Removal of unwanted, hidden text properties can be a hard job in > some cases. Do you have any examples? > * Using Netscape 7.1 browser, you cannot use the "browser page-back" > navigation function beyond a page, where the WYSIWYG editor was > invoked for page editing. > * /Paste/ function (pasting clipboard content) seems to be > prohibited - at least when using Netscape 7.1 browser. Haven't had this problem with any other browsers. > The biggest issue for us, obviously, was that it stored data as HTML. > However, I see this page created as of July 17th, 2007( > http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it > storing wikitext, so we need to take another look. A simple XML parser can parse the content to Wikicode before it's saved in the database. PHPs xml_parse should work fine. > Thanks, > John Q. -- Bj?rnar From johnq at wikia.com Wed Aug 1 10:08:44 2007 From: johnq at wikia.com (John Q) Date: Wed, 01 Aug 2007 18:08:44 +0800 Subject: [Wikia-l] YUI && WYSIWYG && Wikia Extensions In-Reply-To: <46AFED47.4070806@wikia.com> References: <46AFC22A.4080103@telus.net> <46AFED47.4070806@wikia.com> Message-ID: <46B05BAC.6080504@wikia.com> Hi, So we've started talking to the FCK Editor guys... in just the last few months they started taking their editor and trying to get it to work in a more integrated way with MediaWiki. The funny thing is that they did templates exactly how we were going to do them. The other funny thing is that they're in Warsaw, Poland... so Emil will be making a trip to see them as soon as he's back in Poland. As everyone knows, we've been developing a variant of the SocialText editor... but the FCK Editor guys started with something further along... so we're going to talk to them and probably try this out. It came up here at Wikimania just today, also... lots of coincidences. The funny part was hearing Brion Vibber, of all people, say that eventually all of mediawiki will move toward wysiwyg editing... that it's inevitable... (but Tim Starling added, "but it's going to take a while"). Anyway... nice spotting that development in FCK Editor DanTMan... I hadn't looked at it in a while. John Q. John Q wrote: > Hi DanTMan, > > We made a strategic decision to use YUI a while back. It's been > released openly, it's supported by Yahoo, it has incredible > documentation and example code, and it's tested on the core set of > browsers very thoroughly. So, yes, you can count on being able to use > YUI. > > Our servers currently compress the js files being downloaded and > shortly we'll be consolidating files for less back-and-forth. > > For FSKEditor and MediaWiki, we took a look at that before venturing > down the path of making our own. Here are some of the things I saw on > the FSKEditor extension page that led us to our decision: > > * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an > existing page which contains standard wiki syntax. The fckeditor > removes line breaks which corrupts your page layout. (But don't > panic, the history function is always available.)The text is > stored as *HTML* in the database. > * Removal of unwanted, hidden text properties can be a hard job in > some cases. > * Using Netscape 7.1 browser, you cannot use the "browser page-back" > navigation function beyond a page, where the WYSIWYG editor was > invoked for page editing. > * /Paste/ function (pasting clipboard content) seems to be > prohibited - at least when using Netscape 7.1 browser. > * "Show preview" function does not work properly. > * Templates will work if they do *only* contain wiki syntax. > * Special pages cannot be included. > > The biggest issue for us, obviously, was that it stored data as HTML. > However, I see this page created as of July 17th, 2007( > http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it > storing wikitext, so we need to take another look. > > Thanks, > John Q. > > > > > DanTMan wrote: >> I see we're loading the entire core for the YUI into Wikia. >> I'm wondering, how much of this is going to stick around? I've >> actually been working on ways to use the YUI and a few other things >> inside of MediaWiki. (I Got YUI Animated Tabs working, and EditArea's >> Syntax Highlighting enabled editor to work via Userscript only.) It >> could be nice to use the YAHOO YUI Libs to take the place of some of >> the existing things such as ShowHide and the cookie's used in some >> things like my CharInsert hider with cookie persistence. >> >> On the note of editors. What's the status of the plans for WYSIWYG? I >> looked over WYSIWYG extensions, and the FCKeditor+MediaWiki looks to >> me like the best done editor. Even if Wikia is going to build it's >> own WYSIWYG editor for MediaWiki using WikiWYG I'm considering making >> helping the FCKeditor+MediaWiki project something for Wiki-Tools to >> do. Other than just the WYSIWYG functions and fixing the bugs like >> broken diff previews, I'm considering attempting to add a Syntax >> highlighting mode for WikiText, CSS, JS, and I suppose a few other >> languages. >> >> Looking over Wikia's extensions familiarizing myself with what there >> is to code. I notice some extensions I'd love to use, and some using >> tricks I'd never dare use in a thousand years... What are release >> plans? There are a few that would fit will for me, but the code is >> all GPL licensed. And last I remember reading the GPL, it let you >> keep the code to yourself. But if you distributed it you had to >> freely distribute it to everyone. So I don't believe I could just use >> some of the extensions. On that note, it would be nice to tag some of >> those stable extensions with the ExtensionCredits and release them. >> >> > From johnq at wikia.com Wed Aug 1 10:21:56 2007 From: johnq at wikia.com (John Q) Date: Wed, 01 Aug 2007 18:21:56 +0800 Subject: [Wikia-l] YUI && WYSIWYG && Wikia Extensions In-Reply-To: References: <46AFC22A.4080103@telus.net> <46AFED47.4070806@wikia.com> Message-ID: <46B05EC4.20809@wikia.com> Hi Bj?rnar, comments in-line... Bj?rnar Grip Fj?r wrote: > Hello, > > > >> For FSKEditor and MediaWiki, we took a look at that before venturing >> down the path of making our own. Here are some of the things I saw on >> the FSKEditor extension page that led us to our decision: >> > > I assume this is a typo, and it's FCKEditor being discussed? > Correct, my mistake. > > >> * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an >> existing page which contains standard wiki syntax. The fckeditor >> removes line breaks which corrupts your page layout. (But don't >> panic, the history function is always available.)The text is >> stored as *HTML* in the database. >> > > If you run $wgParser->parse(...) in the getContent function under > includes/EditPage.php you can give the FCKEditor HTMLcode instead of > Wikicode, so it doesn't mess up anything. This ofcourse gives you a > table of contents etc as well, but that's easilly removed with a > couple of preg_replace. It also removes the categories, which can be > gathered with a preg_match before the content is parsed and appended > or prepended (whichever you preffer) after the content is parsed. > There's also the issue with templates, one way to do this is when you > get the content before you parse it to HTML you use: > $content = preg_replace('/({{[\w\d\ ]*}})/i', '$1', > $this-mArticle->getContent()); > > > >> * Removal of unwanted, hidden text properties can be a hard job in >> some cases. >> > > Do you have any examples? > > > >> * Using Netscape 7.1 browser, you cannot use the "browser page-back" >> navigation function beyond a page, where the WYSIWYG editor was >> invoked for page editing. >> * /Paste/ function (pasting clipboard content) seems to be >> prohibited - at least when using Netscape 7.1 browser. >> > > Haven't had this problem with any other browsers. > All the comments above were from the FCKEditor description pages themselves... so for examples, they would be the best people. :) But in the note I just sent, we're going to talk to them more closely as soon as Emil is back in Poland. > > >> The biggest issue for us, obviously, was that it stored data as HTML. >> However, I see this page created as of July 17th, 2007( >> http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it >> storing wikitext, so we need to take another look. >> > > A simple XML parser can parse the content to Wikicode before it's > saved in the database. PHPs xml_parse should work fine. > This part is not so simple with all the cases the wikitext parser handles. Brion, et al., were just talking about this and that to take advantage of most existing tools there would need to be a fixed grammar... but the current wikitext parser has lots of special handling which presents such a fixed grammar beening easily developed. Not being a wikitext parser expert... I'll take his word for it. The way that the FCKEditor guys have done this is making a round-trip to the back-end to run things through the parser... an approach we discussed for some other wysiwyg code we had before we started working with the SocialText code. I wish it were that easy (I really really wish it were that easy)... but I don't believe it is. > > >> Thanks, >> John Q. >> > > > From robinp at paradise.net.nz Wed Aug 1 11:10:24 2007 From: robinp at paradise.net.nz (Robin Forlonge Patterson) Date: Wed, 01 Aug 2007 23:10:24 +1200 Subject: [Wikia-l] Proposal: List wikias in need of adoption on thePortals References: <801553ab0707301144t6d34d7aam7d12aa3db4384c2c@mail.gmail.com> <46AE61D9.9090603@telus.net> Message-ID: <02f801c7d42c$8fc2b420$6d9237d2@633> Good work, Dan and Chad. I wonder whether a category talk page could be a good place to list inactive wikis in that category (similar idea to how we list inactive Society Gardens sites). Might be on the watchlists of some users of wikis in the category, the most likely people to look at an inactive one in the same category. [Mr] Robin Forlonge Patterson, 88 Motuhara Road, Plimmerton, Porirua City 5026, New Zealand http://genealogy.wikia.com/ a free cooperative MediaWiki site ----- Original Message ----- From: "DanTMan" To: "Central Wikia Mailing List" Sent: Tuesday, July 31, 2007 10:10 AM Subject: Re: [Wikia-l] Proposal: List wikias in need of adoption on thePortals > I haven't mentioned anything on it, but I started a little project I > call Adoption 2.0 ..... > The idea is to place an Adoption 2.0 spot somewhere in the Community > Portal or some other public area, and once in awhile tag another one of > the Adoptable wiki with the Adoption 2.0 template and have it become the > new featured one. Basically putting a random adoptable wiki out in the > open to see if anyone wants to adopt it. > > ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com > > Chad Lupkes wrote: > > I added His Dark Materials and DragonLance to the Books page as wikias > > that need adoption and attention. It makes sense to me to provide > > links like this so people can see what needs work. > > > > Any other ideas to direct people to the smaller wikia sites that need > > contributions? From dan_the_man at telus.net Wed Aug 1 12:08:13 2007 From: dan_the_man at telus.net (DanTMan) Date: Wed, 01 Aug 2007 05:08:13 -0700 Subject: [Wikia-l] YUI && WYSIWYG && Wikia Extensions In-Reply-To: References: <46AFC22A.4080103@telus.net> <46AFED47.4070806@wikia.com> Message-ID: <46B077AD.4060504@telus.net> We might want to reconsider the 'absolute' support when it comes to browsers. Do remember that we are also using YUI for the other things. You noted an error in Netscape 7.1 but if you go and look at YUI's graded browser support, Netscape isn't even on there as an A-Grade browser, which means that our normal fancy things aren't meant to support Netscape. So an error in another browser might be something of not to much consequence. http://developer.yahoo.com/yui/articles/gbs/ Hidden text, or hidden inputs? Well on the note of extra hidden inputs, there's something I should note. I haven't setup the code yet, but I'm hoping that FCKeditor can be altered to use the wikitext inside of the textarea field instead of having the HTML there. Even if that requires adding a hidden field containing the html that is currently stored there. This is because right now you need to disable the editor from your preferences if your browser cannot support it. The editor should be able to leave a good fallback if a user has no JS enabled. Also, the use of the diff preview does not work because it is sent html instead of WikiText. But considering that you can easily switch to a WikiText mode it should be possible to have it send that data to the diff. There's also another proposal I'm hoping they'll accept. (Because I'd rather help contribute to the FCKeditor+MediaWiki project, then start a fork of it) Many editors dislike the notion of WYSIWYG, but by far would Love a syntax highlighter. I managed to get EditArea to work purely with userjs, though my WikiText syntax file isn't to good, and the syntax Highlighter inside of EditArea is to limited. It does not support languages inside languages, and I can't create disabling matches such as making
 or  disable highlighting in an area.
Because of this,  I'm hopping to create a third Syntax Highlighting mode 
in FCKeditor+MediaWiki. I'm hoping to use the techniques in some of the 
better JS Syntax Highlighting tools (not specifically the editors) and a 
few of my own ideas, to create a good one as part of the editor.

In addition to that I'm thinking of a few plugin ideas. Such as requests 
to be able to grab WikiText from another Wiki such as Wikipedia or 
another Wikia wiki and import it into the current page.

I also do have a small liking to all the preview modes that are 
possible, and am hoping to create ways to let users use all of them, but 
not lose what is there:
* Hard Preview
** Advantages: Reliable, and we know that the display returned is what 
is actually going to be displayed after the save.
** Disadvantages: Requires a hard reload of the entire page.
* AJAX Preview (The one currently used in Wikia's WikiWYG editor)
** Advantages: Uses AJAX to avoid the need to reload the entire page and 
produce fair results on what is going to be seen.
** Disadvantages: The text is parsed in a method slightly different than 
with the HardPreviews, and in some cases may not match what is going to 
be outputted. The JS and CSS previews don't work because those require a 
page load, and because the preview is contained inside of a nice extra 
box and has no onload, some of the site's CSS won't properly apply to it 
so you can't preview that, and since there is no page load, JS like the 
Show/Hide, Sortable Tables, or a tab view cannot be previewed.
* WYSIWYG mode
** Advantages: No page load times, and it is possible to edit the HTML 
preview that you are seeing so the preview is live.
** Disadvantages: Things like templates, and other things are not viewed 
using this method. The html used is not the real html that comes out 
from a preview, but instead a mangled one used to allow you to see what 
you need to edit. So most css styling and other things will not apply to 
the live preview.
As you can see, each mode has it's advantages and disadvantages. 
Currently, Wikia's WikiWYG is one which only uses the AJAX preview 
method. And the FCKeditor+MediaWiki uses WYSIWYG and Hard Preview.
I'm hoping to add the ability to grab a proper preview for FCKeditor 
through AJAX to allow people to use the widest range of previews 
possible there are good reasons to use each of them.

I'm also hoping to add a few more abilities to the editor:
* Customize the built in CharInsert to make it a viable replacement for 
the normal CharInsert box.
* Allow support for other external libraries like YUI. Some wiki like 
Wikia and even me at Wiki-Tools are comfortable with loading a UI like 
YUI. FCKeditor currently uses it's own stuff. And while nice the editor 
is nice, I have an issue with the popup window used for things like the 
charinsert. Browsers with popup blockers will have issues with these 
that may confuse normal readers, and on a common browser it at times can 
take a bit for these to load. If you're doing a lot of inserts, then 
using these popup windows is very annoying. So i'm hoping to have an 
option for people to enable the use of external UI's like YUI and it's 
containers to replace the use of the windows when a site has them installed.
* I'm also hoping to make some buttons like the bold, italics, etc... 
Buttons work to insert the code when you are in modes such as syntax 
highlight and plain WikiText.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com

Bj?rnar Grip Fj?r wrote:
> Hello,
>
>
>   
>> For FSKEditor and MediaWiki, we took a look at that before venturing
>> down the path of making our own. Here are some of the things I saw on
>> the FSKEditor extension page that led us to our decision:
>>     
> I assume this is a typo, and it's FCKEditor being discussed?
>
>
>   
>>     * On a per-page-basis: Do not add the token "__USE_EDITOR__" on an
>>       existing page which contains standard wiki syntax. The fckeditor
>>       removes line breaks which corrupts your page layout. (But don't
>>       panic, the history function is always available.)The text is
>>       stored as *HTML* in the database.
>>     
>
> If you run $wgParser->parse(...) in the getContent function under
> includes/EditPage.php you can give the FCKEditor HTMLcode instead of
> Wikicode, so it doesn't mess up anything. This ofcourse gives you a
> table of contents etc as well, but that's easilly removed with a
> couple of preg_replace. It also removes the categories, which can be
> gathered with a preg_match before the content is parsed and appended
> or prepended (whichever you preffer) after the content is parsed.
> There's also the issue with templates, one way to do this is when you
> get the content before you parse it to HTML you use:
> $content = preg_replace('/({{[\w\d\ ]*}})/i', '$1',
> $this-mArticle->getContent());
>
>
>   
>>     * Removal of unwanted, hidden text properties can be a hard job in
>>       some cases.
>>     
>
> Do you have any examples?
>
>
>   
>>     * Using Netscape 7.1 browser, you cannot use the "browser page-back"
>>       navigation function beyond a page, where the WYSIWYG editor was
>>       invoked for page editing.
>>     * /Paste/ function (pasting clipboard content) seems to be
>>       prohibited - at least when using Netscape 7.1 browser.
>>     
>
> Haven't had this problem with any other browsers.
>
>
>   
>> The biggest issue for us, obviously, was that it stored data as HTML.
>> However, I see this page created as of July 17th, 2007(
>> http://mediawiki.fckeditor.net/index.php/Main_Page ) that discusses it
>> storing wikitext, so we need to take another look.
>>     
>
> A simple XML parser can parse the content to Wikicode before it's
> saved in the database. PHPs xml_parse should work fine.
>
>   
>> Thanks,
>> John Q.
>>     


From uberhalogen at googlemail.com  Thu Aug  2 15:59:11 2007
From: uberhalogen at googlemail.com (Uber Halogen)
Date: Thu, 2 Aug 2007 16:59:11 +0100
Subject: [Wikia-l] Problems with Google
In-Reply-To: <46AB846F.1040800@wikia.com>
References: <643068044.20070727231639@lexx.eu.org>
	<20070728014501.222a2fa0@absurd> <46AA98B1.8010006@wikia.com>
	
	
	<46AB846F.1040800@wikia.com>
Message-ID: <9e9606a90708020859r47c57acfrc271ba887f9350ca@mail.gmail.com>

I have been having similar problems with a non-WIkia wiki. One week we
were top in google for our 'main' search term - the next we were
40-something. Very odd, especially how this happens to big wikis (such
as the Muppet Wiki(a)) too.
-UH.


From johnq at wikia.com  Sat Aug  4 18:23:16 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 02:23:16 +0800
Subject: [Wikia-l] new code push to servers...
Message-ID: <46B4C414.10403@wikia.com>

Hi everyone,

We have some new code we're rolling out to the servers. As part of our 
normal release process, we move the new code to the production servers 
but have new features initially disabled... this lets us see any effects 
on the servers of the changed code base while we're in peak traffic 
hours. We'll watch it for an hour and if everything is ok, we'll start 
enabling features and letting you know so you can try them out.

If you see anything unexpected in the next couple of hours, please let 
us know.

Thanks,
John Q.



From johnq at wikia.com  Sat Aug  4 20:53:16 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 04:53:16 +0800
Subject: [Wikia-l] v2 skins available in skin preferences now...
Message-ID: <46B4E73C.40701@wikia.com>

Hi,

The v2 skins are now available for you to try out in your skin 
preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit 
awkward but when we introduce the color scheme chooser, there will be 
only one skin (Quartz) and then a list of color schemes 
(slate/smoke/custom/etc.).

Anyway, the v2 skins are available under your preferences. Also, when 
using them, if you click on your user name at the top you'll see "manage 
widgets" in the dropdown menu. You can take a look at the first few we 
have... we'll be working on more of those and putting them in the 
toolbar when they're available.

Also, as a preview, the social features are also live... go to your user 
page and look for a "profile" link on the top article bar. We still have 
some cleanup items on these that might take a day or two... if we find 
something egregious, we'll most likely turn it off until we have it 
figured out.

Thanks,
John Q.



From johnq at wikia.com  Sat Aug  4 21:01:31 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 05:01:31 +0800
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B4E73C.40701@wikia.com>
References: <46B4E73C.40701@wikia.com>
Message-ID: <46B4E92B.6000506@wikia.com>

Also, we have default wiki logos in the new dimensions pre-built. I took 
the existing logo and scaled it to fit, put it on the left side, then 
just put the name of the wiki in text in the remainder of the box.

To replace the default one we did, please upload a file and call it 
"Wiki_wide.png". Again, the dimensions are 266x75.  Anyway, these aren't 
fancy... but something to start with that's better than nothing I hope. 
The background color for the logos I did is the light grey of the smoke 
skin... but if you want the same logo with the dark bkd of slate, let me 
know and I'll do another run on the logos.

Thanks,
John Q.


John Q wrote:
> Hi,
>
> The v2 skins are now available for you to try out in your skin 
> preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit 
> awkward but when we introduce the color scheme chooser, there will be 
> only one skin (Quartz) and then a list of color schemes 
> (slate/smoke/custom/etc.).
>
> Anyway, the v2 skins are available under your preferences. Also, when 
> using them, if you click on your user name at the top you'll see 
> "manage widgets" in the dropdown menu. You can take a look at the 
> first few we have... we'll be working on more of those and putting 
> them in the toolbar when they're available.
>
> Also, as a preview, the social features are also live... go to your 
> user page and look for a "profile" link on the top article bar. We 
> still have some cleanup items on these that might take a day or two... 
> if we find something egregious, we'll most likely turn it off until we 
> have it figured out.
>
> Thanks,
> John Q.
>
>


From johnq at wikia.com  Sat Aug  4 21:28:54 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 05:28:54 +0800
Subject: [Wikia-l] test mail
Message-ID: <46B4EF96.5060800@wikia.com>

... just a test email. please ignore.


From johnq at wikia.com  Sat Aug  4 23:16:59 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 07:16:59 +0800
Subject: [Wikia-l] 4 custom nav links at the top...
Message-ID: <46B508EB.2020500@wikia.com>

Hi... to populate the 4 custom nav links at the top of the v2 skin... 
use the MediaWiki:NavLinks page...


For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks  ...


Thanks,
John Q.



From jamie at marveldatabase.com  Sun Aug  5 00:33:49 2007
From: jamie at marveldatabase.com (Jamie Hari)
Date: Sat, 4 Aug 2007 20:33:49 -0400
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B508EB.2020500@wikia.com>
References: <46B508EB.2020500@wikia.com>
Message-ID: <757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>

Hey John,

http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit

Ours is empty...
What is the format?
Newline delimited?


-- 
Jamie Hari
Editor-in-Chief
Marvel & DC Database Projects



On 8/4/07, John Q  wrote:
>
> Hi... to populate the 4 custom nav links at the top of the v2 skin...
> use the MediaWiki:NavLinks page...
>
>
> For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks  ...
>
>
> Thanks,
> John Q.
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070804/fef1941b/attachment.html 

From dan_the_man at telus.net  Sun Aug  5 00:50:24 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sat, 04 Aug 2007 17:50:24 -0700
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B4E73C.40701@wikia.com>
References: <46B4E73C.40701@wikia.com>
Message-ID: <46B51ED0.1090109@telus.net>

Ok, time for round 2 of hit & miss ^_^ lol...

Hit: The widget system is nice.
Miss: The widget bar puts it's curvy self in between 2 strait edged 
boxes. Opening up an area in between the options and the page is fine, 
but not when it doesn't flow.
Hit: A widget dashboard is nice.
Miss: In Slate the widgets inside are styled white like the page, but 
the edit and X links are still white making them invisible.
Miss: We have one dashboard and no links to it outside of the Special 
pages. I suggest using the parameter after the / to name dashboards, and 
placing a list of created dashboards and form to create new ones on the 
main dashboard page.
Suggestion: Many people have issues with the right sidebar, when 
managing widgets, give a symbol on the sidebar that will allow people to 
move it to the left. And even, give them the ability to create a 
secondary sidebar on the other side (For those users with exceptionally 
large screens that can make use of it) (Perhaps users with tall screens 
could toggle between double and single column modes for the toolbox, etc...)
Hit: Putting the MediaWiki:Sidebar inside of one box separated by 
headers, and giving it 2 columns was an awesome idea. It's optimized 
space for that, and an old sidebar which flowed past the screen now fits 
in a compact space.
Miss: You forgot to send the headers through the wfMsg, they are no 
longer localize-able, and for project like the WGEP that use something 
like sitename in the sidebar then use MediaWiki:Sitename to change that 
to the real name of the site that should display, we have a horrid 
'sitename' in our sidebar.
Hit: A RecentChanges widget is nice, helps keep track of it.
Miss: Things like author, time, and breaks between days are missing. 
Using the current one I can't accurately tell anything about the wiki.
Miss: You forgot to filter bot edits from the Widget. Irrelevant or en 
masse edits show up in the widget causing confusion.
Hit: A wide logo is a pretty good idea, gives good content space and 
doesn't take up any important room.
Miss: Erm... 266? What happened to 250 or 275... And what's with the 6?!
Miss: Background == Bad... 90% of Wikia logos as far as I remember are 
transparent. You're letting people colorize things, but putting a 
background in the logo is a bad idea. They should be made transparent to 
fit properly with all schemes (If you're worried about black/white 
differences, throw a border around the text. Or put a rounded box in the 
logo and put the transparency outside of it)
Suggestion: The Google ads, don't fit well with the small size, 
especially with only one ad in that large area. Using one or two of the 
Half Banners (234x60px) over top each other, or 2 Buttons (125x125px) 
side by side will give you more ads, take up less space, and won't leave 
a big block of blank space beside the ads. No Downside, Especially if 
you style them like they are on: 
https://www.google.com/adsense/static/en_US/AdFormats.html
Hit: The drop-down on the top is nice, and putting a userpage link in 
there will make it possible for me to keep the userpage/talkpage links 
on other wiki in my WikiSwitch.
Miss: You use the Username twice.
Welcome, Dantman! *Dantman*[#\/] - [Log out]
Take out one, and you have spare room for other things like [Switch 
user] or custom links.
Welcome, *Dantman!*[#\/] - [Log out] - [Switch user]
Perhaps the menu could even be a mouse-over.
((Note: I didn't notice the Long message there till I went to central. 
btw: Where is this message customized?))
Hit: The links at the top are nice, and customizing a set is nice to.
Miss: Something's bugged in the css. Half the time "Create an article" 
fits, the other half the article drops down to the next line.... On the 
Animepedia I'm on the Main Page, I hit edit and it drops down, I go back 
to the article and it's still dropped down (Even though before then it 
was fitting on that exact same page), then I hit the article link again 
and it jumps back up to stay on one line. All the while, there's nothing 
on the right to drop it down with my wide screen.
Suggestion: On the Special pages the "special" tab up top moves to the 
left. How about keeping it in the right, and moving the Page Title into 
the left of that bar.
Perhaps the margin between the title and the gold bar on normal pages 
should be reduced to. To much white there.
Hit: YUI is a nice system to use. And in loading them, users could 
probably use them to nicely improve on the existing scripts, and even 
make more flashy methods for them.
Miss: You're loading the YUI stuff badly.
* You loaded utilities.js and animation.js even though animation.js is 
one of the scripts compacted into utilities.js. And you're loading 
animation.js instead of animation-min.js
* You're loading utilities.js and yahoo-dom-event.js even though the 3 
things inside of yahoo-dom-event.js are already in utilities.js
* You're loading container-min.js and container_core-min.js even though 
container_core is just a lighter version of container for those not 
using all of the containers.
* You're loading the logger even though it's not something actively 
used. Though, I'd forgive that, since in truth. The logger is a nice JS 
debugging tool. I load it via Userscript on Wiki-Tools to help me iron 
out things till they work.
* You're loading all these scripts from the local wiki instead of 
loading them from the shared images server. That means more scripts are 
loaded for the client, and Wikia's servers serve out the same script 
again if the user goes to another wiki. When if they were loaded from 
images.wikia.com like I remember many used to be then they would only be 
loaded once between all Wikia wiki.

To summarize this is what you are loading:
/skins3/common/yui/yahoo-dom-event/yahoo-dom-event.js
/skins3/common/yui/utilities/utilities.js
/skins3/common/yui/animation/animation.js
/skins3/common/yui/container/container-min.js
/skins3/common/yui/container/container_core-min.js
/skins3/common/yui/autocomplete/autocomplete-min.js
This is something like what you should be loading: (Note that of course 
you'd use whatever directory you placed it in on images... or you could 
do what I did when I created http://skins.wiki-tools.com, and have a 
subdomain for shared skin/lib output. Though, I was considering moving 
libs like yui to a new http://lib.wiki-tools.com once I got my overload 
method finished.
http://images.wikia.com/skins3/common/yui/utilities/utilities.js
http://images.wikia.com/skins3/common/yui/container/container-min.js
http://images.wikia.com/skins3/common/yui/autocomplete/autocomplete-min.js

Do we see the problem here? The second one loads the exact same stuff 
that the first one does. Except it's not double loading 3 scripts, and 
it's not causing the Wikia servers to dish out duplicate scripts. If you 
have issues with different extensions loading them independantly. Create 
a YUILoader class, and call YUILoader->loadJS( 'utilities/utilities', 
'container/container', 'autocomplete/autocomplete' ); or such... In 
simple terms. Make it understand that utilities is the same as yahoo, 
animation, dom, event, etc... And have it save a list of what it needs 
to load. And when extensions load over half the needed scripts for 
utilities or yahoo-dom-event load those scripts instead and remove the 
others from the list. Also append -min.js to all the libraries except 
utilities and yahoo-dom-event. Yahoo even has a JS loader, PHP is much 
more robust you could easily create a better one in it.
Or, you could do this the lazy way... And load utilities, and all the 
widget stuff that isn't part of the compacted stuff as -min.js then be 
done with it cause you've loaded everything you'll ever need, and also 
loaded the extra yahoo widgets that users can use to create their own 
user js scripts. Like how I integrated YUI's tabs into MediaWiki on 
Wiki-Tools (except it would be cleaner using ones already loaded instead 
of loading via userscript).


Extension suggestion: Fix up the User style extension. If you agree that 
it's a fair idea to give user's the ability to customize a stylesheet 
for their own userspace/talkspace I would be happy to fix up the 
extension to something usable on Wikia on the development server. If you 
want a reason, compare:
http://www.wikia.com/index.php?title=User:Dantman&useskin=monobook to
http://www.wikia.com/index.php?title=User:Dantman&useskin=quartzslate
And think of how nice it would be for a user to customize the CSS of 
their userspace instead of using the ugly WikiText hacks to colorize and 
do strange things to the page.
As for the skin stuff... We can either load a skinname, or load a common 
and a skinname, or we could load a common css page and introduce a new 
"skin-....." into the body tag and allow for per skin css just like we 
have per-page css.

Extension suggestion: The social bookmarking links at the bottom are 
nice. It would be nice to have a set of messages and a parser hook that 
would let us create links that will show up there.
For a quick example idea on how to do it. Take the Animepedia, there's a 
anime encyclopedia called ANN which is nice to link to. It only does 
summaries, but it's nice for side information that we wouldn't bother 
listing. An example on how it would be setup to allow people to define a 
link that should show up there:
==[[MediaWiki:Social links]]==
Format: *    
* ann-anime http://www.animenewsnetwork.com/encyclopedia/anime.php?id=$1 
http:// http://images.wikia.com/anime/en/x/xy/Someimage.png ANN Anime
And on an article, example 1825 is ANN's id for the Anime version of Naruto
1825
Of course, you could just use social for the tag, or switch name with 
type. As for the Numbers, in simple terms, the input text would be split 
up by | and used to replace the numbers.
Of course, bearing that in mind, this example could have gone this way 
using the same extension work.
* ann http://www.animenewsnetwork.com/encyclopedia/{{lc:$1}}.php?id=$2 
http:// http://images.wikia.com/anime/en/x/xy/Someimage.png ANN 
{{ucfirst:$1}}
anime|1825
Then we wouldn't need to use 2 separate link types for the links.
However, that might or might not work depending on if you think that 
there should be one link of each type, or the number of links should be 
the same as the number of tags on the page.


Put V2 of the skins on the volunteer dev server, and I can fix half the 
problems for you on my own in a few hours of my large amount of wasted 
time having little to do.

Side note... That top menu might work pretty nice as a floated one. ^_^ 
You're already using YUI.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com

John Q wrote:
> Hi,
>
> The v2 skins are now available for you to try out in your skin 
> preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit 
> awkward but when we introduce the color scheme chooser, there will be 
> only one skin (Quartz) and then a list of color schemes 
> (slate/smoke/custom/etc.).
>
> Anyway, the v2 skins are available under your preferences. Also, when 
> using them, if you click on your user name at the top you'll see "manage 
> widgets" in the dropdown menu. You can take a look at the first few we 
> have... we'll be working on more of those and putting them in the 
> toolbar when they're available.
>
> Also, as a preview, the social features are also live... go to your user 
> page and look for a "profile" link on the top article bar. We still have 
> some cleanup items on these that might take a day or two... if we find 
> something egregious, we'll most likely turn it off until we have it 
> figured out.
>
> Thanks,
> John Q.
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070804/80a6c052/attachment.html 

From johnq at wikia.com  Sun Aug  5 02:01:49 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 10:01:49 +0800
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B51ED0.1090109@telus.net>
References: <46B4E73C.40701@wikia.com> <46B51ED0.1090109@telus.net>
Message-ID: <46B52F8D.3050609@wikia.com>

DanTMan.... always a pleasure. :)

comments in-line...

DanTMan wrote:
> Ok, time for round 2 of hit & miss ^_^ lol...
>
> Hit: The widget system is nice.
> Miss: The widget bar puts it's curvy self in between 2 strait edged 
> boxes. Opening up an area in between the options and the page is fine, 
> but not when it doesn't flow.
Actually, we had planned to make the widget boxes without curves... but 
we wanted to focus on getting this out so people could use it. We're 
going to have things to fix, undoubtedly, so we'll be working in that 
style change as we go.


> Hit: A widget dashboard is nice.
> Miss: In Slate the widgets inside are styled white like the page, but 
> the edit and X links are still white making them invisible.
> Miss: We have one dashboard and no links to it outside of the Special 
> pages. I suggest using the parameter after the / to name dashboards, 
> and placing a list of created dashboards and form to create new ones 
> on the main dashboard page.
Actually, we haven't *officially* released the WidgetDashboard... but 
I'm thinking a link to it will be in the username drop down on the top line.

I think what you're suggesting is the ability to create more than one 
dashboard... right now there's one per user, just like one user page, 
one user talk page, one user profile page, and then one user dashboard 
page. I can see how you'd fill it up in about 8ms... :)   ... let me 
think about how that would work and see what people want as we roll out 
more.


> Suggestion: Many people have issues with the right sidebar, when 
> managing widgets, give a symbol on the sidebar that will allow people 
> to move it to the left. And even, give them the ability to create a 
> secondary sidebar on the other side (For those users with 
> exceptionally large screens that can make use of it) (Perhaps users 
> with tall screens could toggle between double and single column modes 
> for the toolbox, etc...)
Interesting... I have a few thoughts on how to get people more choice 
there... let me get this out there and working then we can discuss.

> Hit: Putting the MediaWiki:Sidebar inside of one box separated by 
> headers, and giving it 2 columns was an awesome idea. It's optimized 
> space for that, and an old sidebar which flowed past the screen now 
> fits in a compact space.
> Miss: You forgot to send the headers through the wfMsg, they are no 
> longer localize-able, and for project like the WGEP that use something 
> like sitename in the sidebar then use MediaWiki:Sitename to change 
> that to the real name of the site that should display, we have a 
> horrid 'sitename' in our sidebar.
They will be... Inez did that and he usually sends everything through 
the system messages... so that will get fixed... thanks for spotting it. 
He's sleeping right now... but when I wake him up in an hour, he can 
start with that. :)
> Hit: A RecentChanges widget is nice, helps keep track of it.
> Miss: Things like author, time, and breaks between days are missing. 
> Using the current one I can't accurately tell anything about the wiki.
Yep, I know... we get that info from the API... I pointed that out and 
got a reason that I can't remember right now... but I just talked to 
YuriK in the hallway here and he said we should be able to get whatever 
we need there through the API... so that should get better soon.

> Miss: You forgot to filter bot edits from the Widget. Irrelevant or en 
> masse edits show up in the widget causing confusion.
We get this via the MediaWiki API ... I'll defer to the people pulling 
the data there.


> Hit: A wide logo is a pretty good idea, gives good content space and 
> doesn't take up any important room.
> Miss: Erm... 266? What happened to 250 or 275... And what's with the 6?!
Heh... ok, have to admit I didn't think about it from a round number 
point of view.    130x150 (pretty standard wiki logo size) = 260x75.  I 
think when I did this number a while ago... and I have to admit I don't 
remember off-hand where I got the 133x150 which turned into 266x75. We 
are actually thinking to make that area dynamic so that if the logo ends 
before 266 then the header links move left allowing lnoger links for the 
custom header links... but I wanted people to see how much space they 
*have* before starting to deal with dynamic spacing there.

> Miss: Background == Bad... 90% of Wikia logos as far as I remember are 
> transparent. You're letting people colorize things, but putting a 
> background in the logo is a bad idea. They should be made transparent 
> to fit properly with all schemes (If you're worried about black/white 
> differences, throw a border around the text. Or put a rounded box in 
> the logo and put the transparency outside of it)
Yeah, this was me and a bot I wrote between 4am and 6am yesterday. The 
idea was just to get something in there for the first day...  I expect 
most people will want to replace this anyway. I'll look into running the 
bot again and putting white around the text with imagemagick and make 
the bkd invisible. Need sleep first (and fixing anything broken will 
come first).


> Suggestion: The Google ads, don't fit well with the small size, 
> especially with only one ad in that large area. Using one or two of 
> the Half Banners (234x60px) over top each other, or 2 Buttons 
> (125x125px) side by side will give you more ads, take up less space, 
> and won't leave a big block of blank space beside the ads. No 
> Downside, Especially if you style them like they are on: 
> https://www.google.com/adsense/static/en_US/AdFormats.html
Actually, I did a mockup with two 125 x 125's ... but actually the word 
is that no one really buys those sizes, so 180x150 was there already 
from the previous version. Having the two half banner's is not a bad 
idea... but 99% of the list is groaning at you now. :)


> Hit: The drop-down on the top is nice, and putting a userpage link in 
> there will make it possible for me to keep the userpage/talkpage links 
> on other wiki in my WikiSwitch.
> Miss: You use the Username twice.
> Welcome, Dantman! *Dantman*[#\/] - [Log out]
> Take out one, and you have spare room for other things like [Switch 
> user] or custom links.
> Welcome, *Dantman!*[#\/] - [Log out] - [Switch user]
> Perhaps the menu could even be a mouse-over.
> ((Note: I didn't notice the Long message there till I went to central. 
> btw: Where is this message customized?))
Actually, on our test wiki ... fp012.qa.wikia.com... it looks the way 
you suggest. I'll have Emil take a look. Will ask the designer about 
mouse-over vs. click drop-down.


> Hit: The links at the top are nice, and customizing a set is nice to.
> Miss: Something's bugged in the css. Half the time "Create an article" 
> fits, the other half the article drops down to the next line.... On 
> the Animepedia I'm on the Main Page, I hit edit and it drops down, I 
> go back to the article and it's still dropped down (Even though before 
> then it was fitting on that exact same page), then I hit the article 
> link again and it jumps back up to stay on one line. All the while, 
> there's nothing on the right to drop it down with my wide screen.
Ok... we need to take a look at that. Any consistency in the behavior 
you can figure out before we get there would be appreciated.


> Suggestion: On the Special pages the "special" tab up top moves to the 
> left. How about keeping it in the right, and moving the Page Title 
> into the left of that bar.
> Perhaps the margin between the title and the gold bar on normal pages 
> should be reduced to. To much white there.
Will take a look.

> Hit: YUI is a nice system to use. And in loading them, users could 
> probably use them to nicely improve on the existing scripts, and even 
> make more flashy methods for them.
> Miss: You're loading the YUI stuff badly.
> * You loaded utilities.js and animation.js even though animation.js is 
> one of the scripts compacted into utilities.js. And you're loading 
> animation.js instead of animation-min.js
:) I'll follow up with Inez. We actually are going to be consolidating a 
lot of the separate js files into one to reduce back-and-forths... and 
Yahoo just released a new version of YUI a couple of days ago that only 
loads the elements needed on a particular page. We're not going to 
upgrade to that until this release has settled, though.
> * You're loading utilities.js and yahoo-dom-event.js even though the 3 
> things inside of yahoo-dom-event.js are already in utilities.js
> * You're loading container-min.js and container_core-min.js even 
> though container_core is just a lighter version of container for those 
> not using all of the containers.
> * You're loading the logger even though it's not something actively 
> used. Though, I'd forgive that, since in truth. The logger is a nice 
> JS debugging tool. I load it via Userscript on Wiki-Tools to help me 
> iron out things till they work.
Yes, it's being loaded for debugging purposes. All of this stuff is new 
enough that we'll need that there for a while yet. I'll ask Inez about 
the lib overlap and see.
> * You're loading all these scripts from the local wiki instead of 
> loading them from the shared images server. That means more scripts 
> are loaded for the client, and Wikia's servers serve out the same 
> script again if the user goes to another wiki. When if they were 
> loaded from images.wikia.com like I remember many used to be then they 
> would only be loaded once between all Wikia wiki.
Yes, they'll be loaded from images... Emil noticed this late last night. 
That will be changed shortly.


>
> To summarize this is what you are loading:
> /skins3/common/yui/yahoo-dom-event/yahoo-dom-event.js
> /skins3/common/yui/utilities/utilities.js
> /skins3/common/yui/animation/animation.js
> /skins3/common/yui/container/container-min.js
> /skins3/common/yui/container/container_core-min.js
> /skins3/common/yui/autocomplete/autocomplete-min.js
> This is something like what you should be loading: (Note that of 
> course you'd use whatever directory you placed it in on images... or 
> you could do what I did when I created http://skins.wiki-tools.com, 
> and have a subdomain for shared skin/lib output. Though, I was 
> considering moving libs like yui to a new http://lib.wiki-tools.com 
> once I got my overload method finished.
> http://images.wikia.com/skins3/common/yui/utilities/utilities.js
> http://images.wikia.com/skins3/common/yui/container/container-min.js
> http://images.wikia.com/skins3/common/yui/autocomplete/autocomplete-min.js
>
> Do we see the problem here? The second one loads the exact same stuff 
> that the first one does. Except it's not double loading 3 scripts, and 
> it's not causing the Wikia servers to dish out duplicate scripts. If 
> you have issues with different extensions loading them independantly. 
> Create a YUILoader class, and call YUILoader->loadJS( 
> 'utilities/utilities', 'container/container', 
> 'autocomplete/autocomplete' ); or such... In simple terms. Make it 
> understand that utilities is the same as yahoo, animation, dom, event, 
> etc... And have it save a list of what it needs to load. And when 
> extensions load over half the needed scripts for utilities or 
> yahoo-dom-event load those scripts instead and remove the others from 
> the list. Also append -min.js to all the libraries except utilities 
> and yahoo-dom-event. Yahoo even has a JS loader, PHP is much more 
> robust you could easily create a better one in it.
> Or, you could do this the lazy way... And load utilities, and all the 
> widget stuff that isn't part of the compacted stuff as -min.js then be 
> done with it cause you've loaded everything you'll ever need, and also 
> loaded the extra yahoo widgets that users can use to create their own 
> user js scripts. Like how I integrated YUI's tabs into MediaWiki on 
> Wiki-Tools (except it would be cleaner using ones already loaded 
> instead of loading via userscript).
>
>
Ditto with above. I need to have Inez take a look.  :)

> Extension suggestion: Fix up the User style extension. If you agree 
> that it's a fair idea to give user's the ability to customize a 
> stylesheet for their own userspace/talkspace I would be happy to fix 
> up the extension to something usable on Wikia on the development 
> server. If you want a reason, compare:
> http://www.wikia.com/index.php?title=User:Dantman&useskin=monobook to
> http://www.wikia.com/index.php?title=User:Dantman&useskin=quartzslate
> And think of how nice it would be for a user to customize the CSS of 
> their userspace instead of using the ugly WikiText hacks to colorize 
> and do strange things to the page.
> As for the skin stuff... We can either load a skinname, or load a 
> common and a skinname, or we could load a common css page and 
> introduce a new "skin-....." into the body tag and allow for per skin 
> css just like we have per-page css.
Yes, Emil was taking a look at this just a few hours ago... it's a bug 
that it's not getting included... but I think there might be a caching 
issue through our squids going on there as well. We'll get that going as 
soon as we can.


>
> Extension suggestion: The social bookmarking links at the bottom are 
> nice. It would be nice to have a set of messages and a parser hook 
> that would let us create links that will show up there.
> For a quick example idea on how to do it. Take the Animepedia, there's 
> a anime encyclopedia called ANN which is nice to link to. It only does 
> summaries, but it's nice for side information that we wouldn't bother 
> listing. An example on how it would be setup to allow people to define 
> a link that should show up there:
> ==[[MediaWiki:Social links]]==
> Format: *    
> * ann-anime 
> http://www.animenewsnetwork.com/encyclopedia/anime.php?id=$1 http:// 
> http://images.wikia.com/anime/en/x/xy/Someimage.png ANN Anime
> And on an article, example 1825 is ANN's id for the Anime version of 
> Naruto
> 1825
> Of course, you could just use social for the tag, or switch name with 
> type. As for the Numbers, in simple terms, the input text would be 
> split up by | and used to replace the numbers.
> Of course, bearing that in mind, this example could have gone this way 
> using the same extension work.
> * ann http://www.animenewsnetwork.com/encyclopedia/{{lc:$1}}.php?id=$2 
> http:// http://images.wikia.com/anime/en/x/xy/Someimage.png ANN 
> {{ucfirst:$1}}
> anime|1825
> Then we wouldn't need to use 2 separate link types for the links.
> However, that might or might not work depending on if you think that 
> there should be one link of each type, or the number of links should 
> be the same as the number of tags on the page.
Yes, we need to make this customizable for other countries/languages 
anyway since their social bookmarking links are different. First goal 
was get this out there to play with.

>
>
> Put V2 of the skins on the volunteer dev server, and I can fix half 
> the problems for you on my own in a few hours of my large amount of 
> wasted time having little to do.
>
> Side note... That top menu might work pretty nice as a floated one. 
> ^_^ You're already using YUI.


Ok, DanTMan.... good stuff.

John Q.


>
> ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com
> John Q wrote:
>> Hi,
>>
>> The v2 skins are now available for you to try out in your skin 
>> preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit 
>> awkward but when we introduce the color scheme chooser, there will be 
>> only one skin (Quartz) and then a list of color schemes 
>> (slate/smoke/custom/etc.).
>>
>> Anyway, the v2 skins are available under your preferences. Also, when 
>> using them, if you click on your user name at the top you'll see "manage 
>> widgets" in the dropdown menu. You can take a look at the first few we 
>> have... we'll be working on more of those and putting them in the 
>> toolbar when they're available.
>>
>> Also, as a preview, the social features are also live... go to your user 
>> page and look for a "profile" link on the top article bar. We still have 
>> some cleanup items on these that might take a day or two... if we find 
>> something egregious, we'll most likely turn it off until we have it 
>> figured out.
>>
>> Thanks,
>> John Q.
>>
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>   


From dan_the_man at telus.net  Sun Aug  5 04:43:34 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sat, 04 Aug 2007 21:43:34 -0700
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B52F8D.3050609@wikia.com>
References: <46B4E73C.40701@wikia.com> <46B51ED0.1090109@telus.net>
	<46B52F8D.3050609@wikia.com>
Message-ID: <46B55576.2010207@telus.net>

-----The message didn't get received by the list or archives since it 
was to long so I'm truncating and resending this-----
^_^ Let's see if I can make inline comments without breaking anything, 
rofl... I have a thunderbird extension which takes any sort of html, or 
text quotes and nicely formats them. So whether you use some html tags 
or just >'s at the start of the line, it turns them into some sort of 
html quote element that is uniformly styled. (Which is why I prefer HTML 
quotes being sent to the server instead of >'s because if mailman 
formats those and breaks the lines that start with > I end up with some 
sort of weird thing where there is a quote, non-quote, and quote on the 
next line because Mailman inserted a newline pushing the text out of the 
text type quote.

John Q wrote:
> DanTMan.... always a pleasure. :)  
^_^ you think that now... but you don't know how many times Jack 
Phoenix, and one or two other users has poked me and said to get hired 
onto the tech team... I'm not so sure how this would go on payroll... lol
> comments in-line...
>
> DanTMan wrote:
>   
>> Ok, time for round 2 of hit & miss ^_^ lol...
>>
>> Hit: The widget system is nice.
>> Miss: The widget bar puts it's curvy self in between 2 strait edged 
>> boxes. Opening up an area in between the options and the page is fine, 
>>
>>     
> but not when it doesn't flow.Actually, we had planned to make the widget boxes without curves... but 
> we wanted to focus on getting this out so people could use it. We're 
> going to have things to fix, undoubtedly, so we'll be working in that 
> style change as we go.
>
>
>   
>> Hit: A widget dashboard is nice.
>> Miss: In Slate the widgets inside are styled white like the page, but 
>> the edit and X links are still white making them invisible.
>> Miss: We have one dashboard and no links to it outside of the Special 
>> pages. I suggest using the parameter after the / to name dashboards, 
>> and placing a list of created dashboards and form to create new ones 
>> on the main dashboard page.
>>     
> Actually, we haven't *officially* released the WidgetDashboard... but 
> I'm thinking a link to it will be in the username drop down on the top line.
>
> I think what you're suggesting is the ability to create more than one 
> dashboard... right now there's one per user, just like one user page, 
> one user talk page, one user profile page, and then one user dashboard 
> page. I can see how you'd fill it up in about 8ms... :)   ... let me 
> think about how that would work and see what people want as we roll out 
> more.  
Yup... more than one dashboard would be nice. And some sort of quick 
links to them. Perhaps a widget to link to widgets ^_^ rofl... Stick one 
in your sidebar to get quick links to your dashboard. Actually for that 
matter, a Widget which you could hit an add button and create links 
inside of would be nice. Thinking it over, there's a possibility that 
using some form trickery, drag n' drop stuff, and various events that 
you could create one that will let someone drag a url from the page and 
drop it into that box to create a new link there.

I don't know about only having one though ;) Don't forget... We may have 
only one Profile because it's a new feature. But as for Userpages and 
Talkpages. We archive our talkpages with sub talk pages. And don't 
forget about our gigantic userspace. Every user has a near unlimited 
region of space to fill up. Every page that begins with User:Username/ 
belongs to you... And MediaWiki even recognizes that as a fact because 
it adds your various User contributions and other links to the toolbox 
on those pages. ^_^ my userpage itself is actually comprised of around 
15 pages together. Lots of transclusions, and even more parserfunctions 
which make a single set of pages on the Animepedia look customized to 
each individual site when a Bot simply copies all those to the other 
wiki it's told to.
>> Hit: A wide logo is a pretty good idea, gives good content space and 
>> doesn't take up any important room.
>> Miss: Erm... 266? What happened to 250 or 275... And what's with the 6?!
>>     
> Heh... ok, have to admit I didn't think about it from a round number 
> point of view.    130x150 (pretty standard wiki logo size) = 260x75.  I 
> think when I did this number a while ago... and I have to admit I don't 
> remember off-hand where I got the 133x150 which turned into 266x75. We 
> are actually thinking to make that area dynamic so that if the logo ends 
> before 266 then the header links move left allowing lnoger links for the 
> custom header links... but I wanted people to see how much space they 
> *have* before starting to deal with dynamic spacing there.
>   
^_^ if you need some consolidation... The logo in Monobook is actually 
155x155px... We've just been lieing to everyone that it's 150, rofl...
>> Hit: The drop-down on the top is nice, and putting a userpage link in 
>> there will make it possible for me to keep the userpage/talkpage links 
>> on other wiki in my WikiSwitch.
>> Miss: You use the Username twice.
>> Welcome, Dantman! *Dantman*[#\/] - [Log out]
>> Take out one, and you have spare room for other things like [Switch 
>> user] or custom links.
>> Welcome, *Dantman!*[#\/] - [Log out] - [Switch user]
>> Perhaps the menu could even be a mouse-over.
>> ((Note: I didn't notice the Long message there till I went to central. 
>> btw: Where is this message customized?))
>>     
> Actually, on our test wiki ... fp012.qa.wikia.com... it looks the way 
> you suggest. I'll have Emil take a look. Will ask the designer about 
> mouse-over vs. click drop-down.
>   
If you use Mouse-Over you can provide a CSS fallback for those without 
JS that looks the same. So at this second:
Miss: The dropdown has no CSS fallback, anyone without JS that doesn't 
know how to use URL trickery or search tricks to get to prefs or switch 
skins has no way to get to their userpage, talkpage, contributions 
pages, or even get to their preferences page to switch their skins.
Hit: Widgets work even without JS. I disabled JS, and even though 
they're more dynamic then the rest of the site the RC Widget still 
showed up in the sidebar. That's a big hit, even if someone goes to a 
less functional computer, they still have the normal functionality of 
the widgets they configured elsewhere.
>> Hit: The links at the top are nice, and customizing a set is nice to.
>> Miss: Something's bugged in the css. Half the time "Create an article" 
>> fits, the other half the article drops down to the next line.... On 
>> the Animepedia I'm on the Main Page, I hit edit and it drops down, I 
>> go back to the article and it's still dropped down (Even though before 
>> then it was fitting on that exact same page), then I hit the article 
>> link again and it jumps back up to stay on one line. All the while, 
>> there's nothing on the right to drop it down with my wide screen.
>>     
> Ok... we need to take a look at that. Any consistency in the behavior 
> you can figure out before we get there would be appreciated.
>
>   
>> Hit: YUI is a nice system to use. And in loading them, users could 
>> probably use them to nicely improve on the existing scripts, and even 
>> make more flashy methods for them.
>> Miss: You're loading the YUI stuff badly.
>> * You loaded utilities.js and animation.js even though animation.js is 
>> one of the scripts compacted into utilities.js. And you're loading 
>> animation.js instead of animation-min.js
>>     
> :) I'll follow up with Inez. We actually are going to be consolidating a 
> lot of the separate js files into one to reduce back-and-forths... and 
> Yahoo just released a new version of YUI a couple of days ago that only 
> loads the elements needed on a particular page. We're not going to 
> upgrade to that until this release has settled, though.
>   
>> * You're loading utilities.js and yahoo-dom-event.js even though the 3 
>> things inside of yahoo-dom-event.js are already in utilities.js
>> * You're loading container-min.js and container_core-min.js even 
>> though container_core is just a lighter version of container for those 
>> not using all of the containers.
>> * You're loading the logger even though it's not something actively 
>> used. Though, I'd forgive that, since in truth. The logger is a nice 
>> JS debugging tool. I load it via Userscript on Wiki-Tools to help me 
>> iron out things till they work.
>>     
> Yes, it's being loaded for debugging purposes. All of this stuff is new 
> enough that we'll need that there for a while yet. I'll ask Inez about 
> the lib overlap and see.
>   
>> * You're loading all these scripts from the local wiki instead of 
>> loading them from the shared images server. That means more scripts 
>> are loaded for the client, and Wikia's servers serve out the same 
>> script again if the user goes to another wiki. When if they were 
>> loaded from images.wikia.com like I remember many used to be then they 
>> would only be loaded once between all Wikia wiki.
>>     
> Yes, they'll be loaded from images... Emil noticed this late last night. 
> That will be changed shortly.
>   
>> To summarize this is what you are loading:
>> /skins3/common/yui/yahoo-dom-event/yahoo-dom-event.js
>> /skins3/common/yui/utilities/utilities.js
>> /skins3/common/yui/animation/animation.js
>> /skins3/common/yui/container/container-min.js
>> /skins3/common/yui/container/container_core-min.js
>> /skins3/common/yui/autocomplete/autocomplete-min.js
>> This is something like what you should be loading: (Note that of 
>> course you'd use whatever directory you placed it in on images... or 
>> you could do what I did when I created http://skins.wiki-tools.com, 
>> and have a subdomain for shared skin/lib output. Though, I was 
>> considering moving libs like yui to a new http://lib.wiki-tools.com 
>> once I got my overload method finished.
>> http://images.wikia.com/skins3/common/yui/utilities/utilities.js
>> http://images.wikia.com/skins3/common/yui/container/container-min.js
>> http://images.wikia.com/skins3/common/yui/autocomplete/autocomplete-min.js
>>
>> Do we see the problem here? The second one loads the exact same stuff 
>> that the first one does. Except it's not double loading 3 scripts, and 
>> it's not causing the Wikia servers to dish out duplicate scripts. If 
>> you have issues with different extensions loading them independantly. 
>> Create a YUILoader class, and call YUILoader->loadJS( 
>> 'utilities/utilities', 'container/container', 
>> 'autocomplete/autocomplete' ); or such... In simple terms. Make it 
>> understand that utilities is the same as yahoo, animation, dom, event, 
>> etc... And have it save a list of what it needs to load. And when 
>> extensions load over half the needed scripts for utilities or 
>> yahoo-dom-event load those scripts instead and remove the others from 
>> the list. Also append -min.js to all the libraries except utilities 
>> and yahoo-dom-event. Yahoo even has a JS loader, PHP is much more 
>> robust you could easily create a better one in it.
>> Or, you could do this the lazy way... And load utilities, and all the 
>> widget stuff that isn't part of the compacted stuff as -min.js then be 
>> done with it cause you've loaded everything you'll ever need, and also 
>> loaded the extra yahoo widgets that users can use to create their own 
>> user js scripts. Like how I integrated YUI's tabs into MediaWiki on 
>> Wiki-Tools (except it would be cleaner using ones already loaded 
>> instead of loading via userscript).
>>
>>
>>     
> Ditto with above. I need to have Inez take a look.  :)
>   
Three comments, I sort of hit you over and over on that issue... rofl
>> Extension suggestion: Fix up the User style extension. If you agree 
>> that it's a fair idea to give user's the ability to customize a 
>> stylesheet for their own userspace/talkspace I would be happy to fix 
>> up the extension to something usable on Wikia on the development 
>> server. If you want a reason, compare:
>> http://www.wikia.com/index.php?title=User:Dantman&useskin=monobook to
>> http://www.wikia.com/index.php?title=User:Dantman&useskin=quartzslate
>> And think of how nice it would be for a user to customize the CSS of 
>> their userspace instead of using the ugly WikiText hacks to colorize 
>> and do strange things to the page.
>> As for the skin stuff... We can either load a skinname, or load a 
>> common and a skinname, or we could load a common css page and 
>> introduce a new "skin-....." into the body tag and allow for per skin 
>> css just like we have per-page css.
>>     
> Yes, Emil was taking a look at this just a few hours ago... it's a bug 
> that it's not getting included... but I think there might be a caching 
> issue through our squids going on there as well. We'll get that going as 
> soon as we can.
>   
Bug, userstyles... ^_^ I think we're on 2 different pages.
So... userstyles aren't being included into V2 as a bug right now? No 
wonder the JS I put in my global.js to enable EditArea when I'm editing 
isn't working. O_o but then why do I see the script tag in the source, 
and my JS overview tell me that my code is being included. And yet, 
EditArea isn't working and I have no JS errors. T_T I guess I did the JS 
testing for elements to well, and it's just failing without creating any 
JS errors because the elements it's looking for aren't there.

But to summarize what I was meaning. Was not a userscripts userstyles 
that a user sees, but styles (never scripts) that a user uses to control 
not what he see's everywhere, but what everyone including him sees on 
his userpage. The idea just comes from this extension:
http://www.mediawiki.org/wiki/Extension:UserPageStyles
However despite the fact that Jim R. Wilson (Jimbojw 
) created it... I find it a 
little poorly done... It's using a

in_array ('sysop', $wgUser->getGroups())

Instead of a $wgUser->isAllowed( 'hideStyles' ); Which also means that 
sysops are only being considered instead of being able to be extended to 
staff.
And I don't like the fact that other user's styles aren't seen by 
admins. Not everyone is going to use it harmfully, I want to be able to 
see the nice things they do to their userpage to. And if i'm styling my 
own userpage to fix it up so that it's not buggy in looks, or I'm using 
it to color the background instead of using WikiText hacks, I don't want 
admins seeing a Messed up userpage because they can't see the custom 
styles. That defeats the purpose of the extension.
Most likely I'd do a few things to do that. Like... Add a 
&userpagestyles= parameter to force them on or off against the default. 
Disable the userstyles in edit mode for everyone's userspace/usertalk 
except your own unless you set &userpagestyles=true. Anyone who wishes 
to see the styles while editing someone else's page can use JS to append 
a checkbox with name="userpagestyles" value="true" method="get" to the 
edit form and they can check it off to let them view it. Also, that 
&userpagestyles= can be used on the userpages themselves to disable the 
styles and regain whatever buttons were hidden from you by them. Plus, 
on the User:Username/style.css or whatever page we choose to use the 
styles would be disabled as well. So if you have an issue with a user 
using the CSS harmfully on their userpage. Just hit up the search or the 
url, to add the /style.css or whatever we choose to use and the styles 
will already be disabled there. Then as an admin just erase the stuff 
from the page. (.css pages are already protected, so a vandal can't come 
in and edit that page to make a user's userpage become screwed up for 
everyone.

It's a great concept, with a little better ideas that could be used to 
implement it without causing vandalism issues.
If you like the idea. I can setup the extension on the Volunteer 
Development server in the /extensions/wikia folder, and start tweaking 
it to make it coded right and use better methods of working nicely 
without being a vandal issue.
>> Extension suggestion: The social bookmarking links at the bottom are 
>> nice. It would be nice to have a set of messages and a parser hook 
>> that would let us create links that will show up there.
>> For a quick example idea on how to do it. Take the Animepedia, there's 
>> a anime encyclopedia called ANN which is nice to link to. It only does 
>> summaries, but it's nice for side information that we wouldn't bother 
>> listing. An example on how it would be setup to allow people to define 
>> a link that should show up there:
>> ==[[MediaWiki:Social links]]==
>> Format: *    
>> * ann-anime 
>> http://www.animenewsnetwork.com/encyclopedia/anime.php?id=$1 http:// 
>> http://images.wikia.com/anime/en/x/xy/Someimage.png ANN Anime
>> And on an article, example 1825 is ANN's id for the Anime version of 
>> Naruto
>> 1825
>> Of course, you could just use social for the tag, or switch name with 
>> type. As for the Numbers, in simple terms, the input text would be 
>> split up by | and used to replace the numbers.
>> Of course, bearing that in mind, this example could have gone this way 
>> using the same extension work.
>> * ann http://www.animenewsnetwork.com/encyclopedia/{{lc:$1}}.php?id=$2 
>> http:// http://images.wikia.com/anime/en/x/xy/Someimage.png ANN 
>> {{ucfirst:$1}}
>> anime|1825
>> Then we wouldn't need to use 2 separate link types for the links.
>> However, that might or might not work depending on if you think that 
>> there should be one link of each type, or the number of links should 
>> be the same as the number of tags on the page.
>>     
> Yes, we need to make this customizable for other countries/languages 
> anyway since their social bookmarking links are different. First goal 
> was get this out there to play with.
^_^ So 2 goals... A MediaWiki message that lets the actual social bookmarking links be altered to fit countries and languages. And a MediaWiki message and parser hook that lets wiki create custom social links to other sites that are directed at the current page through a parser hook in the page. (Perhaps double that hook with a ParserFunction just incase someone finds some reason to put it in a template. Say, turning my example into a {{ANN|anime|id}} template that takes less typing for the users and is a little more intuitive without adding extra things to do in programming.

>> Put V2 of the skins on the volunteer dev server, and I can fix half 
>> the problems for you on my own in a few hours of my large amount of 
>> wasted time having little to do.
>>
>> Side note... That top menu might work pretty nice as a floated one. 
>> ^_^ You're already using YUI.    
> Ok, DanTMan.... good stuff.
>
> John Q.
>
>   
>> ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com    
~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com



From dan_the_man at telus.net  Sun Aug  5 05:35:04 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sat, 04 Aug 2007 22:35:04 -0700
Subject: [Wikia-l] Install V2 on fp001
Message-ID: <46B56188.60208@telus.net>

John Q. Could you please put V2 of the skins on the Dev server. 
GreenReaper came up with a skin test... I'm not a fan of the logo bit, 
but he gave me an interesting idea.
http://images2.wikia.com/furry/images/3/36/Greenreaper_skintest.png
I want to experiment with a few things like Expanding the content area, 
collapsing/resizing the sidebar, expanding the edit area and a few other 
small but interesting tricks that look small and flashy, but drastically 
make editing and viewing smoother and easier to do.
Perhaps putting V2 releases as they come out, onto fp001 and letting the 
volunteers copy them to something like quartzslate-dantman and muck 
around with things there to see if some interesting new features may be 
possible is a good idea?

-- 
~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com



From inez at wikia.com  Sun Aug  5 05:45:02 2007
From: inez at wikia.com (=?UTF-8?B?SW5leiBLb3JjennFhHNraQ==?=)
Date: Sun, 05 Aug 2007 13:45:02 +0800
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B52F8D.3050609@wikia.com>
References: <46B4E73C.40701@wikia.com> <46B51ED0.1090109@telus.net>
	<46B52F8D.3050609@wikia.com>
Message-ID: <46B563DE.8050303@wikia.com>

John Q pisze:
>> Hit: Putting the MediaWiki:Sidebar inside of one box separated by 
>> headers, and giving it 2 columns was an awesome idea. It's optimized 
>> space for that, and an old sidebar which flowed past the screen now 
>> fits in a compact space.
>> Miss: You forgot to send the headers through the wfMsg, they are no 
>> longer localize-able, and for project like the WGEP that use something 
>> like sitename in the sidebar then use MediaWiki:Sitename to change 
>> that to the real name of the site that should display, we have a 
>> horrid 'sitename' in our sidebar.
> They will be... Inez did that and he usually sends everything through 
> the system messages... so that will get fixed... thanks for spotting it. 
> He's sleeping right now... but when I wake him up in an hour, he can 
> start with that. :)

Hi

I just fix it, should be ok now.

Inez


From johnq at wikia.com  Sun Aug  5 06:42:08 2007
From: johnq at wikia.com (John Q)
Date: Sun, 05 Aug 2007 14:42:08 +0800
Subject: [Wikia-l] Install V2 on fp001
In-Reply-To: <46B56188.60208@telus.net>
References: <46B56188.60208@telus.net>
Message-ID: <46B57140.20607@wikia.com>

Hi DanTMan... figuring out stuff we haven't thought of is good. Green is 
always creative and a smart guy. Let's talk about how we help each other 
while also letting us stay in business. :) :) :)

... but I will be off the air for at least 10-12 hours if all goes as 
planned... the last 4 days were actually just one long day, so I have 
some sleep to catch up on.

Talk to you soon
John Q.

p.s., while I'm sleeping try not to storm the castle. :)

DanTMan wrote:
> John Q. Could you please put V2 of the skins on the Dev server. 
> GreenReaper came up with a skin test... I'm not a fan of the logo bit, 
> but he gave me an interesting idea.
> http://images2.wikia.com/furry/images/3/36/Greenreaper_skintest.png
> I want to experiment with a few things like Expanding the content area, 
> collapsing/resizing the sidebar, expanding the edit area and a few other 
> small but interesting tricks that look small and flashy, but drastically 
> make editing and viewing smoother and easier to do.
> Perhaps putting V2 releases as they come out, onto fp001 and letting the 
> volunteers copy them to something like quartzslate-dantman and muck 
> around with things there to see if some interesting new features may be 
> possible is a good idea?
>
>   


From inez at wikia.com  Sun Aug  5 07:31:15 2007
From: inez at wikia.com (=?UTF-8?B?SW5leiBLb3JjennFhHNraQ==?=)
Date: Sun, 05 Aug 2007 15:31:15 +0800
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
References: <46B508EB.2020500@wikia.com>
	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
Message-ID: <46B57CC3.2080900@wikia.com>

Jamie Hari pisze:
> Hey John,
> 
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit 
> 
> 
> Ours is empty...
> What is the format?
> Newline delimited?

Hi,

The format is one title in line delimited by empty line. I just set 
example links for marveldatabase.com.

Nota that this is probably temporary format, we are looking for suggestions.

Inez

> 
> 
> -- 
> Jamie Hari
> Editor-in-Chief
> Marvel & DC Database Projects
> 
> 
> 
> On 8/4/07, *John Q* > wrote:
> 
>     Hi... to populate the 4 custom nav links at the top of the v2 skin...
>     use the MediaWiki:NavLinks page...
> 
> 
>     For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks
>       ...
> 
> 
>     Thanks,
>     John Q.
> 
>     _______________________________________________
>     Wikia-l mailing list
>     Wikia-l at wikia.com 
>     http://lists.wikia.com/mailman/listinfo/wikia-l
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l



From jamie at marveldatabase.com  Sun Aug  5 08:34:57 2007
From: jamie at marveldatabase.com (Jamie Hari)
Date: Sun, 5 Aug 2007 04:34:57 -0400
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B57CC3.2080900@wikia.com>
References: <46B508EB.2020500@wikia.com>
	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
	<46B57CC3.2080900@wikia.com>
Message-ID: <757d22db0708050134r601c82e9wd7b2a785d6fbd9c9@mail.gmail.com>

Excellent! Thanks!


I suppose my next question is: How would one modify the other 4 existing
links at the top?

i.e. :

Home 
Forum 
Random page 
Create a new page 

I would like to customize "Forum" and "Create a new page" to our existing
forums and new page creation area.


Cheers,


-- 
Jamie Hari
Editor-in-Chief
Marvel & DC Database Projects


On 8/5/07, Inez Korczy?ski  wrote:
>
> Jamie Hari pisze:
> > Hey John,
> >
> >
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
> > <
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
> >
> >
> > Ours is empty...
> > What is the format?
> > Newline delimited?
>
> Hi,
>
> The format is one title in line delimited by empty line. I just set
> example links for marveldatabase.com.
>
> Nota that this is probably temporary format, we are looking for
> suggestions.
>
> Inez
>
> >
> >
> > --
> > Jamie Hari
> > Editor-in-Chief
> > Marvel & DC Database Projects
> >
> >
> >
> > On 8/4/07, *John Q* > wrote:
> >
> >     Hi... to populate the 4 custom nav links at the top of the v2
> skin...
> >     use the MediaWiki:NavLinks page...
> >
> >
> >     For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks
> >       ...
> >
> >
> >     Thanks,
> >     John Q.
> >
> >     _______________________________________________
> >     Wikia-l mailing list
> >     Wikia-l at wikia.com 
> >     http://lists.wikia.com/mailman/listinfo/wikia-l
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Wikia-l mailing list
> > Wikia-l at wikia.com
> > http://lists.wikia.com/mailman/listinfo/wikia-l
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070805/66f8a992/attachment.html 

From dan_the_man at telus.net  Sun Aug  5 08:35:13 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sun, 05 Aug 2007 01:35:13 -0700
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B57CC3.2080900@wikia.com>
References: <46B508EB.2020500@wikia.com>	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
	<46B57CC3.2080900@wikia.com>
Message-ID: <46B58BC1.5020500@telus.net>

Then I would suggest a list format. * has been used for the sidebar for 
a good long time. It is easy to parse out into a list, and when rendered 
in WikiText it gives a nice list of things. If I remember right, the 
Licenses message uses it to. It would be the best to use.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com

Inez Korczy?ski wrote:
> Jamie Hari pisze:
>   
>> Hey John,
>>
>> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit 
>> 
>>
>> Ours is empty...
>> What is the format?
>> Newline delimited?
>>     
>
> Hi,
>
> The format is one title in line delimited by empty line. I just set 
> example links for marveldatabase.com.
>
> Nota that this is probably temporary format, we are looking for suggestions.
>
> Inez
>
>   
>> -- 
>> Jamie Hari
>> Editor-in-Chief
>> Marvel & DC Database Projects
>>
>>
>>
>> On 8/4/07, *John Q* > wrote:
>>
>>     Hi... to populate the 4 custom nav links at the top of the v2 skin...
>>     use the MediaWiki:NavLinks page...
>>
>>
>>     For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks
>>       ...
>>
>>
>>     Thanks,
>>     John Q.
>>
>>     _______________________________________________
>>     Wikia-l mailing list
>>     Wikia-l at wikia.com 
>>     http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>     
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   


From jamie at marveldatabase.com  Sun Aug  5 08:39:51 2007
From: jamie at marveldatabase.com (Jamie Hari)
Date: Sun, 5 Aug 2007 04:39:51 -0400
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B58BC1.5020500@telus.net>
References: <46B508EB.2020500@wikia.com>
	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
	<46B57CC3.2080900@wikia.com> <46B58BC1.5020500@telus.net>
Message-ID: <757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>

Oops!


It also appears as though an alternate display text isn't an option:


News:Contents|News

Comics:Contents|Comics

Marvel Database:Database|Database

Gallery:Contents|Gallery


I don't want it to say "News:Contents", I'd rather it just say, "News".
If I do the above, the links simply don't appear.


That would be a good feature request... ;)


Jamie


On 8/5/07, DanTMan  wrote:
>
> Then I would suggest a list format. * has been used for the sidebar for
> a good long time. It is easy to parse out into a list, and when rendered
> in WikiText it gives a nice list of things. If I remember right, the
> Licenses message uses it to. It would be the best to use.
>
> ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment
> Project, and Wiki-Tools.com
>
> Inez Korczy?ski wrote:
> > Jamie Hari pisze:
> >
> >> Hey John,
> >>
> >>
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
> >> <
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
> >
> >>
> >> Ours is empty...
> >> What is the format?
> >> Newline delimited?
> >>
> >
> > Hi,
> >
> > The format is one title in line delimited by empty line. I just set
> > example links for marveldatabase.com.
> >
> > Nota that this is probably temporary format, we are looking for
> suggestions.
> >
> > Inez
> >
> >
> >> --
> >> Jamie Hari
> >> Editor-in-Chief
> >> Marvel & DC Database Projects
> >>
> >>
> >>
> >> On 8/4/07, *John Q* > wrote:
> >>
> >>     Hi... to populate the 4 custom nav links at the top of the v2
> skin...
> >>     use the MediaWiki:NavLinks page...
> >>
> >>
> >>     For example, http://xyz.wikia.com/wiki/MediaWiki:NavLinks
> >>       ...
> >>
> >>
> >>     Thanks,
> >>     John Q.
> >>
> >>     _______________________________________________
> >>     Wikia-l mailing list
> >>     Wikia-l at wikia.com 
> >>     http://lists.wikia.com/mailman/listinfo/wikia-l
> >>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Wikia-l mailing list
> >> Wikia-l at wikia.com
> >> http://lists.wikia.com/mailman/listinfo/wikia-l
> >>
> >
> > _______________________________________________
> > Wikia-l mailing list
> > Wikia-l at wikia.com
> > http://lists.wikia.com/mailman/listinfo/wikia-l
> >
> >
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070805/a5b35ebc/attachment.html 

From greenreaper at hotmail.com  Sun Aug  5 08:42:15 2007
From: greenreaper at hotmail.com (Laurence Parry)
Date: Sun, 5 Aug 2007 04:42:15 -0400
Subject: [Wikia-l] Install V2 on fp001
References: <46B56188.60208@telus.net> <46B57140.20607@wikia.com>
Message-ID: 

> Hi DanTMan... figuring out stuff we haven't thought of is good. Green is
> always creative and a smart guy. Let's talk about how we help each other
> while also letting us stay in business. :) :) :)

Oh, don't worry, the ad blocking isn't being done skin-side, it's on my 
client's userContent.css. I don't see most regularly-sized ads anywhere.

(I even took time to check that it was aligned properly with IE . . . ;-)

-- 
Laurence "GreenReaper" Parry
http://greenreaper.co.uk/
"Eternity lies ahead of us, and behind. Have you drunk your fill?"
 



From greenreaper at hotmail.com  Sun Aug  5 18:53:42 2007
From: greenreaper at hotmail.com (Laurence Parry)
Date: Sun, 5 Aug 2007 14:53:42 -0400
Subject: [Wikia-l] Floating images not extending page length
Message-ID: 

We are used to having floating images that are longer than the length of 
short articles. They extend the article page length in Monobook, but this no 
longer occurs in Quartz, which looks odd:
http://furry.wikia.com/wiki/User:GreenReaper/A_Tale_of_Two_Wikis

(technically, it *does* extend the container, but the footer bar is not at 
the end of that, so nor is the white page)

-- 
Laurence "GreenReaper" Parry
http://greenreaper.co.uk/
"Eternity lies ahead of us, and behind. Have you drunk your fill?" 



From martineznovo at gmail.com  Sun Aug  5 19:06:38 2007
From: martineznovo at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Mart=EDnez?=)
Date: Sun, 5 Aug 2007 21:06:38 +0200
Subject: [Wikia-l] Floating images not extending page length
In-Reply-To: 
References: 
Message-ID: 

Ok, and look at those white borders around the images. This can be
fixed using this CSS code in Common.css, or change it in the main.css
of Monobook... It's done in 
with great results (look at the image on the green background),

div.tright {
  border-width: 0;
  margin: 0.5em 0 0.8em 1.4em;
}
div.tleft {
  border-width: 0;
  margin: 0.5em 1.4em 0.8em 0;
}

Wait!, but if it's Quartz skin, why the Monobook css is loaded?


2007/8/5, Laurence Parry :
> We are used to having floating images that are longer than the length of
> short articles. They extend the article page length in Monobook, but this no
> longer occurs in Quartz, which looks odd:
> http://furry.wikia.com/wiki/User:GreenReaper/A_Tale_of_Two_Wikis
>
> (technically, it *does* extend the container, but the footer bar is not at
> the end of that, so nor is the white page)
>
> --
> Laurence "GreenReaper" Parry
> http://greenreaper.co.uk/
> "Eternity lies ahead of us, and behind. Have you drunk your fill?"
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>


From martineznovo at gmail.com  Sun Aug  5 19:44:36 2007
From: martineznovo at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Mart=EDnez?=)
Date: Sun, 5 Aug 2007 21:44:36 +0200
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B4E73C.40701@wikia.com>
References: <46B4E73C.40701@wikia.com>
Message-ID: 

Some issues with the widget sidebar links:

The links have a encoded space (%20) prepended to the url. It seems
not to be a problem in Firefox, but it must be avoided.

The "id" attribute of that links has a """ character appended.

An example of the HTML source:





2007/8/4, John Q :
> Hi,
>
> The v2 skins are now available for you to try out in your skin
> preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit
> awkward but when we introduce the color scheme chooser, there will be
> only one skin (Quartz) and then a list of color schemes
> (slate/smoke/custom/etc.).
>
> Anyway, the v2 skins are available under your preferences. Also, when
> using them, if you click on your user name at the top you'll see "manage
> widgets" in the dropdown menu. You can take a look at the first few we
> have... we'll be working on more of those and putting them in the
> toolbar when they're available.
>
> Also, as a preview, the social features are also live... go to your user
> page and look for a "profile" link on the top article bar. We still have
> some cleanup items on these that might take a day or two... if we find
> something egregious, we'll most likely turn it off until we have it
> figured out.
>
> Thanks,
> John Q.
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>


From cizania at gmail.com  Sun Aug  5 19:54:49 2007
From: cizania at gmail.com (=?ISO-8859-1?Q?Ciza=F1a?=)
Date: Sun, 5 Aug 2007 14:54:49 -0500
Subject: [Wikia-l] Floating images not extending page length
In-Reply-To: 
References: 
	
Message-ID: 

On 8/5/07, Jes?s Mart?nez  wrote:
>
> Wait!, but if it's Quartz skin, why the Monobook css is loaded?
>

because all the "content" (now "article") format is completely based on
monobook, the only things that have to be remove are, content, all portlets
types (navigation, personal cations), modifications to the monobook so it
fits wikia monobook needs and some some tweaks here and there but the rest
stays as it is.


On 8/5/07, Laurence Parry  wrote:
>
> We are used to having floating images that are longer than the length of
> short articles. They extend the article page length in Monobook, but this
> no
> longer occurs in Quartz, which looks odd:
> http://furry.wikia.com/wiki/User:GreenReaper/A_Tale_of_Two_Wikis
>
> (technically, it *does* extend the container, but the footer bar is not at
> the end of that, so nor is the white page)
>
> --
> Laurence "GreenReaper" Parry
> http://greenreaper.co.uk/
> "Eternity lies ahead of us, and behind. Have you drunk your fill?"


A fast solution while they fix it, is to add a category to that page.

Ciz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070805/8e0ea16b/attachment.html 

From johnq at wikia.com  Sun Aug  5 21:26:08 2007
From: johnq at wikia.com (John Q)
Date: Mon, 06 Aug 2007 05:26:08 +0800
Subject: [Wikia-l] Floating images not extending page length
In-Reply-To: 
References: 
Message-ID: <46B64070.3000102@wikia.com>

Hi... ok, we'll fix it up. Christian will take a look at the css.
Thanks,
John Q.


Laurence Parry wrote:
> We are used to having floating images that are longer than the length of 
> short articles. They extend the article page length in Monobook, but this no 
> longer occurs in Quartz, which looks odd:
> http://furry.wikia.com/wiki/User:GreenReaper/A_Tale_of_Two_Wikis
>
> (technically, it *does* extend the container, but the footer bar is not at 
> the end of that, so nor is the white page)
>
>   


From johnq at wikia.com  Sun Aug  5 21:34:43 2007
From: johnq at wikia.com (John Q)
Date: Mon, 06 Aug 2007 05:34:43 +0800
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: 
References: <46B4E73C.40701@wikia.com>
	
Message-ID: <46B64273.30707@wikia.com>

Hi Jesus...

Can you point me to the wiki where you see this? Since the first part of 
the uri is missing it looks like this might be an interwiki link not 
getting processed and instead a space gets inserted.

Let me know where you see this please.

Thanks,
John Q.




Jes?s Mart?nez wrote:
> Some issues with the widget sidebar links:
>
> The links have a encoded space (%20) prepended to the url. It seems
> not to be a problem in Firefox, but it must be avoided.
>
> The "id" attribute of that links has a """ character appended.
>
> An example of the HTML source:
>
> 
>
>
>
> 2007/8/4, John Q :
>   
>> Hi,
>>
>> The v2 skins are now available for you to try out in your skin
>> preferences. Look for QuartzSlate and QuartzSmoke... the naming is bit
>> awkward but when we introduce the color scheme chooser, there will be
>> only one skin (Quartz) and then a list of color schemes
>> (slate/smoke/custom/etc.).
>>
>> Anyway, the v2 skins are available under your preferences. Also, when
>> using them, if you click on your user name at the top you'll see "manage
>> widgets" in the dropdown menu. You can take a look at the first few we
>> have... we'll be working on more of those and putting them in the
>> toolbar when they're available.
>>
>> Also, as a preview, the social features are also live... go to your user
>> page and look for a "profile" link on the top article bar. We still have
>> some cleanup items on these that might take a day or two... if we find
>> something egregious, we'll most likely turn it off until we have it
>> figured out.
>>
>> Thanks,
>> John Q.
>>
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>     
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   


From uberhalogen at googlemail.com  Sun Aug  5 21:39:00 2007
From: uberhalogen at googlemail.com (Uber Halogen)
Date: Sun, 5 Aug 2007 22:39:00 +0100
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>
References: <46B508EB.2020500@wikia.com>
	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
	<46B57CC3.2080900@wikia.com> <46B58BC1.5020500@telus.net>
	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>
Message-ID: <9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>

On 05/08/2007, Jamie Hari  wrote:
> Oops!
>
>
> It also appears as though an alternate display text isn't an option:
>
>
> News:Contents|News
>
> Comics:Contents|Comics
>
> Marvel Database:Database|Database
>
> Gallery:Contents|Gallery
>
>
> I don't want it to say "News:Contents", I'd rather it just say, "News".
> If I do the above, the links simply don't appear.
>
>
> That would be a good feature request... ;)
>
>
> Jamie
>
>
>
> On 8/5/07, DanTMan  wrote:
> > Then I would suggest a list format. * has been used for the sidebar for
> > a good long time. It is easy to parse out into a list, and when rendered
> > in WikiText it gives a nice list of things. If I remember right, the
> > Licenses message uses it to. It would be the best to use.
> >
> > ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment
> Project, and Wiki-Tools.com
> >
> > Inez Korczy?ski wrote:
> > > Jamie Hari pisze:
> > >
> > >> Hey John,
> > >>
> > >>
> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
> > >>
> 
> > >>
> > >> Ours is empty...
> > >> What is the format?
> > >> Newline delimited?
> > >>
> > >
> > > Hi,
> > >
> > > The format is one title in line delimited by empty line. I just set
> > > example links for marveldatabase.com.
> > >
> > > Nota that this is probably temporary format, we are looking for
> suggestions.
> > >
> > > Inez
> > >
> > >
> > >> --
> > >> Jamie Hari
> > >> Editor-in-Chief
> > >> Marvel & DC Database Projects
> > >>
> > >>
> > >>
> > >> On 8/4/07, *John Q* > wrote:
> > >>
> > >>     Hi... to populate the 4 custom nav links at the top of the v2
> skin...
> > >>     use the MediaWiki:NavLinks page...
> > >>
> > >>
> > >>     For example,
> http://xyz.wikia.com/wiki/MediaWiki:NavLinks
> > >>     
> ...
> > >>
> > >>
> > >>     Thanks,
> > >>     John Q.
> > >>
> > >>     _______________________________________________
> > >>     Wikia-l mailing list
> > >>     Wikia-l at wikia.com 
> > >>     http://lists.wikia.com/mailman/listinfo/wikia-l
> > >>
> > >>
> > >>
> ------------------------------------------------------------------------
> > >>
> > >> _______________________________________________
> > >> Wikia-l mailing list
> > >> Wikia-l at wikia.com
> > >> http://lists.wikia.com/mailman/listinfo/wikia-l
> > >>
> > >
> > > _______________________________________________
> > > Wikia-l mailing list
> > > Wikia-l at wikia.com
> > > http://lists.wikia.com/mailman/listinfo/wikia-l
> > >
> > >
> > _______________________________________________
> > Wikia-l mailing list
> > Wikia-l at wikia.com
> > http://lists.wikia.com/mailman/listinfo/wikia-l
> >
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>
Since the code already exists in the monobook skin it would be easy to
replicate. Please may I also direct the development team at an idea to
create a function which does what the sidebar in monobook currently
does. It could be put in Skin.php - there are many uses for it and
currently I am aware of several things that would be benefit from such
a function. The main advantage would be that it can more easily be
fixed if flaws are found and it would save disk space in the long run.
Thanks,
MinuteElectron.

From johnq at wikia.com  Sun Aug  5 22:12:15 2007
From: johnq at wikia.com (John Q)
Date: Mon, 06 Aug 2007 06:12:15 +0800
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
References: <46B508EB.2020500@wikia.com>	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>	<46B57CC3.2080900@wikia.com>
	<46B58BC1.5020500@telus.net>	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>
	<9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
Message-ID: <46B64B3F.8010502@wikia.com>

Yes, that's the general plan. :)  But it brings up a question that we 
decided to wait before implementing so we could ask everyone...

Currently, we have the MediaWiki:NavLinks article which populates 4 
links into the header area. We're also taking monobook's sidebar and 
populating the contents of that into the right nav area. My guess would 
be that the 4 links you'd want in the header are already in the monobook 
sidebar and the result would be 4 duplicate links. One solution to this 
is to create another MediaWiki article that would be the equivalent of 
monobook sidebar but only for the v2 skin... then you could avoid 
duplicate links. Downside is two lists to maintain.

Thoughts?

Thanks,
John Q.






Uber Halogen wrote:
> On 05/08/2007, Jamie Hari  wrote:
>   
>> Oops!
>>
>>
>> It also appears as though an alternate display text isn't an option:
>>
>>
>> News:Contents|News
>>
>> Comics:Contents|Comics
>>
>> Marvel Database:Database|Database
>>
>> Gallery:Contents|Gallery
>>
>>
>> I don't want it to say "News:Contents", I'd rather it just say, "News".
>> If I do the above, the links simply don't appear.
>>
>>
>> That would be a good feature request... ;)
>>
>>
>> Jamie
>>
>>
>>
>> On 8/5/07, DanTMan  wrote:
>>     
>>> Then I would suggest a list format. * has been used for the sidebar for
>>> a good long time. It is easy to parse out into a list, and when rendered
>>> in WikiText it gives a nice list of things. If I remember right, the
>>> Licenses message uses it to. It would be the best to use.
>>>
>>> ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment
>>>       
>> Project, and Wiki-Tools.com
>>     
>>> Inez Korczy?ski wrote:
>>>       
>>>> Jamie Hari pisze:
>>>>
>>>>         
>>>>> Hey John,
>>>>>
>>>>>
>>>>>           
>> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
>>     
>> 
>>     
>>>>> Ours is empty...
>>>>> What is the format?
>>>>> Newline delimited?
>>>>>
>>>>>           
>>>> Hi,
>>>>
>>>> The format is one title in line delimited by empty line. I just set
>>>> example links for marveldatabase.com.
>>>>
>>>> Nota that this is probably temporary format, we are looking for
>>>>         
>> suggestions.
>>     
>>>> Inez
>>>>
>>>>
>>>>         
>>>>> --
>>>>> Jamie Hari
>>>>> Editor-in-Chief
>>>>> Marvel & DC Database Projects
>>>>>
>>>>>
>>>>>
>>>>> On 8/4/07, *John Q* > wrote:
>>>>>
>>>>>     Hi... to populate the 4 custom nav links at the top of the v2
>>>>>           
>> skin...
>>     
>>>>>     use the MediaWiki:NavLinks page...
>>>>>
>>>>>
>>>>>     For example,
>>>>>           
>> http://xyz.wikia.com/wiki/MediaWiki:NavLinks
>>     
>>>>>     
>>>>>           
>> ...
>>     
>>>>>     Thanks,
>>>>>     John Q.
>>>>>
>>>>>     _______________________________________________
>>>>>     Wikia-l mailing list
>>>>>     Wikia-l at wikia.com 
>>>>>     http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>>
>>>>>
>>>>>
>>>>>           
>> ------------------------------------------------------------------------
>>     
>>>>> _______________________________________________
>>>>> Wikia-l mailing list
>>>>> Wikia-l at wikia.com
>>>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> Wikia-l mailing list
>>>> Wikia-l at wikia.com
>>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> Wikia-l mailing list
>>> Wikia-l at wikia.com
>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>
>>>       
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>
>>     
> Since the code already exists in the monobook skin it would be easy to
> replicate. Please may I also direct the development team at an idea to
> create a function which does what the sidebar in monobook currently
> does. It could be put in Skin.php - there are many uses for it and
> currently I am aware of several things that would be benefit from such
> a function. The main advantage would be that it can more easily be
> fixed if flaws are found and it would save disk space in the long run.
> Thanks,
> MinuteElectron.
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   


From dan_the_man at telus.net  Sun Aug  5 23:40:44 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sun, 05 Aug 2007 16:40:44 -0700
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
References: <46B508EB.2020500@wikia.com>	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>	<46B57CC3.2080900@wikia.com>
	<46B58BC1.5020500@telus.net>	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>
	<9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
Message-ID: <46B65FFC.2090402@telus.net>

I actually already have code for something like that:

	/***** Functions to do things that aren't in SkinTemplate by default *****/
	/**
	 * Build an array of links for a box specified by a message name
	 *
	 * @return array
	 * @private
	 */
	function buildLinkBox( $msgName ) {
		global $parserMemc, $wgEnableSidebarCache;
		global $wgLang, $wgContLang;

		$fname = 'BurningDespair::buildLinkBox';

		wfProfileIn( $fname );

		$key = wfMemcKey( $msgName );
		$cacheBar = $wgEnableSidebarCache &&
			($wgLang->getCode() == $wgContLang->getCode());
		
		if ($cacheBar) {
			$cachedbar = $parserMemc->get( $key );
			if ($cachedbar!="") {
				wfProfileOut($fname);
				return $cachedbar;
			}
		}

		$links = array();
		$lines = explode( "\n", wfMsgForContent( $msgName ) );
		foreach ($lines as $line) {
			if (strpos($line, '*') !== 0)
				continue;
			if (strpos($line, '|') !== false) { // sanity check
				$line = explode( '|' , trim($line, '* '), 2 );
				$link = wfMsgForContent( $line[0] );
				if ($link == '-')
					continue;
				if (wfEmptyMsg($line[1], $text = wfMsg($line[1])))
					$text = $line[1];
				if (wfEmptyMsg($line[0], $link))
					$link = $line[0];

				if ( preg_match( '/^(?:' . wfUrlProtocols() . ')/', $link ) ) {
					$href = $link;
				} else {
					$title = Title::newFromText( $link );
					if ( $title ) {
						$title = $title->fixSpecialName();
						$href = $title->getLocalURL();
					} else {
						$href = 'INVALID-TITLE';
					}
				}

				$links[] = array(
					'text' => $text,
					'href' => $href,
					'id' => 'n-' . strtr($line[1], ' ', '-'),
					'active' => false
				);
			}
		}
		if ($cacheBar)
			$parserMemc->set( $key, $links, 86400 );
		wfProfileOut( $fname );
		return $links;
	}

I just stick it in the Skin's template and use a $this->set( ... ); to 
set up other parts of data to have the message data.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com



Uber Halogen wrote:
> On 05/08/2007, Jamie Hari  wrote:
>   
>> Oops!
>>
>>
>> It also appears as though an alternate display text isn't an option:
>>
>>
>> News:Contents|News
>>
>> Comics:Contents|Comics
>>
>> Marvel Database:Database|Database
>>
>> Gallery:Contents|Gallery
>>
>>
>> I don't want it to say "News:Contents", I'd rather it just say, "News".
>> If I do the above, the links simply don't appear.
>>
>>
>> That would be a good feature request... ;)
>>
>>
>> Jamie
>>
>>
>>
>> On 8/5/07, DanTMan  wrote:
>>     
>>> Then I would suggest a list format. * has been used for the sidebar for
>>> a good long time. It is easy to parse out into a list, and when rendered
>>> in WikiText it gives a nice list of things. If I remember right, the
>>> Licenses message uses it to. It would be the best to use.
>>>
>>> ~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment
>>>       
>> Project, and Wiki-Tools.com
>>     
>>> Inez Korczy?ski wrote:
>>>       
>>>> Jamie Hari pisze:
>>>>
>>>>         
>>>>> Hey John,
>>>>>
>>>>>
>>>>>           
>> http://en.marveldatabase.com/index.php?title=MediaWiki:NavLinks&action=edit
>>     
>> 
>>     
>>>>> Ours is empty...
>>>>> What is the format?
>>>>> Newline delimited?
>>>>>
>>>>>           
>>>> Hi,
>>>>
>>>> The format is one title in line delimited by empty line. I just set
>>>> example links for marveldatabase.com.
>>>>
>>>> Nota that this is probably temporary format, we are looking for
>>>>         
>> suggestions.
>>     
>>>> Inez
>>>>
>>>>
>>>>         
>>>>> --
>>>>> Jamie Hari
>>>>> Editor-in-Chief
>>>>> Marvel & DC Database Projects
>>>>>
>>>>>
>>>>>
>>>>> On 8/4/07, *John Q* > wrote:
>>>>>
>>>>>     Hi... to populate the 4 custom nav links at the top of the v2
>>>>>           
>> skin...
>>     
>>>>>     use the MediaWiki:NavLinks page...
>>>>>
>>>>>
>>>>>     For example,
>>>>>           
>> http://xyz.wikia.com/wiki/MediaWiki:NavLinks
>>     
>>>>>     
>>>>>           
>> ...
>>     
>>>>>     Thanks,
>>>>>     John Q.
>>>>>
>>>>>     _______________________________________________
>>>>>     Wikia-l mailing list
>>>>>     Wikia-l at wikia.com 
>>>>>     http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>>
>>>>>
>>>>>
>>>>>           
>> ------------------------------------------------------------------------
>>     
>>>>> _______________________________________________
>>>>> Wikia-l mailing list
>>>>> Wikia-l at wikia.com
>>>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>>
>>>>>           
>>>> _______________________________________________
>>>> Wikia-l mailing list
>>>> Wikia-l at wikia.com
>>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> Wikia-l mailing list
>>> Wikia-l at wikia.com
>>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>>
>>>       
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>
>>     
> Since the code already exists in the monobook skin it would be easy to
> replicate. Please may I also direct the development team at an idea to
> create a function which does what the sidebar in monobook currently
> does. It could be put in Skin.php - there are many uses for it and
> currently I am aware of several things that would be benefit from such
> a function. The main advantage would be that it can more easily be
> fixed if flaws are found and it would save disk space in the long run.
> Thanks,
> MinuteElectron.
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070805/a9468919/attachment.html 

From toughpigs at gmail.com  Sun Aug  5 23:41:55 2007
From: toughpigs at gmail.com (Danny Horn)
Date: Sun, 5 Aug 2007 19:41:55 -0400
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B64B3F.8010502@wikia.com>
References: <46B508EB.2020500@wikia.com>
	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>
	<46B57CC3.2080900@wikia.com> <46B58BC1.5020500@telus.net>
	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>
	<9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
	<46B64B3F.8010502@wikia.com>
Message-ID: 

One problem that I'm having with the new skin is that the "navigation"
widget is at the bottom of the sidebar. Navigation needs to be right at the
top, so it's in easy reach all the time.

I don't really get the point of the NavLinks yet. "Home" duplicates the
function of the logo. I don't use a forum on any of my wikis. "Random page"
is cool, but "Create new article" isn't really top-level for me.

The links that I want people to see right away are Home, Recent changes,
Random page, Current events, Active talk pages, and Help -- the ones in the
"navigation" widget.


-- D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/wikia-l/attachments/20070805/37020ff5/attachment.html 

From dan_the_man at telus.net  Sun Aug  5 23:45:45 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sun, 05 Aug 2007 16:45:45 -0700
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: <46B64B3F.8010502@wikia.com>
References: <46B508EB.2020500@wikia.com>	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>	<46B57CC3.2080900@wikia.com>	<46B58BC1.5020500@telus.net>	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>	<9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>
	<46B64B3F.8010502@wikia.com>
Message-ID: <46B66129.5060505@telus.net>

How about a fallback.
[[MediaWiki:Sidebar]] and [[MediaWiki:Quartz sidebar]]. If 
[[MediaWiki:Quartz sidebar]] is empty, then fallback to 
[[MediaWiki:Sidebar]]. Or [[MediaWiki:Quartz sidebar]] could use a wfMes 
to use the contents of [[MediaWiki:Sidebar]] as the default for itself.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com

John Q wrote:
> Yes, that's the general plan. :)  But it brings up a question that we 
> decided to wait before implementing so we could ask everyone...
>
> Currently, we have the MediaWiki:NavLinks article which populates 4 
> links into the header area. We're also taking monobook's sidebar and 
> populating the contents of that into the right nav area. My guess would 
> be that the 4 links you'd want in the header are already in the monobook 
> sidebar and the result would be 4 duplicate links. One solution to this 
> is to create another MediaWiki article that would be the equivalent of 
> monobook sidebar but only for the v2 skin... then you could avoid 
> duplicate links. Downside is two lists to maintain.
>
> Thoughts?
>
> Thanks,
> John Q.
>
>
>
>
>
>
> Uber Halogen wrote:
>   
>> On 05/08/2007, Jamie Hari  wrote:    
>>     
>> Since the code already exists in the monobook skin it would be easy to
>> replicate. Please may I also direct the development team at an idea to
>> create a function which does what the sidebar in monobook currently
>> does. It could be put in Skin.php - there are many uses for it and
>> currently I am aware of several things that would be benefit from such
>> a function. The main advantage would be that it can more easily be
>> fixed if flaws are found and it would save disk space in the long run.
>> Thanks,
>> MinuteElectron.
>> _______________________________________________
>> Wikia-l mailing list
>> Wikia-l at wikia.com
>> http://lists.wikia.com/mailman/listinfo/wikia-l
>>
>>   
>>     
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>
>   


From dan_the_man at telus.net  Sun Aug  5 23:51:28 2007
From: dan_the_man at telus.net (DanTMan)
Date: Sun, 05 Aug 2007 16:51:28 -0700
Subject: [Wikia-l] 4 custom nav links at the top...
In-Reply-To: 
References: <46B508EB.2020500@wikia.com>	<757d22db0708041733m4669a72eoefa9cd674f143076@mail.gmail.com>	<46B57CC3.2080900@wikia.com>
	<46B58BC1.5020500@telus.net>	<757d22db0708050139s105e1b5oa82da07e37fad228@mail.gmail.com>	<9e9606a90708051439q3a3dcbbcv432adc68913055cc@mail.gmail.com>	<46B64B3F.8010502@wikia.com>
	
Message-ID: <46B66280.6050903@telus.net>

The boxes on the right are customizable of order. Just go to Manage 
Widgets and you have the ability to reorder the sidebar.
But I would note that unlike in Monobook the toolbar is up top instead 
of down below.
But as for those nav links... Having a Home link there isn't bad. In 
fact, most wiki stick a link to the Main Page in their sidebar, so very 
few starting people know that the logo just links back to the main 
page,  removing a Main Page link could be confusing. As for Create a new 
article, that is something that also confuses many new people, they 
don't even know that such a page exists, many active users don't even 
know that Wikia has that. Remember that the links are for everyone.
As for Recent changes, and most of the other links they're already 
inside of the new toolbox. The ones that people put in the sidebar are 
actually now redundant.

~Daniel Friesen(Dantman) of The Gaiapedia, Wikia Graphical Entertainment Project, and Wiki-Tools.com

Danny Horn wrote:
> One problem that I'm having with the new skin is that the "navigation" 
> widget is at the bottom of the sidebar. Navigation needs to be right 
> at the top, so it's in easy reach all the time.
>
> I don't really get the point of the NavLinks yet. "Home" duplicates 
> the function of the logo. I don't use a forum on any of my wikis. 
> "Random page" is cool, but "Create new article" isn't really top-level 
> for me.
>
> The links that I want people to see right away are Home, Recent 
> changes, Random page, Current events, Active talk pages, and Help -- 
> the ones in the "navigation" widget.
>
>
> -- D.
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wikia-l mailing list
> Wikia-l at wikia.com
> http://lists.wikia.com/mailman/listinfo/wikia-l
>   


From martineznovo at gmail.com  Mon Aug  6 18:01:46 2007
From: martineznovo at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Mart=EDnez?=)
Date: Mon, 6 Aug 2007 20:01:46 +0200
Subject: [Wikia-l] v2 skins available in skin preferences now...
In-Reply-To: <46B64273.30707@wikia.com>
References: <46B4E73C.40701@wikia.com>
	
	<46B64273.30707@wikia.com>
Message-ID: 

Well, it isn't exactly as how I wrote it. The "view selected source"
in Firefox modified it a little.

The real code is as follows:

(...)