In-place editing is going to be the future of all collaborative content, or at least, it's hard to imagine otherwise.
This is possibly the greatest step forward that the VisualEditor promises to bring Mediawiki. Odd that it was hardly mentioned in the tldr thread "Odd plans on Future/Parser_plan - are they true?". Perhaps some people have not tried the new editor? http://www.mediawiki.org/wiki/Special:VisualEditorSandbox
Let me please not reopen the questions of l33tism or wikitext whimsey, I simply wanted to state that clicking directly on the cursor location you want to edit is a big deal. One's poor brain does not have to shift gears; the computer actually saves you a little bit of your life (how often can you say that?); this is a good interface.
...and having a parser in Javascript will really broaden the horizons for wikipedia: embedding wiki content in another application, offline editing, abandoning legacy mediawiki code, to name a few.
-Adam
On Wed, 21 Mar 2012 00:43:51 -0700, Adam Wight wrote:
In-place editing is going to be the future of all collaborative content, or at least, it's hard to imagine otherwise.
This is possibly the greatest step forward that the VisualEditor promises to bring Mediawiki. Odd that it was hardly mentioned in the tldr thread "Odd plans on Future/Parser_plan - are they true?". Perhaps some people have not tried the new editor? http://www.mediawiki.org/wiki/Special:VisualEditorSandbox
How to edit the Wikitext there, and immediately see the parsed result during editing? (NOT vice versa, like now - edit parsed result and see the code)
When playing with the visual editor this morning I noticed that myself too. It would be nice if the markup could be edited as well as the parsed version. I mean don't forget that it's going to be hard to add {{#ifeq:}} and all those syntax parsers if you can't edit the source code to it.
-----Original Message----- From: wikitext-l-bounces@lists.wikimedia.org [mailto:wikitext-l-bounces@lists.wikimedia.org] On Behalf Of vitalif@yourcmc.ru Sent: Wednesday, March 21, 2012 17:51 To: Wikitext-l Subject: Re: [Wikitext-l] Long live the visual editor!
On Wed, 21 Mar 2012 00:43:51 -0700, Adam Wight wrote:
In-place editing is going to be the future of all collaborative content, or at least, it's hard to imagine otherwise.
This is possibly the greatest step forward that the VisualEditor promises to bring Mediawiki. Odd that it was hardly mentioned in the tldr thread "Odd plans on Future/Parser_plan - are they true?". Perhaps some people have not tried the new editor? http://www.mediawiki.org/wiki/Special:VisualEditorSandbox
How to edit the Wikitext there, and immediately see the parsed result during editing? (NOT vice versa, like now - edit parsed result and see the code)
_______________________________________________ Wikitext-l mailing list Wikitext-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitext-l
----- Original Message -----
From: "Maximilian Doerr" cybernet678@yahoo.com
When playing with the visual editor this morning I noticed that myself too. It would be nice if the markup could be edited as well as the parsed version. I mean don't forget that it's going to be hard to add {{#ifeq:}} and all those syntax parsers if you can't edit the source code to it.
As one of the "wikitext will never die" contingent, I'm going to do my best not to say anything that sounds like "We told you so" here.
Cheers, -- jr 'walks into the sunset, snickering quietly' a
On Wed, 21 Mar 2012 17:53:56 -0400, Maximilian Doerr wrote:
When playing with the visual editor this morning I noticed that myself too. It would be nice if the markup could be edited as well as the parsed version. I mean don't forget that it's going to be hard to add {{#ifeq:}} and all those syntax parsers if you can't edit the source code to it.
That's what I've meant somewhere in the tldr thread... The visual inplace editor is a good idea to try, but it should be implemented with GREAT CARE, not like "you'll not going to be able to edit wikitext from now anymore"... Or you'll going to be able to parse text on the server anymore... Or only with server-side javascript... :D :)
On Wed, Mar 21, 2012 at 2:59 PM, vitalif@yourcmc.ru wrote:
That's what I've meant somewhere in the tldr thread... The visual inplace editor is a good idea to try, but it should be implemented with GREAT CARE, not like "you'll not going to be able to edit wikitext from now anymore"... Or you'll going to be able to parse text on the server anymore... Or only with server-side javascript... :D :)
Yes, we are definitely keeping wikitext around. We also want the editor to support switching between wikitext and visual mode as suggested earlier in this thread, but that hasn't been implemented yet. The prototype we released wasn't really a "this is what we'd like it to be" demo, more like a "this is what we have right now" demo.
Roan
On 03/21/2012 11:53 PM, Maximilian Doerr wrote:
When playing with the visual editor this morning I noticed that myself too. It would be nice if the markup could be edited as well as the parsed version. I mean don't forget that it's going to be hard to add {{#ifeq:}} and all those syntax parsers if you can't edit the source code to it.
Well, there is wiki-view and I guess there'll be round-trip there, after all?
However, I'm frowning in puzzlement at the level of visual empowerment of the wiki-link editing (my most unfavourite task). Is it planned to be left at that, just plain entry field for a title? No list browsing, no search, no search for partial hits or, say, soundexes?
Yury
On 22 March 2012 16:31, Yury Tarasievich yury.tarasievich@gmail.com wrote:
However, I'm frowning in puzzlement at the level of visual empowerment of the wiki-link editing (my most unfavourite task). Is it planned to be left at that, just plain entry field for a title? No list browsing, no search, no search for partial hits or, say, soundexes?
I believe the software uses a development methodology known as "open source" that sounds quite exciting in its potential.
- d.
On 03/22/2012 05:40 PM, David Gerard wrote:
On 22 March 2012 16:31, Yury Tarasievichyury.tarasievich@gmail.com wrote:
However, I'm frowning in puzzlement at the level of visual empowerment of
...
I believe the software uses a development methodology known as "open source" that sounds quite exciting in its potential.
Whatever. For all you know, folks having issues with The Next Big Thing might not even be in IT industry (I'm not, for one).
Yury
On Thu, Mar 22, 2012 at 9:31 AM, Yury Tarasievich yury.tarasievich@gmail.com wrote:
However, I'm frowning in puzzlement at the level of visual empowerment of the wiki-link editing (my most unfavourite task). Is it planned to be left at that, just plain entry field for a title? No list browsing, no search, no search for partial hits or, say, soundexes?
You're looking at a quick prototype which is by no means final. Of course the link editing feature should be much richer, but we haven't written the code for that right now. We just released what we had at the time.
Roan
On Wed, Mar 21, 2012 at 8:43 AM, Adam Wight spam@ludd.net wrote:
y, I simply wanted to state that clicking directly on the cursor location you want to edit is a big deal.
I like it! so an idea for the next step would be able to preview the link created and also interactively select them from a list. I would want to be able to build up a list of links on the page. ones on my watchlist and recently edited links to select from. I really think this would be a cool feature. I like the new editor!
I was playing with etherpad and gutting it so that I could use a perl backend, https://github.com/h4ck3rm1k3/introspector-wiki-server/tree/master/etherpad I made some progress in reverse engineering it, of course there is alot more work to do. In theory we could have users being able to see each others edits (if they wanted to)
Exciting!
mike
wikitext-l@lists.wikimedia.org