On 11 Jan 2016 at 14:16:40, Marius Dumitru Florea (
 mariusdumitru.florea@xwiki.com(mailto:mariusdumitru.florea@xwiki.com))
 wrote:
  On Mon, Jan 11, 2016 at 2:00 PM,
vincent(a)massol.net
 wrote:
 > Hi Marius,
 >
 > I prefer to think in term of use cases. Here are the ones I see as
 > important on this topic and that I think we need to ensure that we
 > implement:
 >
 > UC1: Ability for admins to install an extension that contributes a new
 > editor
 > UC2: Ability for admins to select which editor is the default editor 
 for
  > their users in a given wiki (note that
ideally this configuration 
 should be
  > per wiki for the farm use case)
 > UC3: Ability for admins to decide which editors are active (i.e. which
 > editors users will be able to configure or use). For example it should 
 be
  > possible to completely replace the GWT-based
WYSIWYG by CKEeditor and
 > preventing any user from using the GWT-based WYSIWYG editor.
 > UC4: Ability for a user (simple or advanced) to explicitly decide which
 > default editors he/she’ll use (in his/her user profile probably). 
 Should
  > override the editor selected in UC2 (but
they should only see editors 
 that
  > are active, cf UC3)
 > UC5: Ability for an advanced user to choose on the spot (on-demand) the
 > editor to use to edit a given page, bypassing the default editor. 
 Should
   override
the editor selected in UC4.
 WDYT?
 
 All these use cases are covered by both A and B so it doesn't help me
 choose one or the other. My question is more how to implement these use
 cases: using A or B? 
 
 Ok cool if they’re covered by A and B (it wasn’t mentioned in your email…).
 
  Note that currently there’s no default choice
anymore for advanced users
 when they edit a page and we’d need to put that back (that’s UC4).
 
 . The first entry in the Edit menu is "Edit" which leads to the default
 edit mode. Of course, it's not as in Colibri, you still need to open the
 menu.