On Oct 25, 2014 6:17 PM, "Amir E. Aharoni" &lt;amir.aharoni(a)mail.huji.ac.il&gt; wrote: could Having a side by side really time wikitext - display doesn't sound like an aweful idea at all to me. I'm quite surprised anyone would find that aweful actually. I don't understand why you're so dismissive of that idea. --Martijn https://medium.com/@MrJamesFisher/wikipedia-needs-an-ide-not-a-wysiwyg-edit… https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>

I'm not very confident to say the author is completely right/wrong but the words the IDE would update display the source and the HTML together, and update the HTML inrealtime. Source on the left, HTML on the right. ​made me feel interested. If wikitext editor could display and update the result next to source I would be happier contributor than now, for sure.​ *Vira Motorko* Help save natural resources – please think twice before printing this e-mail or any attachments. 2014-10-25 20:20 GMT+03:00 Amir E. Aharoni &lt;amir.aharoni(a)mail.huji.ac.il&gt;il>:

Perpetuating it with a dedicated IDE wouldn't help it go away. בתאריך 25 באוק 2014 20:51, "Martijn Hoekstra" &lt;martijnhoekstra(a)gmail.com&gt; כתב:

People Who Are Able to Edit Articles But Not to Code dismiss wiki syntax much more than I do. Most of them don't even bother to begin to understand it. The few who do are a rare exception. A wiki syntax IDE will not "go a long way", as the article says, in helping them edit. They will still be forced to do mental mapping from [[]] to links, from ==== to headings, and so on, even if it's shown side-by-side. -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬ 2014-10-25 21:22 GMT+03:00 Martijn Hoekstra &lt;martijnhoekstra(a)gmail.com&gt;om>:

Keep in mind that the projects on Y are brainstorms/seeds -- so it is important to keep that in perspective. By the time they've evolved they often look radically different. That said I think there is kernel of truth there. Our components solve often every problem with one solution. We do need a way to code on top of wikis, but that is not necessarily the same thing as a tool to quickly add/remove text. But we tend to think of them as one. Do we need a better interface for writing components of top of wikis -- I'd think so. Do we need a better way to edit text -- for sure. Are those two the same thing? Lila On Sat, Oct 25, 2014 at 11:03 AM, Amir E. Aharoni < amir.aharoni(a)mail.huji.ac.il&gt; wrote:

Oh, it will remain, just internally. Maybe some day it will be replaced with pure XML, but that day is far away, and by the time it happens editors aren't supposed to care. (That's just me fantasizing; Parsoid people may have a different idea.) -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬ 2014-10-25 21:44 GMT+03:00 Mark &lt;delirium(a)hackish.org&gt;rg>:

On Sat, Oct 25, 2014 at 1:20 PM, Amir E. Aharoni < amir.aharoni(a)mail.huji.ac.il&gt; wrote: {{citation needed}} {{citation needed}}

On Sat, Oct 25, 2014 at 9:56 AM, Andy Mabbett &lt;andy(a)pigsonthewing.org.uk&gt; wrote: [...] ... so, what is it?? /me searches.... ah, Article: http://en.wikipedia.org/wiki/Integrated_development_environment Annotated image: http://i01.i.aliimg.com/photo/v0/267990999/Integrated_Development_Environme… We already have many of these components (requested in the medium post, or in the image), as needed for editing an article: * Syntax highlighter <https://www.mediawiki.org/wiki/User:Remember_the_dot/Syntax_highlighter> (gadget) * Ajax preview (A few options. I've used user:js/ajaxPreview <https://en.wikipedia.org/wiki/User:Js/ajaxPreview> for many years and love it and strongly recommend it) * Split preview (side-by-side) <https://en.wikipedia.org/wiki/Wikipedia:User_scripts#Previewing> (although that doesn't have simultaneous scrolling, which would be fancy/nice. Also the width-drag doesn't seem to work. It probably just needs an update after 6 years..) * integrating the diff viewer with the syntax highlighted source text, sounds incredibly confusing, so let's not do that. Besides, we have ajax Show Changes. * We have a Section-edit link, for jumping to the right section * We have a Template/Page transclusion list, under the edit-source textarea We don't have HTML preview, which might be interesting. Surely it's possible to whip up a userscript for it, if anyone would actually find it massively useful. (Or, we can just leave the browser's own Web Developer bar open to see the HTML. ctrl-f is our friend.) It would be nice to get some of those userscripts turned into (global)Gadgets and/or Extensions, but they're all usable. The only thing they (and all our fancy optional extras) really need, is better visibility. There are a number of ideas to do that, at https://www.mediawiki.org/wiki/Requests_for_comment/Redesign_user_preferenc… and (especially the bottom of) it's talkpage. More ideas appreciated.

On Sat, Oct 25, 2014 at 1:23 PM, Federico Leva (Nemo) &lt;nemowiki(a)gmail.com&gt; wrote: See links for "Live preview" earlier on in my message (a.k.a. Ajax Preview). (Or to repeat: https://en.wikipedia.org/wiki/User:Js/ajaxPreview which I heartily recommend, and there are 3 alternative items linked at the bottom of that page. The one in Special:Preferences isn't nearly as good.) Re: HTML-preview: I suspect I've misunderstood that section of the Medium post (I thought he was coming at it from a debugger angle, but possibly not). Now that I re-read it, I think maybe he's just asking for "synchronous scrolling & selection-highlighting" in the side-by-side preview?