I kind of agree with you in regards to Monobook. Never been a total fan, yet will kind of miss it. It had its uses and was kind of neat, but honestly though, it was missing stuff that Wikia offered (that I liked).
But anyways, I am not gonna dump a list of complaints on your wall, other than it was someone reactionary to keep yet the wiki-like viewpoint is nostalgic-stirring.
I guess some people dont like change as much as I envision.
People don't seem to get that if Wikia supported Monobook, meaning put in ads and access to a bunch of other stuff Oasis skin has, it would lose much of the attraction it has right now. Wikia is probably mostly using GDPR as an excuse, but they could have handled it much better.
Hey Fandyllic. I have recently been trying to pickup JS. I have tried a few small things here. I would appreciate your opinion when you have the chance. Is there a more efficient way? Are there any conventions I am not following? Those are the types of questions I have.
I'm by no means a JS expert, but the code looks straightforward, so if it works you're probably fine.
After looking at your code, my only advice is to read up on JQuery which is JS library built-in to most major websites including Fandom wikis. If you look at my code, I use it heavily. It has tons of shortcuts for quicker manipulation of CSS and HTML DOM elements.
Okay. Thanks for the feedback. Is there anyone else you would recommend me asking for feedback? I am already aware of JQuery. As you said, it is very common. So much so that it is hard to find anything that works with just "plain" JS. However, I had gotten the impression is was mostly useful for selecting multiple elements at a time; something which doesn't really apply in my case. Although, I did use it so the function isn't called until the pages is fully loaded; at least, I think that is what I did.
I don't mind replying to necroposts if someone else tries to revive them. I've never understood the problem with necroposting if the comment is relevant. So, go ahead and lay blame... I just don't think its a problem.
I'd like to restore and re-do the page for API ShowUIPanel that you deleted on January 27th, 2014. While there's not much to say about this function that hasn't been said in Creating standard left-sliding frames, it would be quite helpful to have an entry for the function itself (and API HideUIPanel). Took me a long time to figure out the difference between Show() and ShowUIPanel(), and having an explanatory page for the function would have made things much quicker. Perhaps the deleted page was useless, but I think I can make it helpful.
I had some things I wanted to do with my user page that didn't work; so I wanted to see if it was due to the resource loader. I transcluded your page to test (I hope you don't mind) since I know Tabber requires resource loader. That is when I noticed you found a work-around for the resource loader issue. Why haven't you shared this man?
I think (and as you may have suspected) that is because using raw effectively renders it locally; so it is looking for those subpages on the local wiki. Perhaps you could get around that by using interwiki transclusion inside the Tabber?
I saw in a comment, you made, that said Visual editor is slow. I agree. It is slow and cumbersome and generally for newbie editors or very casual ones. Wikia won't update it anytime soon.
Meanwhile, the visual editor on wikipedia is much better and has practical uses to it. I can use it to cite sources, highlight, and can CTRL+B/I with it. UI is slick enough for general use. It doesnt replace the goodness of source editing.