Thank you Issara for rephrasing it in a different way. As I mentioned before we can think of it as a way of progressive disclosurehttp://en.wikipedia.org/wiki/Progressive_disclosureof complexity Visual editor has fewer controls and less complexity than the existing Wikitext editor, both in its UI and its presentation of content.
Allowing access, albeit deemphasized to the wikitext editor, only from within the VE environment fits nicely with that goal. Again I'm not suggesting that we remove direct access to the wikitext editor if a preference has been set, but in all other cases the VE does provide an experience that will benefit new and existing users alike while (if implemented) a 1 click switch to the old editing experience.
For me it is about trust and confidence as well as establishing a direction with intention, If we show doubt that the VE is in fact a better experience and provide top level choice between the two editor experiences we are not showing that confidences
* * * * *Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Fri, Jun 21, 2013 at 12:17 PM, Isarra Yos zhorishna@gmail.com wrote:
Perhaps we're asking the wrong question here.
There are two options, and how they are presented either results in problems with clutter, or with clarity, but both options are for the same action of editing the page/section. So why present the options until the user clicks on the link for editing at all?
Now at that point it could go with a dropdown presenting the choices, but let's look at how this sort of thing, with two or more edit modes, is usually done across existing platforms: Click the link/button, and generally it opens up to the visual editor by default. From there, the source mode is a tab or option that can then be switched between as needed, with the visual editor also doubling as a preview if the user is working mostly in source.
Wordpress is a good example. Their visual editor itself makes me want to cry, but the interface is clearly navigable and such. It's basically what I expected with this when I first heard of it as well.
-K
On 21/06/13 17:40, Trevor Parscal wrote:
VisualEditor has the option to take over section edit links. We find this is probably going to be unpopular for people who want to at least sometimes edit wikitext, but don't want to loose them as VisualEditor users. After discussing a few different options, including showing both links (really cluttered and horribly long in some languages) and using icons (no icon would really convey what we want here).
We have decided that it's probably best to make the edit link show an alternative in a menu on hover. There's a prototype of this (somewhere) that MatmaRex has hacked together (screenshot attached) which is close. I mocked something up that is similar but perhaps a little better looking.
Max brings up a good point about my mockup, which is that it doesn't quite fit with other vector-isms. Given that Vector is something we want to evolve, we shouldn't get too caught up in that, but it's something worth considering since deviation from what vector is today should probably only be done if it's in the direction of what Vector should be in the future.
I'm hoping that others on the list could perhaps make suggestions, offer ideas, make simple mockups or prototypes and help make this feature as good as possible.
We need to have this solved quickly since we are releasing in a couple of weeks.
- Trevor
Design mailing listDesign@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/design
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design