Forum:Try the new editor

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Try the new editor
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 2 July 2011 by Ryan PM.

Wikia has released a new Editor. Do we as a community want to try it? Wikia has released a blog about it [[community:User_blog:Sarah_Manley/Try_the_New_Wikia_Editor|here]] for anyone who didn't click the link in the bubble. :P svco4bY.png3Gf5N2F.png 21:14, June 21, 2011 (UTC)


Neutral - As Non-RTE editor. svco4bY.png3Gf5N2F.png 21:14, June 21, 2011 (UTC)

Neutral - Doesn't look that great, but appearences can be deceptive and don't see any other good reason to oppose What I've done Ciphrius Kane Talk 21:21, June 21, 2011 (UTC)

Support-ish - The editor doesn't just affect those using the RTE btw -- it changes BOTH RTE and Visual editor. I like the editconflict page and stuff too. Previews are a lot nicer. The sidebar (and not having to scroll down for the saving buttons and stuff) is really nice. Overall, I'd say it's better than what's currently in use, although, I don't edit much. :P Grim reaper hood.png Ben RyfosTalk 21:31, June 21, 2011 (UTC)

Support. It will be enabled eventually, so we may as well get used to it now. Plus, it is actually a huge improvement :3 ajr 21:37, June 21, 2011 (UTC)

Yea, also worth mentioning that this effects the RTE and classic editors. ajr 21:38, June 21, 2011 (UTC)
How will this affect the classic, good editor? Will that be disable-able easily in, for example, Special:Preferences if users do not like it? JOEYTJE50TALKpull my finger 06:37, June 22, 2011 (UTC)
Visual Editor will respect your current preference on not using RTE. The only thing that is leaving is CreatePlates that were phased out with LayoutBuilder (We will still keep MediaWiki:Newarticletext) which we do not use. As for Newarticletext, the page might need to be changed with the length shown (gives you a "More" option when it goes down "x" pixels). Ryan PM 06:43, June 22, 2011 (UTC)

Support - Per Ajr. If it will inevitably come in time, might as well get used to it now. ɳex undique 22:07, June 21, 2011 (UTC)

Yes please - Per teh guys above me. It works really well and is a massive improvement. Matt (t) 22:12, June 21, 2011 (UTC)

Weak support - As it allows people to easily preview changes, summary box is at the side (which is more convenient) etc. There are still some problems, but nothing too major in my opinion. Smithing (talk | contribs) 23:31, June 21, 2011 (UTC)

Neutral - The update does not affect Monobook users. --Andorin (Talk) (Contribs) 23:34, June 21, 2011 (UTC)

Meh - We'll have to eventually won't we? I dislike how preview opens a lightbox, javascript doesn't load half the time for me on wikia. Oh well. sssSp7p.pngIjLCqFF.png 23:37, June 21, 2011 (UTC)

Support - Might as well see how much less bad than the proper editor it is. 222 talk 06:30, June 22, 2011 (UTC)

Support - Was going to just activate it as soon as they released it to WikiaLabs, but I guess I was too slow. Anyway as discussed over at Community and Community Test, this is an improvement over RTE in that it's not entirely JavasScript, doesn't exhibit the same bugs and was built from the ground up with a loose framework of RTE. That being said, we shouldn't wait to long as it will be enabled on all wikis within the next four to six weeks assuming no major bugs persist. In time, there should be more added to it, either by us or Wikia as it currently lacks a history link when there is space in the right tab for "Last edited by <name> (See revision <number>), and similar differences in the near future. Ryan PM 06:38, June 22, 2011 (UTC)

After messing with it on my test wiki, until MonoBook layout only is added to our preferences, we'll still be forced to use the awful EditPageReskin/EditPageLayout changes if you still use the Wikia/Oasis skin (This means that it still respects the no RTE, but it will use the newer surrounding interface/rail). I oppose using this until those preferences are made live as well as my ability to add to the Licensing tab. Ryan PM 02:59, June 23, 2011 (UTC)
Making changes to it before we use it. Since nothing can be done to change the look back to what it was before the reskin, let's just bit the pill and take the plunge. I re-support using it. Ryan PM 01:45, July 2, 2011 (UTC)

Will it be enabled for Monobook? - I'm guessing it won't, but hey ho. Real Crazy 15:50, June 22, 2011 (UTC)

No. bad_fetustalk 16:09, June 22, 2011 (UTC)

Strong oppose - Just tried it on the community test wiki, and it was horrible. The current editor is certainly more functional; (while not so important,) the newer one is ugly; it uses a javascript to show previews, wikitext , while we've been trying to avoid the use of javascript all this time, since not everyone can view javascript, and since javascript may not load on wikia as fergie mentioned. Also, I don't see why we are rushing to start using it. It's brand new, and is likely to cause new RTE-style bugs, and it has not been pleasant dealing with those bugs in the past. Also, I don't see any major points raised by supporters above. Thus, I oppose. bad_fetustalk 16:09, June 22, 2011 (UTC)

Let me remind you RTE is more JavaScript heavy. The one bug that currently persists in Visual Editor is the odd case of clicking "Edit" and being taken to a different page with ?action=edit. CKE and various i18n files are all that will remain from RTE once Wikia enables wgEnableEditPageReskinExt and removes RTE completely. When JavaScript does not load, as it did for RTE, it will place the user in Source Mode. Ryan PM 18:57, June 22, 2011 (UTC)
RTE indeed is more JavaScript heavy. On the other hand, the source editor is not. The newer editor uses JavaScript even on the source editor, thus, you need JavaScript to edit. As I've explained above, use of JavaScript is not favorable. When JavaScript does not load, as it did for RTE, it will place the user in Source Mode. - Again, the source mode also uses JavaScript. bad_fetustalk 14:57, June 23, 2011 (UTC)

Oppose - Nothing wrong with what we already have. Andrew talk 17:22, June 22, 2011 (UTC)

As much as I agree with you (assuming we are talking about the Source Editor/Default MediaWiki editor), Wikia will have this editor down our necks in the next month or so. Ryan PM 18:57, June 22, 2011 (UTC)

Oppose - Per Chessmaster and Soldier 1033 Prayer-icon.pngTyiloTalkQuest.png 23:00, June 22, 2011 (UTC)

  • Now, with all due respect, did you opposers actually think at all about this before opposing? First off, this will be enabled anyways, so have fun while you oppose progress for two months only to ultimately do no good. Second, have you realized that this will give us the chance to provide real feedback to Wikia for improving the new editor, rather than just sitting here and whining about it until it comes out, then complaining when they won't change it? Honestly people, let's think this through. ajr 03:01, June 23, 2011 (UTC)
I don't think wikia would like to scrap the whole design, just because I think it looks awful. Prayer-icon.pngTyiloTalkQuest.png 11:56, June 23, 2011 (UTC)
Sorry ajr, but that's one of the stupidest reasoning I've ever seen on this wiki. I have absolutely no idea why you have this impression that we should start using it immediately just because it will get enabled in the future. That has no difference from jumping from the tenth floor of a building because you will die anyways. For the second part, if you want to give wikia feedback, go use a test wiki. There is no reason to turn this wiki into a testbed. I don't see how I'm the one that didn't think at all about this. bad_fetustalk 14:57, June 23, 2011 (UTC)
Yea, let's just sit here and whine about the change until it eventually hits us and we can't do anything about it... sounds like a plan. Me complaining about it has far less of an effect than an entire wiki doing that, and since it will come anyways, we might as well start getting used to it now rather than sitting here opposing any change. ajr 02:41, June 26, 2011 (UTC)

Neutral - It has already taken effect on a wiki I edit, and it's not much of an improvement. However, the publish button is towards the top of the screen, so a bit more ease of access. --Dragon defender.png EidolonRydiaTalk HS Argonite 2h sword.png 06:12, June 23, 2011 (UTC)

Weak Support - I haven't tried it, but we may as well give it a go. Users like me who are still used to source can continue to use source, but let's not just impede on improvements because its to something we don't use or like. It will come eventually, so we might as well start now. The only reason that makes this weak is that there may be bugs, and bugs aren't nice. But then again, we can help to iron them out! Also, why is it a problem not everyone can use javascript? Many editors here play RuneScape, so would have java installed. Those who don't have javascript are usually just long-time editors who no longer play RS, but still edit; those editors will probably use the source editor anyway. So an extremely minor percentage of people would be affected. Cheers, Chicken7 >talk 06:59, June 23, 2011 (UTC)

Java and javascript are completely different things... bad_fetustalk 14:49, June 23, 2011 (UTC)
^. Google it. JOEYTJE50TALKpull my finger 17:06, June 23, 2011 (UTC)
Also, javascript is built into every modern web browser. Everyone has it, some just choose to disable it. Obviously, it has some security risks, but as web designer, I find that a poor choice, though I won't try and start a discussion about that here. Hofmic Talk 18:04, June 23, 2011 (UTC)
I don't choose to disable it, it just doesn't load on wikia half the time (like I've already stated..). sssSp7p.pngIjLCqFF.png 18:06, June 23, 2011 (UTC)
Yeah, I know, I have that problem too sometimes, rather annoying, and frankly nothing that can be done about it. You know, the wikipedia editor would be so nice to have here :P Hofmic Talk 18:15, June 23, 2011 (UTC)
lol i fail. Well similar argument would sit. And I agree Wikia's javascript stuff absolutely sucks. They should start using stuff like HTML5 instead of this slow java crap. Chicken7 >talk 07:39, June 27, 2011 (UTC)
the new editor has the same kind of bugs as the current RTE, but these bugs also appear in the article itself (it uses the <a> and <img> tags in the content, while users can't do that manually, which screws up the entire page then, even more than the current RTE). So, the bugs are definetely gone with this editor. JOEYTJE50TALKpull my finger 16:06, June 30, 2011 (UTC)

Neutral-ish - At first, it seemed great, but it's just made the edit window too darn small! The obvious solution seems to be to use widescreen editing, but then you can't see the new stuff that's on the sidebar, particularly category select, the one I'd use the most. I certainly hope that they'll move the stuff to the bottom when in widescreen editing mode... Also, not so sure if the one scrollbar thing is an improvement, since now you can't put extra information at the bottom of the page, such as the conveniently accessible insert template, for symbols and tags. Having such a thing on the sidebar is more limited due to the size of the template, as well, it has the disadvantage of having to open a drop down box there too... Hofmic Talk 18:04, June 23, 2011 (UTC)

Neutral - Sure add it, as long as it does not REPLACE another editor. I'm just using the standard editor (not RTE) and will probably continue doing so. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 06:38, June 25, 2011 (UTC)

You should read the article and/or the above discussion. The source (non-RTE) editor will be changed. Quest.png Gaz Lloyd 7:^]Events!99s 23:18, June 27, 2011 (UTC)
Fswe uses monobook so for him it will indeed not replace the current editor. I assume that's what he means. JOEYTJE50TALKpull my finger 01:22, June 28, 2011 (UTC)

Neutral - Per Fswe1. xScoobsx Talk Contribs 02:47, June 27, 2011 (UTC)

Neutral - Per Fswe1. Pcnerd007 20:44, June 27, 2011 (UTC)

Support - After using the editor there doesn't appear to be a big change. There are things that make it better for new users, but not inconvenient to more experienced users. I don't really have any complaints with using it. Hunter cape (t).png Sentra246Blue hallowe'en mask.png 09:12, June 28, 2011 (UTC)

Closed - The EditPageReskin will be activated. If issues arise, begin a new thread. Ryan PM 02:02, July 2, 2011 (UTC)