I believe Subbu will follow up with a more complete response, but I'll note
that:
1) no plan survives first encounter with the enemy. Parsoid was going to
be simpler than the PHP parser, Parsoid was going to be written in PHP,
then C, then prototyped in JS for a later implementation in C, etc.
, the less
complicated things will be, correct?
Date: Tue, 20 Jan 2015 11:02:10 -0500
From: canan...@wikimedia.org
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] Parsoid's progress
I believe Subbu will follow up with a more complete response, but I'll note
that:
1) no plan
C. Scott Ananian wrote:
1) no plan survives first encounter with the enemy. Parsoid was going to
be simpler than the PHP parser, Parsoid was going to be written in PHP,
then C, then prototyped in JS for a later implementation in C, etc. It
has varied over time as we learned more about the
Thank you both for the detailed replies. They were very helpful and I feel
like I have a better understanding now. I'm still trying to wrap my head
around Parsoid, its implementation, and how it fits in with the larger
future of MediaWiki development.
Subramanya Sastry wrote:
The core parser has
Exactly: The HTML to wikitext conversion is what makes Parsoid useful, and
not only for VE.
Thanks to Parsoid, ContentTranslation has a simple rich text editor with
contenteditable (not a full VE, though this may change in the future). We
are just starting to deploy it to production, but the
On 01/19/2015 08:15 AM, MZMcBride wrote:
Currently Parsoid is the largest client of the MediaWiki PHP parser, I'm
told. If Parsoid is regularly calling and relying upon the MediaWiki PHP
parser, what exactly is the point of Parsoid?
Parsoid can go:
wikitext = HTML = wikitext
The MediaWiki
Matthew Flaschen wrote:
On 01/19/2015 08:15 AM, MZMcBride wrote:
And from this question flows another: why is Parsoid
calling MediaWiki's api.php so regularly?
I think it uses it for some aspects of templates and hooks. I'm sure
the Parsoid team could explain further.
I've been discussing
(Combining pieces of Jay's thread and pieces of the shared hosting thread.)
Daniel Friesen wrote:
Parsoid can do Parsoid DOM to WikiText conversions. So I believe the
suggestion is that storage be switched entirely to the Parsoid DOM and
WikiText in classic editing just becomes a method of
@lists.wikimedia.org
Subject: [Wikitech-l] Parsoid's progress
(Combining pieces of Jay's thread and pieces of the shared hosting thread.)
Daniel Friesen wrote:
Parsoid can do Parsoid DOM to WikiText conversions. So I believe the
suggestion is that storage be switched entirely to the Parsoid DOM
