Re: [Wikitech-l] Editing JSON in MediaWiki

[Gergo Tisza]

You probably want to subclass JsonContentHandler and add wikitext transform
and whatever else you need. For schemas, have a look
at JsonSchemaContentHandler in EventLogging.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Daniel Kinzler]

Am 09.04.2017 um 08:23 schrieb Denny Vrandečić:
> Here's my requirement:
> - a wiki page is one JSON document
> - when editing, the user edits the JSON directly
> - when viewing, I have a viewer that turns the JSON into wikitext, and that
> wikitext gets rendered as wikitext and turned into HTML by MediaWiki

Quick thoughts off the top of my head:

Generating wikitext from some other thing is what Scribunto does. Instead of
using the Lua handler, you would make a handler for Json, with whetever rules
you like for generating wikitext.

I have ne4ver looked at customizing Scribunto, but this seems to right place to
plug this in.

The alternative is to try to have some kind of "cascading" ContentHandler, that
generates a WikiTextContent object first, and then turns that into HTML.


-- 
Daniel Kinzler
Senior Software Developer

Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[zppix e]

That seems like a performance hog in the making in my opinion to not mention, 
mostly unneeded as far as I can tell.

Sent from my iPhone

> On Apr 9, 2017, at 6:11 AM, Gergo Tisza  wrote:
> 
> You probably want to subclass JsonContentHandler and add wikitext transform
> and whatever else you need. For schemas, have a look
> at JsonSchemaContentHandler in EventLogging.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Isarra Yos]

Sounds like what they want is what collaborationlistcontent/handler 
does, specifically, at least for now.


On 09/04/17 06:30, James Hare wrote:

Why, exactly, do you want a wikitext intermediary between your JSON and
your HTML? The value of wikitext is that it’s a syntax that is easier to
edit than HTML. But if it’s not the native format of your data, nor can
browsers render it directly, what’s the point of having it?

The CollaborationKit extension [0] has two content models,
CollaborationHubContent and CollaborationListContent, and they have two
different strategies for parsing. CollaborationHubContent takes validated
JSON and puts out raw HTML; this is the most straightforward to work with.
CollaborationListContent instead puts out wikitext that is fed into the
parser, since it is expected that lists can be transcluded onto other
pages, and this means using wikitext (as transcluded HTML is not an
option). However, this creates a lot of limitations, including parser
restrictions that make sense in the context of arbitrary wikitext parsing
but not when the markup is provided directly by an extension. The long term
plan is for CollaborationListContent to put out HTML, since it’s more
straightforward than using a wikitext intermediary that the user does not
see anyway.

[0] https://www.mediawiki.org/wiki/Extension:CollaborationKit

On April 8, 2017 at 11:23:38 PM, Denny Vrandečić (vrande...@gmail.com)
wrote:

Here's my requirement:
- a wiki page is one JSON document
- when editing, the user edits the JSON directly
- when viewing, I have a viewer that turns the JSON into wikitext, and that
wikitext gets rendered as wikitext and turned into HTML by MediaWiki

I have several options, including:

1) hook for a tag like , and write an extension that parses the
content between the tags and turns it into wikitext (not ideal, as I don't
use any of the existing support for JSON stuff, and also I could have
several such tags per page, which does not fit with my requirements)

2) I found the JsonConfig extension by yurik. This allows me to do almost
all of the things above - but it returns HTML directly, not wikitext. It
doesn't seem trivial to be able to return wikitext instead of HTML, but
hopefully I am wrong? Also, this ties in nicely with the Code Editor.

3) there is actually a JsonContentHandler in core. But looking through it
it seems that this suffers from the same limitations - I can return HTML,
but not wikitext.

3 seems to have the advantage to be more actively worked on that 2 (which
is not based on 3, probably because it is older than 3). So future goodies
like a Json Schema validator will probably go to 3, but not to 2, so I
should probably go to 3.

Writing this down, one solution could be to create the wikitext, and then
call the wikitext parser manually and have it create HTML?

I have already developed the extension in 1, and then fully rewritten it in
2. Before I go and rewrite it again in 3, I wanted to ask whether I am
doing it right, or if should do it completely differently, and also if
there are examples of stuff developed in 3, i.e. of extensions or features
using the JsonContent class.

Example:
I have a JSON document
{ "username": "Denny" }
which gets turned into wikitext
''Hello, [[User:Denny|Denny]]!''
which then gets turned into the right HTML and displayed to the user, e.g.
Hello, Denny!

Cheers,
Denny
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l




___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Thomas PT]

An other maybe relevant example : ProofreadPage has a content model for 
proofreading pages with multiple areas of Wikitext and use some for 
transclusion and others for rendering:

* 
https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/blob/master/includes/page/PageContent.php
* 
https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/blob/master/includes/page/PageContentHandler.php

Thomas

> Le 9 avr. 2017 à 18:44, Isarra Yos  a écrit :
> 
> Sounds like what they want is what collaborationlistcontent/handler does, 
> specifically, at least for now.
> 
> On 09/04/17 06:30, James Hare wrote:
>> Why, exactly, do you want a wikitext intermediary between your JSON and
>> your HTML? The value of wikitext is that it’s a syntax that is easier to
>> edit than HTML. But if it’s not the native format of your data, nor can
>> browsers render it directly, what’s the point of having it?
>> 
>> The CollaborationKit extension [0] has two content models,
>> CollaborationHubContent and CollaborationListContent, and they have two
>> different strategies for parsing. CollaborationHubContent takes validated
>> JSON and puts out raw HTML; this is the most straightforward to work with.
>> CollaborationListContent instead puts out wikitext that is fed into the
>> parser, since it is expected that lists can be transcluded onto other
>> pages, and this means using wikitext (as transcluded HTML is not an
>> option). However, this creates a lot of limitations, including parser
>> restrictions that make sense in the context of arbitrary wikitext parsing
>> but not when the markup is provided directly by an extension. The long term
>> plan is for CollaborationListContent to put out HTML, since it’s more
>> straightforward than using a wikitext intermediary that the user does not
>> see anyway.
>> 
>> [0] https://www.mediawiki.org/wiki/Extension:CollaborationKit
>> 
>> On April 8, 2017 at 11:23:38 PM, Denny Vrandečić (vrande...@gmail.com)
>> wrote:
>> 
>> Here's my requirement:
>> - a wiki page is one JSON document
>> - when editing, the user edits the JSON directly
>> - when viewing, I have a viewer that turns the JSON into wikitext, and that
>> wikitext gets rendered as wikitext and turned into HTML by MediaWiki
>> 
>> I have several options, including:
>> 
>> 1) hook for a tag like , and write an extension that parses the
>> content between the tags and turns it into wikitext (not ideal, as I don't
>> use any of the existing support for JSON stuff, and also I could have
>> several such tags per page, which does not fit with my requirements)
>> 
>> 2) I found the JsonConfig extension by yurik. This allows me to do almost
>> all of the things above - but it returns HTML directly, not wikitext. It
>> doesn't seem trivial to be able to return wikitext instead of HTML, but
>> hopefully I am wrong? Also, this ties in nicely with the Code Editor.
>> 
>> 3) there is actually a JsonContentHandler in core. But looking through it
>> it seems that this suffers from the same limitations - I can return HTML,
>> but not wikitext.
>> 
>> 3 seems to have the advantage to be more actively worked on that 2 (which
>> is not based on 3, probably because it is older than 3). So future goodies
>> like a Json Schema validator will probably go to 3, but not to 2, so I
>> should probably go to 3.
>> 
>> Writing this down, one solution could be to create the wikitext, and then
>> call the wikitext parser manually and have it create HTML?
>> 
>> I have already developed the extension in 1, and then fully rewritten it in
>> 2. Before I go and rewrite it again in 3, I wanted to ask whether I am
>> doing it right, or if should do it completely differently, and also if
>> there are examples of stuff developed in 3, i.e. of extensions or features
>> using the JsonContent class.
>> 
>> Example:
>> I have a JSON document
>> { "username": "Denny" }
>> which gets turned into wikitext
>> ''Hello, [[User:Denny|Denny]]!''
>> which then gets turned into the right HTML and displayed to the user, e.g.
>> Hello, Denny!
>> 
>> Cheers,
>> Denny
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> 
> 
> 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



signature.asc
Description: Message signed with OpenPGP
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] DEADLINE EXTENDED: Wikimania 2017 call for submissions

[phoebe ayers]

Thanks Joseph! Just a followup reminder that submissions are due TOMORROW.

If you have submitted a proposal already but it's marked as a "draft",
please finalize it and mark it as "completed" by tomorrow as well. (If you
are a submitter you may already have email from me about this).

thanks everyone! We are going to have a great program this year!

Phoebe
(for the program committee)



On Sat, Apr 8, 2017 at 10:38 AM, Joseph Seddon 
wrote:

> REMINDER: Deadline for submitting presentations, panels,
> roundtables and workshops to Wikimania is *April 10*.
>
> You have TWO days remaining.
>
> The deadline for posters and birds-of-a-feather sessions remains *May 15*.
>
> Please see below for the call for submissions for Wikimania, and submit
> your ideas! Please also note, for those who have already submitted, there
> is now a field in the registration form for "completed" or "in-progress"
> submission. When you are ready to have your submission reviewed, please
> note that it is "completed". Thank you!
>
> Please contact us with any questions: wikimania-prog...@wikimedia.org
>
> Seddon
>
> Phoebe
> >
> > On Tue, Feb 14, 2017 at 10:10 AM, phoebe ayers 
> > wrote:
> >
> > > All,
> > > I'm very pleased to send out the Wikimania Montréal Call for
> Submissions,
> > > which can be found in French here:
> > > https://wikimania2017.wikimedia.org/wiki/Submissions/fr
> > > and in English here:
> > > https://wikimania2017.wikimedia.org/wiki/Submissions/en
> > >
> > > On behalf of the Wikimania programme committee,
> > > Phoebe Ayers
> > > -
> > >
> > > Que vous soyez un membre de la communauté de l’un des projets Wikimédia
> > > (tels que Wikipédia, Wikibooks, Wikidata, Wikisource, Wikinews,
> Wikimedia
> > > Commons, Wiktionnaire, MediaWiki ou autres), un créateur de contenu
> libre
> > > ou un consommateur, nous recevrons avec plaisir votre proposition pour
> > une
> > > session lors de Wikimania 2017.
> > >
> > > *dates importantes*
> > >
> > > Appel aux propositions ouvert : 2 février 2017
> > > Date limite de soumission des présentations (conférence, panneau, table
> > > ronde et atelier) : *15 avril 2017*
> > > Date limite de soumission des brefs exposés, affiches et réunions
> > > d’oiseaux de la même plume : 15 mai 2017.
> > > Notification d’acceptation des présentations : 20 avril 2017
> > > Notification d’acceptation des brefs exposés, affiches et réunions
> > > d’oiseaux de la même plume : 10 juin 2017
> > >
> > > *Types de soumissions & Comment soumettre: *https://wikimania2017.
> > > wikimedia.org/wiki/Submissions/fr
> > >
> > > *Des questions ?* Merci de contacter le Comité du programme par
> > > wikimania-program(à)wikimedia.org.
> > >
> > > 
> > >
> > > Whether you are a community member of one of the Wikimedia projects
> (such
> > > as Wikipedia, Wikibooks, Wikidata, Wikisource, Wikinews, Wikimedia
> > Commons,
> > > Wiktionary, MediaWiki or others), or a fellow open content creator or
> > > consumer, we welcome your proposal for a session at Wikimania 2017.
> > >
> > > *Important dates*
> > >
> > > Call for proposals opens: February 2, 2017
> > > Deadline for submitting presentation (lecture, panel, roundtable and
> > > workshop) submissions: *April 10, 2017*
> > > Deadline for submitting lightning talks, poster, and birds of a feather
> > > submissions: May 15, 2017
> > > Notification of acceptance for presentations: April 20, 2017
> > > Notification of acceptance for lightning talks, poster and birds of a
> > > feather submissions: June 10, 2017
> > >
> > > *Submission types & how to submit:* https://wikimania2017.
> > > wikimedia.org/wiki/Submissions/en
> > >
> > > *Any questions?* Please contact the Programme Committee at
> > > wikimania-program at wikimedia.org
> > >
> >
> >
> >
> > --
> > * I use this address for lists; send personal messages to phoebe.ayers
> 
> > gmail.com *
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: wikimedi...@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
>
>
>
>
> --
> Seddon
>
> *Advancement Associate (Community Engagement)*
> *Wikimedia Foundation*
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: wikimedi...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 




-- 
* I use this address for lists; send personal messages to phoebe.ayers 
gmail.com *
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.o

Re: [Wikitech-l] Editing JSON in MediaWiki

[Denny Vrandečić]

On Sat, Apr 8, 2017 at 11:30 PM James Hare  wrote:

> Why, exactly, do you want a wikitext intermediary between your JSON and
> your HTML? The value of wikitext is that it’s a syntax that is easier to
> edit than HTML. But if it’s not the native format of your data, nor can
> browsers render it directly, what’s the point of having it?
>

Ah, good question indeed. The reason is that users would be actually
putting fragments of wikitext into the JSON structure, and then the JSON
structure gets assembled into wikitext. Not only would I prefer to have the
users work with fragments of wikitext than fragments of HTML, but some
things are almost impossible with HTML - e.g. making internal links red or
blue depending on the existence of the article, etc.


>
> The CollaborationKit extension [0] has two content models,
> CollaborationHubContent and CollaborationListContent, and they have two
> different strategies for parsing. CollaborationHubContent takes validated
> JSON and puts out raw HTML; this is the most straightforward to work with.
> CollaborationListContent instead puts out wikitext that is fed into the
> parser, since it is expected that lists can be transcluded onto other
> pages, and this means using wikitext (as transcluded HTML is not an
> option). However, this creates a lot of limitations, including parser
> restrictions that make sense in the context of arbitrary wikitext parsing
> but not when the markup is provided directly by an extension. The long term
> plan is for CollaborationListContent to put out HTML, since it’s more
> straightforward than using a wikitext intermediary that the user does not
> see anyway.
>

Thanks, that is super helpful to know! And thanks for the rationale in
particular.


>
> [0] https://www.mediawiki.org/wiki/Extension:CollaborationKit
>
> On April 8, 2017 at 11:23:38 PM, Denny Vrandečić (vrande...@gmail.com)
> wrote:
>
> Here's my requirement:
> - a wiki page is one JSON document
> - when editing, the user edits the JSON directly
> - when viewing, I have a viewer that turns the JSON into wikitext, and that
> wikitext gets rendered as wikitext and turned into HTML by MediaWiki
>
> I have several options, including:
>
> 1) hook for a tag like , and write an extension that parses the
> content between the tags and turns it into wikitext (not ideal, as I don't
> use any of the existing support for JSON stuff, and also I could have
> several such tags per page, which does not fit with my requirements)
>
> 2) I found the JsonConfig extension by yurik. This allows me to do almost
> all of the things above - but it returns HTML directly, not wikitext. It
> doesn't seem trivial to be able to return wikitext instead of HTML, but
> hopefully I am wrong? Also, this ties in nicely with the Code Editor.
>
> 3) there is actually a JsonContentHandler in core. But looking through it
> it seems that this suffers from the same limitations - I can return HTML,
> but not wikitext.
>
> 3 seems to have the advantage to be more actively worked on that 2 (which
> is not based on 3, probably because it is older than 3). So future goodies
> like a Json Schema validator will probably go to 3, but not to 2, so I
> should probably go to 3.
>
> Writing this down, one solution could be to create the wikitext, and then
> call the wikitext parser manually and have it create HTML?
>
> I have already developed the extension in 1, and then fully rewritten it in
> 2. Before I go and rewrite it again in 3, I wanted to ask whether I am
> doing it right, or if should do it completely differently, and also if
> there are examples of stuff developed in 3, i.e. of extensions or features
> using the JsonContent class.
>
> Example:
> I have a JSON document
> { "username": "Denny" }
> which gets turned into wikitext
> ''Hello, [[User:Denny|Denny]]!''
> which then gets turned into the right HTML and displayed to the user, e.g.
> Hello, Denny!
>
> Cheers,
> Denny
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Denny Vrandečić]

On Sun, Apr 9, 2017 at 4:11 AM Gergo Tisza  wrote:

> You probably want to subclass JsonContentHandler and add wikitext transform
>

What does it mean to add wikitext transform?


> and whatever else you need. For schemas, have a look
> at JsonSchemaContentHandler in EventLogging.
>

Thanks, that looks very helpful! I am surprised this is not part of Core,
or a stand-alone component, but it is in EventLogging. Thanks!




> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Denny Vrandečić]

On Sun, Apr 9, 2017 at 8:38 AM Daniel Kinzler 
wrote:

> Am 09.04.2017 um 08:23 schrieb Denny Vrandečić:
> > Here's my requirement:
> > - a wiki page is one JSON document
> > - when editing, the user edits the JSON directly
> > - when viewing, I have a viewer that turns the JSON into wikitext, and
> that
> > wikitext gets rendered as wikitext and turned into HTML by MediaWiki
>
> Quick thoughts off the top of my head:
>
> Generating wikitext from some other thing is what Scribunto does. Instead
> of
> using the Lua handler, you would make a handler for Json, with whetever
> rules
> you like for generating wikitext.
>

Thanks, I will take a look into how Scribunto does that.

>
> I have ne4ver looked at customizing Scribunto, but this seems to right
> place to
> plug this in.
>
> The alternative is to try to have some kind of "cascading" ContentHandler,
> that
> generates a WikiTextContent object first, and then turns that into HTML.
>
>
Not sure what you mean here - just create wikitext and then run it through
the parser?


>
> --
> Daniel Kinzler
> Senior Software Developer
>
> Wikimedia Deutschland
> Gesellschaft zur Förderung Freien Wissens e.V.
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Editing JSON in MediaWiki

[Denny Vrandečić]

Thanks Tpt, that sounds relevant! I will take a look into the code. More
code examples are really useful to figure this all out :)

On Sun, Apr 9, 2017 at 9:53 AM Thomas PT  wrote:

> An other maybe relevant example : ProofreadPage has a content model for
> proofreading pages with multiple areas of Wikitext and use some for
> transclusion and others for rendering:
>
> *
> https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/blob/master/includes/page/PageContent.php
> *
> https://github.com/wikimedia/mediawiki-extensions-ProofreadPage/blob/master/includes/page/PageContentHandler.php
>
> Thomas
>
> > Le 9 avr. 2017 à 18:44, Isarra Yos  a écrit :
> >
> > Sounds like what they want is what collaborationlistcontent/handler
> does, specifically, at least for now.
> >
> > On 09/04/17 06:30, James Hare wrote:
> >> Why, exactly, do you want a wikitext intermediary between your JSON and
> >> your HTML? The value of wikitext is that it’s a syntax that is easier to
> >> edit than HTML. But if it’s not the native format of your data, nor can
> >> browsers render it directly, what’s the point of having it?
> >>
> >> The CollaborationKit extension [0] has two content models,
> >> CollaborationHubContent and CollaborationListContent, and they have two
> >> different strategies for parsing. CollaborationHubContent takes
> validated
> >> JSON and puts out raw HTML; this is the most straightforward to work
> with.
> >> CollaborationListContent instead puts out wikitext that is fed into the
> >> parser, since it is expected that lists can be transcluded onto other
> >> pages, and this means using wikitext (as transcluded HTML is not an
> >> option). However, this creates a lot of limitations, including parser
> >> restrictions that make sense in the context of arbitrary wikitext
> parsing
> >> but not when the markup is provided directly by an extension. The long
> term
> >> plan is for CollaborationListContent to put out HTML, since it’s more
> >> straightforward than using a wikitext intermediary that the user does
> not
> >> see anyway.
> >>
> >> [0] https://www.mediawiki.org/wiki/Extension:CollaborationKit
> >>
> >> On April 8, 2017 at 11:23:38 PM, Denny Vrandečić (vrande...@gmail.com)
> >> wrote:
> >>
> >> Here's my requirement:
> >> - a wiki page is one JSON document
> >> - when editing, the user edits the JSON directly
> >> - when viewing, I have a viewer that turns the JSON into wikitext, and
> that
> >> wikitext gets rendered as wikitext and turned into HTML by MediaWiki
> >>
> >> I have several options, including:
> >>
> >> 1) hook for a tag like , and write an extension that parses the
> >> content between the tags and turns it into wikitext (not ideal, as I
> don't
> >> use any of the existing support for JSON stuff, and also I could have
> >> several such tags per page, which does not fit with my requirements)
> >>
> >> 2) I found the JsonConfig extension by yurik. This allows me to do
> almost
> >> all of the things above - but it returns HTML directly, not wikitext. It
> >> doesn't seem trivial to be able to return wikitext instead of HTML, but
> >> hopefully I am wrong? Also, this ties in nicely with the Code Editor.
> >>
> >> 3) there is actually a JsonContentHandler in core. But looking through
> it
> >> it seems that this suffers from the same limitations - I can return
> HTML,
> >> but not wikitext.
> >>
> >> 3 seems to have the advantage to be more actively worked on that 2
> (which
> >> is not based on 3, probably because it is older than 3). So future
> goodies
> >> like a Json Schema validator will probably go to 3, but not to 2, so I
> >> should probably go to 3.
> >>
> >> Writing this down, one solution could be to create the wikitext, and
> then
> >> call the wikitext parser manually and have it create HTML?
> >>
> >> I have already developed the extension in 1, and then fully rewritten
> it in
> >> 2. Before I go and rewrite it again in 3, I wanted to ask whether I am
> >> doing it right, or if should do it completely differently, and also if
> >> there are examples of stuff developed in 3, i.e. of extensions or
> features
> >> using the JsonContent class.
> >>
> >> Example:
> >> I have a JSON document
> >> { "username": "Denny" }
> >> which gets turned into wikitext
> >> ''Hello, [[User:Denny|Denny]]!''
> >> which then gets turned into the right HTML and displayed to the user,
> e.g.
> >> Hello, Denny!
> >>
> >> Cheers,
> >> Denny
> >> ___
> >> Wikitech-l mailing list
> >> Wikitech-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >> ___
> >> Wikitech-l mailing list
> >> Wikitech-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> >
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> _