Wikitext-l May 2012

wikitext-l@lists.wikimedia.org

5 participants
4 discussions

Parsoid web service
by Gabriel Wicke 23 May '12

23 May '12

Hello, I have just set up a very basic web service for Parsoid at http://parsoid.wmflabs.org/ It gives you the ability to browse the English Wikipedia as Parsoid currently sees it, and provides forms for wikitext -> HTML DOM and HTML DOM -> wikitext conversion tests. Round-tripping is brand new and very limited, and does not support the preservation of variable whitespace, templates and other complex constructs yet. Currently 154 parser tests are passing in the new --roundtrip mode that Subbu added last week. Gabriel

3 2

Visual Editor & WikiEditor Integration outside MediaWiki
by Jim Safley 21 May '12

21 May '12

Will I be able to implement the Visual Editor outside MediaWiki? For instance, could I install it as a JavaScript library in a separate application? I notice that the original edit toolbar and the toolbar that comes with the WikiEditor extension are coupled so tightly to MediWiki that it's near impossible to integrate them into a separate application. (If I'm wrong, please educate me.) I wonder if the same will apply to the rich-text editor. Thanks, Jim

2 3

Editing surface/UX: Inline menus
by Erik Moeller 04 May '12

04 May '12

How can we make the Visual Editor as efficient as, or more so than, wikitext editing when it comes to handling complex tasks like citations, templates, etc.? I know it's a bit early to talk about detailed aspects of the editing surface, but this may have some impact on architectural considerations for plug-ins and such, so I wanted to raise it on this list. I don't think it's that much of a stretch goal to be more efficient than wikitext editing for a lot of common cases. For example, using complex templates manually is extremely inefficient, usually requiring a visit to a Template: namespace to read the template documentation, then apply the correct syntax and hope you're not making a typo in the process. A few models: * Wikia's current-generation visual editor offers panels with access to templates and categories, autocompleting as you type. If our goal is to create an editing surface that focuses on the content and gets out of the way (and IMO it should be), these types of panels add clutter which is likely unacceptable. * Most RTE editing surfaces have toolbars, and some also add desktop application style pulldowns. The pulldown/toolbar combination has many known usability issues as software complexity increases -- they become cluttered, and keyboard shortcuts for anything but the stuff you use all the time become hard to remember. * Code IDEs use a lot of hinting/autocompletion based on intelligence gathered from parsing the file you're editing, or any other files. This works well when what gets rendered in the editing surface is identical to what the user is typing. It's easy to auto-complete "myObject.getSomeStuff()", but it's less discoverable that I should start typing "{{Infobox country" to get a beautiful right-aligned table. * vi is the best example of a powerful modal editor which can perform complex operations by essentially entering an in-editor command-line. It's also well-known to be very difficult to learn and master, in large part because its UX is so different from other applications people commonly use. What other models ought to be/are being considered? A couple of ideas: == Inline menus == You could have a menu key, say Ctrl+I or, if we want to be more radical, a single compose key like "\", which triggers an in-editor menu structure with associated keyboard hints. E.g. if the user types <menu key>c, they see an overlay expanding at cursor position: w - cite a website b - cite a book n - cite a newspaper j - cite a journal So by typing: <menu key>cw, I could enter whichever the appropriate dialog is for citing a website (which itself could be rendered in-line if that gives us additional efficiency). This type of system could intelligently trigger auto-completion where appropriate. Say "y" is the shortcut for category, and I type: <menu key>yChurches in <cursor down><cursor down><cursor down><enter/tab> to insert the category "Churches in the United Kingdom". Or say "t" is short for template, so I could type: <menu key>tInfobox a<cursor down><cursor down><enter/tab> to insert the template "Infobox album" and invoke the appropriate dialog. One could make such a feature discoverable by adding hints to the UI in appropriate places, e.g. if the most obvious invocation method is through a tabbed dialog, each dialog could have a small hint indicating how to quickly invoke it inline. == Inline markup completion in visual mode == Another option would be to just intelligently detect use of existing markup, e.g. to magically complete "[[Category:Churches in" or "{{Cite web" or "{{Infobox co" even when in visual mode. This is beneficial for people who already know wiki markup, but is arguably less efficient/user-friendly than a menu/command structure that's designed from scratch to be maximally efficient, discoverable and intuitive. It also would tie us permanently to wiki markup. What do you think? How can we make the visual editing surface maximally efficient for frequent use? All best, Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate

3 3

Parsoid expanding [[:en:Barack Obama]]
by Gabriel Wicke 03 May '12

03 May '12

Hello, template expansion performance in Parsoid has made great strides recently. [[:en:Barack Obama]] now expands in relatively reasonable time and memory: echo '{{:Barack Obama}}' | time node parse.js > obama.html 42.18user 2.04system 0:46.23elapsed 95%CPU (0avgtext+0avgdata 1528480maxresident)k 848inputs+0outputs (8major+691968minor)pagefaults 0swaps Sample output: http://dev.wikidev.net/gabriel/tmp/obama.html The time utility reports the maximum resident memory inflated by a factor of four (some bug in time afaik), so this works out to 382M resident max which matches with top. This is measured on my Intel i3 M370 laptop, and in the same ballpark as the PHP parser running on the cluster. There are a few tokenizer issues visible in the output. Some of them, such as the Navbox templates near the bottom, contain constructs like this: {{#if:foo|<tr><th><th style="foo;|<th style="}} bar;"> Supporting this would be very messy, so the template should be changed to use a saner nesting: {{#if:foo|<tr><th>|}}<th style="{{#if:foo|foo;|}} bar"> We'll have to analyze how common this kind of mis-nesting is, and if we can perhaps fix this up automatically. See also http://www.mediawiki.org/wiki/Parsoid/Todo#Limitations. Next bigger tasks I intend to tackle: * Add full round-trip information, and preserve it through transformations and DOM tree creation * Call back to action=parse to retrieve information we need from the wiki (link existence, image dimensions, many information-based parser functions and magic words, extensions). * Create a [ DOM -> token -> WikiText ] serializer chain based on the existing serializer in the Visual Editor Gabriel

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Wikitext-l May 2012