[Moving threads for on-topic-ness.]
On 16 January 2015 at 07:01, Brian Wolff wrote:
> Does anyone actually have
> anything they want that is difficult to do currently and requires a mass
> compat break?
Sure.
Three quick examples of things on the horizon (I'm not particularly saying
we'd ac
Why wikitext is so much disliked? It's more compact to type than HTML. It's
a templating language. HTML is not. Then something like Handlebars (which
is weaker than wikitext) should be used. Or, something like web components
and custom tags. But why removing nice thing (wikitext) which saves a lot
On Jan 16, 2015 1:05 PM, "James Forrester" wrote:
>
> [Moving threads for on-topic-ness.]
>
> On 16 January 2015 at 07:01, Brian Wolff wrote:
>
> > Does anyone actually have
> > anything they want that is difficult to do currently and requires a mass
> > compat break?
>
>
> Sure.
>
> Three quic
Hey,
FYI: we had this discussion for SMW some time ago. We where at version 1.9,
following a naming pattern very similar to the MediaWiki one. The question
there was if the next release containing a break should be either 1.10 (no
change), 2.0 (following semver) or 10.0 (dropping the "1."). People
Hi,
>- Get rid of wikitext on the server-side.
> - HTML storage only. Remove MWParser from the codebase. All
> extensions that hook into wikitext (so, almost all of them?) will need
> to
> be re-written.
You gotta to be kidding. It seems we are a bit out of sync here with
t
On 20 January 2015 at 12:04, Jeroen De Dauw wrote:
> >
>- Get rid of wikitext on the server-side.
> > - HTML storage only. Remove MWParser from the codebase. All
> > extensions that hook into wikitext (so, almost all of them?) will
> > need to
> > be re-written.
> >
>
> J
On 2015-01-20 12:21 PM, James HK wrote:
> Hi,
>
>>- Get rid of wikitext on the server-side.
>> - HTML storage only. Remove MWParser from the codebase. All
>> extensions that hook into wikitext (so, almost all of them?) will need
>> to
>> be re-written.
> You gotta to be kiddi
Hi,
On 1/21/15, Daniel Friesen wrote:
> On 2015-01-20 12:21 PM, James HK wrote:
>> Hi,
>>
>>>- Get rid of wikitext on the server-side.
>>> - HTML storage only. Remove MWParser from the codebase. All
>>> extensions that hook into wikitext (so, almost all of them?) will
>>> need
>>
On Jan 20, 2015 4:22 PM, "James Forrester" wrote:
>
> On 20 January 2015 at 12:04, Jeroen De Dauw
wrote:
>
> > >
> >- Get rid of wikitext on the server-side.
> > > - HTML storage only. Remove MWParser from the codebase. All
> > > extensions that hook into wikitext (so, almost a
On Jan 20, 2015 5:53 PM, "Brian Wolff" wrote:
>
>
> On Jan 20, 2015 4:22 PM, "James Forrester"
wrote:
> >
> > On 20 January 2015 at 12:04, Jeroen De Dauw
wrote:
> >
> > > >
> > >- Get rid of wikitext on the server-side.
> > > > - HTML storage only. Remove MWParser from the codebase.
On Tue, Jan 20, 2015 at 7:53 PM, Brian Wolff wrote:
> My second reason for being skeptical is im mostly unclear on what the
> benefits are over wikitext storage (this is the first time ive heard of the
> ve w/o parsoid thing. Are there other benefits? Simplifying parser cache by
> not having parse
11 matches
Mail list logo
