Hello,
I was wondering if there was a way to enable to VisualEditor in the Main namespace for 3rd-party wikis, or if an ETA is known for when users will able to do that?
Thanks!
On 24 August 2012 06:29, Andrew Martin martopolis@gmail.com wrote:
I was wondering if there was a way to enable to VisualEditor in the Main namespace for 3rd-party wikis, or if an ETA is known for when users will able to do that?
This is possible, but I would not recommend it. Firstly, because there is a lot of missing functionality in VisualEditor right now, and which won't "round-trip" cleanly if left alone (for example, categories or template transclusions). Also, VisualEditor depends on Parsoid to convert between wikitext and HTML, which as well as being incomplete, the team are currently re-writing from NodeJS into C++.
In the Wikimedia Foundation's Engineering Goals for 2012/13[0], we have said that we expect to have an initial "real-world" deployment in December this year, and proper integration (including proper installation instructions!) by June/July next year. Hopefully we may have something useful for general third parties before then, but if you want to try ahead of this schedule, there are instructions to set up Parsoid here[1] and you get grab a copy of the current head for VisualEditor similarly with[2]. Of course, we'd be interested in your feedback and thoughts on what we've got already, and how we could improve it. :-)
Sorry that the timeline isn't shorter.
[0] - https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Milestone... [1] - https://www.mediawiki.org/wiki/Parsoid#Getting_started [2] - git clone https://gerrit.wikimedia.org/r/p/mediawiki/extensions/VisualEditor.git
Yours,
On Fri, Aug 24, 2012 at 6:45 AM, James Forrester jdforrester@gmail.com wrote:
This is possible, but I would not recommend it.
It's not easily possible to disable the namespace restriction without hacking the extension itself. We should make it easier to disable, I'll work on that. Other than that James is completely right, VE isn't quite ready for prime time, which is why we haven't enabled it in the main namespace on any of our wikis yet.
Roan
On Fri, Aug 24, 2012 at 6:45 AM, James Forrester jdforrester@gmail.com wrote:
On 24 August 2012 06:29, Andrew Martin martopolis@gmail.com wrote:
I was wondering if there was a way to enable to VisualEditor in the Main namespace for 3rd-party wikis, or if an ETA is known for when users will able to do that?
This is possible, but I would not recommend it. Firstly, because there is a lot of missing functionality in VisualEditor right now, and which won't "round-trip" cleanly if left alone (for example, categories or template transclusions). Also, VisualEditor depends on Parsoid to convert between wikitext and HTML, which as well as being incomplete, the team are currently re-writing from NodeJS into C++.
One idea we've been kicking around here is the idea that, for brand new wikis, instead of storing wikitext, we could offer an alternate configuration where we store the HTML5+RDFa representation instead of wikitext, thus making Parsoid an optional feature rather than a requirement for running MediaWiki. This approach means that editors on a wiki using VisualEditor without Parsoid would not be able to edit wikitext at all.
The upside of this approach is simplicity for both editors and administrators. The downside of this approach is that it will be a while before VisualEditor will be able to support enough of the features of wikitext such that *all* editors can forego direct wikitext access and still have a fully-functional wiki. So, this idea is (I think) still in the "hey, maybe we could do that" stage rather than a fixed part of the plan.
Rob
On 24 August 2012 20:16, Rob Lanphier robla@wikimedia.org wrote:
One idea we've been kicking around here is the idea that, for brand new wikis, instead of storing wikitext, we could offer an alternate configuration where we store the HTML5+RDFa representation instead of wikitext, thus making Parsoid an optional feature rather than a requirement for running MediaWiki. This approach means that editors on a wiki using VisualEditor without Parsoid would not be able to edit wikitext at all. The upside of this approach is simplicity for both editors and administrators. The downside of this approach is that it will be a while before VisualEditor will be able to support enough of the features of wikitext such that *all* editors can forego direct wikitext access and still have a fully-functional wiki. So, this idea is (I think) still in the "hey, maybe we could do that" stage rather than a fixed part of the plan.
Obsoleting Wikitext is a wonderful, wonderful idea and much to be desired.
So is it a meaningful concept to directly edit said well-structured computer guacamole? By which I mean "not less difficult than directly editing the present ad-hoc computer guacamole".
- d.
wikitext-l@lists.wikimedia.org