User talk:Cqm

Heads up
I patched that bug that was breaking  and pushed it out as v0.2.1. It's additionally now possible to completely blank pages, because it wasn't before, by giving an empty string as the wikitext eg. .  and   are also now back in, because I accidentally left them out of v0.2.0 because I'm a silly person. Anyway, 0.2.1 is already being loaded on the wiki, so it's all perfectly usable. If you need assistance with implementing something with it, you know where to find me (my talk page). Also, while I'm still doing documentation, look at the  object in your console to see if certain functionality exists rather than just going off that obscenely incomplete list on the wiki. 11:45, June 2, 2013 (UTC)
 * Also, if you want to work with the unminified version, you can just copy-paste this into your console and run it, because Tundra doesn't have a catch to see if it's already loaded. 11:49, June 2, 2013 (UTC)
 * I am actually terrible. Thank you for finding that, sir. I already pushed that patch out and it's already being loaded on the wiki. Two things though. Firstly, you see that object that gets logged out to the console with error messages? You can use a  callback to respond to errors with the data in that object, like this:


 * The  is exactly the same as the object that gets logged out. Since moving a page throws an error if the page you're moving doesn't exist, you don't have to pre-check if the page exists, you can just do something like this (incorporating your code here):


 * Second thing, in case the readme didn't make it clear, Tundra is supposed to be used like this:


 * Tundra does begin to load as soon as the import statement runs, but it's asynchronous, and in the short span of time of the page loading, it might not be finished loading yet by the time your script runs. Using  makes sure it is. Keep in mind that it's also asynchronous, and the function you give it won't necessarily be run at the same time as the code around it (it might be if it's already loaded, but please don't rely on it). Perhaps you can do something like, putting the code that creates on the form on the page inside   so it's ready and functional as soon as it appears and to reduce timing conflicts inside your own code.  12:43, June 3, 2013 (UTC)

God letters talk
Sorry, forgot to thank you for notifying me ;) Greatly appreciated :3 18:51, June 8, 2013 (UTC)

Re: Chatlogs
I would just like to have all references to that name in search results etc removed for personal reasons. Hope you understand. :) Rankata28 (talk) 09:39, June 9, 2013 (UTC)

Hur
o.o 23:21, June 9, 2013 (UTC)
 * Yeys ^-^ 23:43, June 9, 2013 (UTC)
 * Yey it does ^-^ Good job & thanks. <3 01:56, June 10, 2013 (UTC)

hi
 CÅM  FIX YOUR JUNK you keep join/quitting in the chat. Please fix. Thanks. 06:26, June 10, 2013 (UTC)

I saw it
And now that I have some juicy [ blackmail], I am going to make you my bitch. 15:21, June 12, 2013 (UTC)

Desysop
Thanks for the explanation ;) Greatly appreciated 07:54, June 18, 2013 (UTC)

RE: Collapsible navboxes
Since the template is used alot, we can test out your changes in Template:Navbox2 first. 00:32, June 21, 2013 (UTC)
 * Can you change [Expand]/[Collapse] to [show]/[hide] (with s and h in small caps) per the earlier style? And please shift the v.d.e. links to the left by 5px, and the [show]/[hide] links to the right by 10px. 13:54, June 21, 2013 (UTC)
 * K, thx! 14:20, June 21, 2013 (UTC)

Re: pengLocations
I'll have a look at the updates. As for why I did some things a certain way, I kept as much of the previous code as possible and just added new functionality, rather than do a total re-write, even though the change was still extensive. -- 22:53, June 21, 2013 (UTC)

re:Conditionals for js
The Dropadd.js should load under the condition: (wgPageName.match('/Charm_log') && $('#charmguide').length) || (!wgPageName.match('/Charm_log') && $('.charmtable').length) The monstercalc.js needs this condition: $('span#XPEach').length || $('span#GEPrice').length || $('span#killXP').length That should work 13:54, June 22, 2013 (UTC)

Re: Your Bot and br-tags
I don't quite understand your response on this subject.

I'll note in advance (as Rich Farmbrough pointed out) that exchanging the standard-compliant format " " for the equally standard-compliant format "  " in either direction is a trivial computational load, so if wikia prefers the former format, there is no real harm in converting all the wiki source to the latter format, and then having wikia convert it back before serving up pages.

"In Chrome version 27, void tags, such as br, img and input, are not escaped. This is also true in version 21 of Firefox."

Odd. I also tried Chrome version 27 (on windows), Chrome 28 (on linux) and Firefox 21 (on both), as well as other browsers, and invariably saw wikia serving up pages with the self-closing format of the tag: " ".

"Apparently it is up to the browser how the page is rendered."

What does this mean? On the one hand, it is tautological&mdash;a browser is a piece of software which renders html pages. On the other, if the suggestion is that browsers tweak their "View Source" output rather than displaying the actual source received over the wire, I didn't see that. I observed wikia's http responses both before and after processing by the browser, and didn't see any case where the "View Source" pane differed from the packet capture.

A third interpretation would be that how wikia parses the wiki source to produce html depends on some browser-specific feature, such as the User-Agent header. Again, I saw no evidence of this with respect to the &lt;br&gt; tag. Note that to minimize the chance that I was "corrupting" a page with an older browser, so that my newer browser received a cached version rather than a freshly parsed version, I chose pages from the top of Special:Contributions/Cblair91Bot.

"the bot altering the tags is technically correct"

or rather, it is technically not incorrect. It is implementing an aesthetic choice between two valid options, not a technical fix. Qloque (talk) 12:07, June 23, 2013 (UTC)


 * Thanks, we're seeing the same thing, but using language differently.


 * wikisource &rarr;wikia&rarr; html source &rarr;internet&rarr;browser&rarr; DOMtree &rarr;rendering&rarr; browser window

" regardless of the formatting in the wiki source; while inspecting the parse tree generated by the browser shows a variety of results, depending on the browser and the inspector's preferred way of displaying a particular parse node. Qloque (talk) 22:42, June 23, 2013 (UTC)
 * So the html page source generated by wikia and delivered to the browser always contains break tags as "

Moving Exchange: pages
I see that you moved a few of the pages on Special:WantedPages atm to the right place. I was wondering whether moving Exchange-namespace pages requires special tools (because of the bots using them) or not - wouldn't want to ruin anything... 09:06, June 27, 2013 (UTC)

Re: Moving pages
Ow! I guess I shouldn't try fixing things if I can't do it properly. Won't ever happen again. Sorry! 10:25, June 27, 2013 (UTC)
 * Oh well. It's a much more complex process than I thought it is and I don't think I can move pages without breaking something, so next time I'll ask someone else to do it rather than attempting it myself. 10:41, June 27, 2013 (UTC)

Moving Pages
Hello, I saw you posted a message on Regis Dramen's talk page about moving pages. You probably noticed that I also attempted moving one of the teleport scrolls pages, it was me that saw they had changed in game and I asked Regis to show me how to move pages to change the names on wiki. I'm sorry we did not do it right and caused you more work. I still have some questions about your message, if you could answer them for me hopefully I can move pages correctly in future.


 * 1) If I check Special:WhatLinksHere how will I tell when there is a double redirect?
 * 2) If there is a double redirect how should I fix it?
 * 3) Does a wanted page also occur when a link on a moved page is broken or does it only occur for a broken exchange price? If its only for exchange prices that break what happens to other types of broken links in articles?
 * 4) How do you fix wanted pages?

Maybe if there is a guide on moving pages you can just point it out to me instead. Thanks 10:37, June 27, 2013 (UTC)


 * I think understand now, thanks alot :) 14:50, June 27, 2013 (UTC)

Hai
User talk:Fswe1. Have fun. 08:44, June 28, 2013 (UTC)
 * Talk:God Letters should be closed as consensus for option 2 per John Ayliff's statement, and, well, the consensus. Do we need a(nother) sysnub for that or can we just go ahead and get it over with? 17:27, June 30, 2013 (UTC)

RE: collapsible wikitable in userspace
do you know why the collapsible wikitables in userspace shows "Expand/Collapse" instead of "show/hide" (such as in User:AzBot)? 06:09, July 3, 2013 (UTC)

Collapsible
I think I like whatever scripts we had before for collapsible tables. As I remember it, the expanding and collapsing was rather smooth. With the mw- default ones, I can see each element being created/destroyed. It ain't pretty. 23:48, July 3, 2013 (UTC)
 * Okay, so I'll have to live with the ugly? FYI, I didn't literally mean it when I said destroyed, lol. 23:56, July 3, 2013 (UTC)

Re:Basilisk safe spot
Yeah, I had them as a slayer task yesterday and, due to the Fremennik Slayer Dungeon's graphical update, they were no longer present. 04:56, July 7, 2013 (UTC)

Suggestion
"CiteATL" - pro or contra? :) 06:44, July 7, 2013 (UTC)
 * To elaborate on that, the most important difference from CiteGeneral would be the "episode" parameter, which would automatically add both the URL and the title of the respective episode. Provided the template is updated every x weeks, of course. Alternatively, we could just keep the url and title parameters, have a postdate parameter, perhaps a minute parameter ("Relevant information around the ___st/nd/rd/th minute."), one for the mod(s) who said it and, of course, accessdate, name and notes. How's that? 06:47, July 7, 2013 (UTC)
 * Okay - would you prefer the episode parameter or url+title? I was thinking to just copypaste the code for other citing templates and adjust where necessary, without using the podomatic thing at all. 09:53, July 7, 2013 (UTC)
 * I tried something at User:Fswe1/Laboratory, but failed miserably. Basically, it needs the optional minute parameter and 's for th episode parameter, assigning urls and titles to the episode numbers we have got so far (0 included). If you find some free time, please do mess with it. =3  19:31, July 7, 2013 (UTC)
 * Superb. I did some stuff with it and added a test reference. It seems to work as far as a reader is concerned, but it keeps bugging me about unclosed brackets and I can't seem to find them. :P Should we add the name and notes parameters? Alternatively, we could make the name something like "atl#" using vardefine, since that seems to work well. :P Then again, on Sliske, the same ATL apisode is referenced twice, but using different minutes. I can imagine that would produce troublez. 06:35, July 8, 2013 (UTC)
 * What would we do without you? :P I'll try to add the name parameter by copypasting. If I fail miserably, we'll blame Cook. Other than that, I think it's pretty much finished. =3 Luckily, there aren't that many instances where CiteGeneral is used for ATL, so it shouldn't take too much time to replace it. If I feel particularly bored, I might even go about filling in the quote parameter. ;P 08:43, July 8, 2013 (UTC)

re: common.js and stuff
Do you have a mockup of what it would like (or can you make one)? 23:37, July 7, 2013 (UTC)

Closure
It needs some clarification, badly.


 * The option to allow use of the script on secondary bot accounts was suggested but has not gathered consensus

Ummmmm what? That's what we do now... Use a secondary bot account for automated edits. And of course it would be "allowed". Trust is on the person, not the account. If we trust someone to be temporarily flagged, we trust them to use another account. What I brought up was forcing large scale usage to be done on a separate account.


 * With this in mind, there will be no change to the existing system of requesting bot flags

Was that referring to the aforementioned script? Or does it mean only crats will be able to assign the flag now? It can be read both ways. Are you saying we don't need to allow admins to flag bots because the thread that spawned this one was not closed as successful? Or are you saying we don't need to change the methods to include forcing a secondary account?

Frankly, not forcing a secondary account is silly. Interpretations of consensus aside, that proposal had no opposition (reasonable or otherwise), was perfectly logical, and it's almost exactly status quo; it only adds another script for use under a bot flag.

What? 01:17, July 8, 2013 (UTC)

Money making guides, part 3
So, I'm having a bit of trouble with the archives and the "Money making guides, part 3" forum. I can't seem to get it to archive. The DPL I use should be working correctly. Can you look into this? Thanks  04:33, July 8, 2013 (UTC)
 * Never mind. Today's update to WantedPages just showed that the naming parameter was messed up on the actual forum page. It's good now! 07:41, July 8, 2013 (UTC)

Collapsible issues
I'm having issues with Template:Userboxes. 11:19, July 10, 2013 (UTC)

Bah
Y u change name. You'll always be Cåm for me. <3 11:45, July 10, 2013 (UTC)
 * Cqm is a stupid name. How am I meant to pronounce that? 12:35, July 10, 2013 (UTC)
 * Ask Paul M or Osborne, they'll figure it out. Unfortunately, I'm hearing "cockum" in my head. 13:48, July 10, 2013 (UTC)

BlackList
It's to prevent shitty, alloneword file names like that from being created. Btw, You're a noob. 16:33, July 10, 2013 (UTC)

Update site notice now
Forum:Feedback for Jagex

I don't think there's been a more perfect time. 17:51, July 11, 2013 (UTC)

Preview mode
The Mol Man and i were talking yesterday about Preview mode when editing a page and how it is glitched. I don't completely understand it, he was saying something about JavaScript and yeh....he kinda lost me. Prior to that, as in the last few days, Preview HAD been working for me. And by all this i am talking specifically about the infobox glitch. It was the first time it had worked correctly and then it just decided to stop. Anyway, Mol said you might be able to help? or know something that would help?
 * Thank you =] for putting a word in to matt and taking the time to explain it to me.

Mike111b (talk) 03:04, July 12, 2013 (UTC) Mike111b (talk) 18:00, July 11, 2013 (UTC)

RE: itemId in Template:ExchangeItem
Yeah, my bad. I wasn't planning on removing that parameter FROM the exchange pages, but just its use as a switch parameter in ExchangeItem. Hadn't realised it was still being used... thanks for the fix! 21:41, July 12, 2013 (UTC)

I CAN FINALLY TYPE YOUR USERNAME PROPERLY
http://i.imgur.com/qrQya4p.png

08:43, July 14, 2013 (UTC)

Cites
I was just thinking... Maybe we could do something for CitePostbag and -GodLetters that automatically adds title and link to the given issue? It'd be a lot of work to replace everything though... 09:28, July 14, 2013 (UTC)
 * I'm not Cook though. :P 09:37, July 14, 2013 (UTC)
 * I have no idea where else to post this. Feel free to use.  19:42, July 15, 2013 (UTC)

Re: pengLocations (redux)
I've gone over the pengLocations code you had a github. I've fixed bugs (=== required some type conversions, the cookie init code got lost somehow, etc.) and tweaked a little, including the whitespace for the comments. You can copy and paste from User:Saftzie/Beta.js into MediaWiki:Common.js/pengLocations.js. One of the tweaks is to use classes for the row highlighting instead of the cssText attribute. The two new entries in MediaWiki:Common.css (or imported thereto) are: /* light tables */ /* mouse over */ tr.highlight-over { background-color: #ccc !important; } /* light on (light off = no class) */ tr.highlight-on { background-color: #cfc !important; } If you don't like the class names and decide to change them, there are two variable declarations in the js that also need to be changed.

I've also put some work into an update to MediaWiki:Common.js/highlightTable.js along the same lines. The updated code should also make it less annoying for people who hop between pages with light tables. It needs a bit of testing, though, so it could be a little while yet. -- 04:08, July 15, 2013 (UTC)


 * There can be multiple light tables on multiple pages. I think the biggest complaint people have about the current code is that the highlighting on one table gets applied to all tables, even across pages. The way I have the js written now, it mostly just lifts the pengLocations code (which is how Quarenon pretty much did it, I think), but with a different monolithic cookie that supports multiple tables on multiple pages. There's a decision to be made if a different cookie for each individual table is desirable. I also thought about using bits for on/off (instead of a whole character), although I haven't implemented that as of now. The cookie part is modular enough that changes shouldn't be too big a deal. At the moment, I just need to test the basic code, though. -- 20:39, July 15, 2013 (UTC)


 * I think I'm essentially done with the code to update MediaWiki:Common.js/highlightTable.js. I've put my current version in User:Saftzie/Beta.js.
 * Rather than a separate browser cookie for each table (or even each page), there are up to 16 browser cookies (maximum).
 * Each cookie covers several pages, based on the hashed page name, and all the tables on those pages. They're named, where hexdigit is the first hex digit of the hash of the page name. I think having a separate cookie for every table or every page could potentially be too many cookies, but having only one would keep anything from expiring if the user kept using any light table anywhere. 16 seems like a reasonable compromise to me.
 * I use a 32-bit Castagnoli crc for the hash. A crc uses minimal coding to calculate. The Castagnoli crc has optimal collision avoidance and uniform distribution in a 32-bit crc.
 * The CSS classes are the same ones that pengLocations uses. That was always my intent. No change is required to MediaWiki:Common.css, although you might want to change the "pengLocations only" comment to include light tables.
 * The browser cookie content is a string composed of the page name hashes and Base64url-encoded binary data for the rows' selection status, so each table still has its own data.
 * There's a lot of new code compared to the old code, but most of it is cookie handling. None of it runs unless there's at least one light table in the article. Cookie data is only stored if the user manipulates the light table in some way. Just loading/viewing the article doesn't create a cookie. For the 39 articles in Mainspace that have light tables, if every page gets cookie data, there would be 685 bytes of data. Of course, I wouldn't expect a user to visit every page with a light table and store a cookie, but the number of pages with light tables could grow, too. So, do we just want to slam it in or try to get some good will first? -- 06:16, July 18, 2013 (UTC)

Please help me understand
When you read [ this] (sourced and said by Jagex themselves) and it responded with this [ this], does this attitude not only invite a RS:3RR - it explicitly says to talk about it - but is also iffy when considering: RuneScape:Status and opinion-weight, RuneScape:User treatment policy/RuneScape:Don't be a dick? I don't want edit wars, but an admin basically refuses. 13:24, July 17, 2013 (UTC)


 * Thank you for answering in such length ;) Don't worry, I wasn't accusing you of it. I'm sorry if I wasn't clear enough.
 * I agree with you that the case may not be clear cut... but that's exactly why people should talk about it and try to reach a consensus. And that is exactly why I was ... 'so shocked' to see Fswe1 did not want to talk about it. You also asked me who the admin was, well to my best knowledge Fswe1 is an admin... or something like that.
 * As you can see in the table below, the article was reverted/edited several times. I was only aware of it being removed once (I didn't check the history page until just now. As I said, the 3RR says people should talk if they disagreed. Fswe1 said is won't and that I just have to listen to him - this breaks 3RR and also the RS:weight of opinion thingy (what I said above). Below is a table with info on who reverted the item Fswe1 does not want to talk about, as you can see: everybody listed only reverted once, except for Fswe1 and Lord Nexius - they reverted twice. I hope this makes you understand my discontent with Fswe1's reaction. So to me this: "it could be said that you and Fswe were both in violation of 3RR" is not exactly the complete picture: he reverted double the times as I did and he also denied to talk about it.
 * {|class=wikitable

!Name !!# revering 'evil'
 * +source
 * Me || 1
 * you ||0 ||so don't worry ;)
 * Chaos dark1|| 1
 * Fswe1|| 2
 * Ciphrius Kane|| 1
 * Lord Nexius || 2
 * }
 * As for the content (the interpretation of alignment/philosophy or mere association) I would like to talk about it, especially since you brought up Zamorak and Saradomin (for more info, see this)... anyway, I think that should happen more on a public forum place, and not user talk pages - since more people seem to disagree xD 10:56, July 18, 2013 (UTC)
 * Ciphrius Kane|| 1
 * Lord Nexius || 2
 * }
 * As for the content (the interpretation of alignment/philosophy or mere association) I would like to talk about it, especially since you brought up Zamorak and Saradomin (for more info, see this)... anyway, I think that should happen more on a public forum place, and not user talk pages - since more people seem to disagree xD 10:56, July 18, 2013 (UTC)
 * }
 * As for the content (the interpretation of alignment/philosophy or mere association) I would like to talk about it, especially since you brought up Zamorak and Saradomin (for more info, see this)... anyway, I think that should happen more on a public forum place, and not user talk pages - since more people seem to disagree xD 10:56, July 18, 2013 (UTC)

Just to clarify
You're still a ****. 10:38, July 18, 2013 (UTC)


 * Did you know there's a symbol for this? Píča. TYL 21:51, July 19, 2013 (UTC)

remove delay and transition effects in collapsibles
Can you look into whether we can remove the delay (when "hide" is clicked) and the transition effects (when "show" is clicked). I have to agree with User:The_Mol_Man above that I liked our old collapsibles more than this current one. Thx! 13:15, July 8, 2013 (UTC)
 * The show/hide text sometimes interchange... it shows "hide" when it should show "show", and vice versa... 03:33, July 23, 2013 (UTC)
 * When collapsibles are nested, i.e. Grand_Exchange_Market_Watch/Adjustments the table rows in the inner table disappear. 04:14, July 23, 2013 (UTC)

RS:EXCHANGE
GED works again, but could you check RS:EXCHANGE and see if I missed doing anything...
 * 1) Was the MediaWiki:Common.css edit button removed?
 * 2) Some of the steps in that page needs to be slightly more detailed for noobs like me.
 * 3) Some steps need to be modified/removed such as:
 * 4) * the ones with "MediaWiki:Group-autoconfirmed.js". Should there be a script there? Couldn't find any...
 * 5) And please add steps on how to reverse the process as well, or just a checklist.

Thanks. 01:33, July 24, 2013 (UTC)

Old file pages
ITS BROKEN WHEN THERE'S MORE THEN ONE WORD BECAUSE U USE SPACES IN THE URL AND U SHOULD CHANGE THAT TO USE UNDERSCORES!!!!!!!!!!!!!!!!! 20:46, JULY 24, 2013 (UTC)

MediaWiki:Common.css
Currently says ... /** * Light tables * Classes currently only applied by peng locations script */ ... but they're used by highlightTable.js now, too. It's not a big deal, since it's just a comment. Thanks for pushing the script, too. -- 23:08, July 24, 2013 (UTC)

Pado dialogue
What token do you have? 14:12, July 26, 2013 (UTC)

collapsible
So I did a search for all the mainspace pages that still use collapsible instead of mw-collapsible (using the regex ) and here's what I cqme up with. Maybe you wanna run your bot to fix it? I know I sure as hell don't feel like doing that. 12:52, July 27, 2013 (UTC)