User talk:MACH-59330

Welcome
Hi, welcome to ! Thanks for your edit to the EditorSourceMinimal/code.css page.

Please leave a message on my talk page if I can help with anything! Cqm (talk) 14:18, July 26, 2016 (UTC)

EditorSourceMinimal
Hey!

Just stopping by to tell you that I have moved the CSS for EditorSourceMinimal to MediaWiki:EditorSourceMinimal/code.css. Not sure if you knew you could edit the MediaWiki namespace on here, but you can. :P I moved the CSS since it will be easier to maintain and you don't need to include the syntaxhighlight tags. -- Monochromatic Bunny 21:25, July 27, 2016 (UTC)

EditorSourceMinimal (2)
Hey, could I use the images of the buttons and edit these changing the color and the color of the background?

Thanks!

Tobias Alcaraz (talk) 00:00, July 28, 2016 (UTC)

Recent edits to Pseudo-Vector
Hi there! Sorry to say, I've undone both your recent edits to the Pseudo-Vector CSS.

Regarding the visual editor-like button styling: this caused 3rd-party/custom edit buttons to become invisible as they also use the  class. For example, my edit toolbar looked like this after the change, with the last third of buttons invisible. Also, I'm not entirely sure this is in the realm of the Vector skin; perhaps it'd be preferable to make a version of EditorSourceMinimal for the MonoBook skin? (EditorSourceMinimal looks quite nice, by the way! :) )

Regarding adding  to every selector: there is a few that that class should definitely be added to (e.g. ,  ,  ,  , and others) to prevent issues when using this in global.css where it'll affect the Oasis skin too. However, adding it to every single one is unneeded (a fair amount of those selectors only exist in MonoBook) and makes personal CSS changes harder due to the increased specificity. Also, there were a few cases (e.g.  was changed to   - notice the now-unqualified   and  ) where the change made selectors less specific, though I guess that was likely just a copy-paste issue.

- OneTwoThreeFall (talk) 08:10, October 3, 2016 (UTC)


 * I appreciate the revert. The rationale for adding the icon CSS was that less imports would be better than more, and less user stylesheets would be better than more from a maintenance perspective. If you think building an optional bolt-on is a good idea, then I can totally do so!


 * I'm aware that overriding the hardcoded icons would need something more elegant than a brute-force technique along the lines of . Any ideas for doing that with CSS would be strongly appreciated.


 * The initial intention of adding the icons was to achieve parity with the new VE toolbar of WP's Vector skin, simply because the VE icons are a visual improvement of sorts against the old edit ones (barring the actual functionality of visual editors in general).


 * It seems not using  is the best way forward for avoiding overqualification of PV against user CSS. Though PV is meant to be Monobook-specific (my intention with adding the parent selector), users with PV will probably set Monobook in their prefs, so it's not actually needed so much at all.


 * -SPD •📞 •✎  10:24, October 3, 2016 (UTC)


 * Rather than have multiple imports, you can combine CSS imports into a single request. On your global.css page, for example, the four imports can be combined by separating each page name with a pipe character in the  parameter, like below:

@import url('//dev.wikia.com/load.php?lang=en&mode=articles&articles=u:c:User:Speedit/header.css|u:dev:MediaWiki:EditorSourceMinimal/code.css|u:dev:Pseudo-Vector/code.css|u:dev:NewDiffStyle/code.css&only=styles');


 * Agreed, the current editor icons aren't the nicest! Strictly speaking, the VisualEditor isn't a part of the Vector skin, but a separate MediaWiki extension, so whether its icons fit within the Pseudo-Vector "spirit", so to say, could be debatable. Making it into an optional bolt-on seems a good idea! Apart from using  and   like you've done, I couldn't find any way to change the hard-coded   icons using only CSS (I thought   /   may work, but it seems they're not usable on   elements). You could instead set the CSS only on the first 11 buttons (the default set) using , to prevent any custom buttons being hidden.


 * Using  for a few selectors (like I mentioned above) would be good, though, as some selectors here do conflict with Oasis skin styling. Personally, I switch between skins fairly often, but I import it via JS so don't see these issues. Those who import it via CSS and do switch skins would likely appreciate a fix!


 * - OneTwoThreeFall (talk) 13:59, October 3, 2016 (UTC)


 * I am not fully familiar with the Monobook skin's physical build. You may be more "qualified" (lol ;D) to go add the selector as necessary to the stylesheet. I'll look at posting the editor icons to a new stylesheet later this week, and I can give you a simple update to your old-skool icons if you wish.


 * There's always JS for buttons, but I've always preferred keeping visual updates to one import (preferably CSS). In other news, there is a consistent Wikia Design System iconset which could supercede the VE icons, although I've got a small bunch of button suggestions already.


 * -SPD •📞 •✎  23:06, October 4, 2016 (UTC)


 * Haha! I've added  to those selectors that could otherwise apply to both skins. Quickly testing, it seems all is well in the Oasis skin - Pseudo-Vector is no longer making changes there. Re. a separate stylesheet: sounds good!


 * Agreed, it's best to stick with CSS where possible, but for changing those buttons without ugly hacks, JS may be a better solution. Interesting, is that an official Wikia site? Looks quite handy for CSS testing.


 * - OneTwoThreeFall (talk) 08:58, October 7, 2016 (UTC)

Loading Throbber Convertion for EditorSourceMinimal
Can you make it so that the loading throbbers are converted into the spinners from EditorVisualMinimal for EditorSourceMinimal?

Love the Nord Theme
Thanks for creating the Nord code Theme. It's 100x better than solarized light. I made a few tiny color alterations to it on my wiki and now it's perfect. Nord should be the default code theme. RoIento (talk) 22:16, March 26, 2018 (UTC)


 * Thanks, I'm really enjoying it as well! :) It's still in testing, so if you find any issues, I'd really love a report. • speedy • 🔔&#xFE0E; • 🚀︎ • 22:51, March 26, 2018 (UTC)


 * I'd be more than happy to report any issues :) haven't encountered any bugs yet though! I made a few color alterations, but the one thing that you may want to take into consideration is that the color of the  css (code comments) might be too dark. My personal preference anyway is to have the comments brighter than the rest so it stands out (changed the one on my wiki to gold). RoIento (talk) 23:17, March 26, 2018 (UTC)

Profile icons
Hi Speedit. I noticed that you have done some changes to the structure of both MediaWiki:WDSIcons/code.js and MediaWiki:ProfileIcons.js. And although I don't know if it is intentional or not, the wds icons used on the masthead have accordingly become bigger and moved up by your changes. See. And since I couldn't fix it to our need in the wiki through CSS without making the icons disappear behind an invisible wall, could you please look at this problem, or at least tell me of an alternative to have the icons smaller and on the same line as the text beside them?--Luma.dash (talk) 05:43, April 29, 2018 (UTC)
 * Not intentional. While new WDSIcons is gonna be hella useful, it's nowhere near stable. Even the sprite source is out of date.
 * Here's your fix:


 * • speedy • 🔔&#xFE0E; • 🚀&#xFE0E; • 14:28, April 29, 2018 (UTC)

VanguardTools
Hey there, I left a message for you here!. :) --Bryan https://vignette.wikia.nocookie.net/testbravefrontierrpg/images/7/79/VANGUARD.svg/revision/latest?cb=20171111130412&path-prefix=de ( talk | c | dev ) 22:36, May 4, 2018 (UTC)
 * I've moved the talkpage and will take a look soon c: • speedy • 🔔&#xFE0E; • 🚀&#xFE0E; • 10:42, May 5, 2018 (UTC)

CategoryRenameAuto-update
Hi, I saw you know how to create JSON pages for JS script. May I ask you for creation JSON page for this script? ~ [  Q uəntum ii ð the Wise  ] 08:57, May 9, 2018 (UTC)
 * Link? • speedy • 🔔&#xFE0E; • 🚀︎ • 11:07, May 9, 2018 (UTC)

Thanks
Thanks for coming up with this script for PseudoMonoBook. Makes Oasis a little more friendly than the default version but still hard if you have only ever used Monobook or in the case of Uncyclopedia where I admin at, their own skin. Now all going on the 25th May. :(  20:08, May 24, 2018 (UTC)

Porting the speduomonobook to wikipedia
Can it be imported to wikipedia? &mdash; MechQueste  talk  19:19, May 13, 2018 (UTC)
 * It'd be a lot of pain and would involve JS. Not really appetizing for me. • speedy • 🔔&#xFE0E; • 🚀&#xFE0E; • 14:39, May 19, 2018 (UTC)

Enabling PseudoMonobook
Hi! I just tried to enable PseudoMonobook via the import instructions, but it didn't seem to work. So I copied the source, but that didn't work either (link to contribs). Did I do something wrong? Your help would be very much appreciated :) --O u WTB 19:37, May 25, 2018 (UTC)
 * If you want to import PseudoMonobook globally, you should place the import on your global.css on Community Central. -- Cube - shaped   garbage can  19:44, May 25, 2018 (UTC)
 * Mmm.. It still doesn't seem to do anything. Even after trying Ctrl+F5 . --O u WTB 08:55, May 26, 2018 (UTC)
 * Correction, it works just fine now. Thanks a lot, great feature! :) --O u WTB 08:55, May 26, 2018 (UTC)

Pseudomonobook is kind of nice
&mdash; MechQueste  talk  03:24, June 6, 2018 (UTC)

I've got a question about PseudoMonobook. O mnie · Skontaktuj się ze mną! · Co wniosłem do tej Wiki 11:22, June 9, 2018 (UTC)

Re: Adding to Template:Languages
A new format seems to be the best choice. It modifies what the default one returns, so it should adapt to minor changes. Goes over  (to use CSS notation) and changes the link.

This will need some changes, since uselang links on subpages of mainpage won't work there. In short:
 * Wrap Languages on subpages in
 * Add this to root main page, above LangSelect

With this, main page will have uselang links and subpages will link to other subpages. — Nanaki 20:25, July 18, 2018 (UTC)

about Template:Script_Install
Hi!

I think Template:Script_Install was i18ned, but it doesn’t show non-English languages now. So I’d like to know how to add translation, but sorry, I don’t know Lua.

Would you please add translations again?

Thanks, --Plover-Y (talk) 2018-07-21 04:04 (UTC)