All propositions are nice.  However, this is my point of view.

# Variant 2.1:
Enumeration probably isn't a good option; it works when you have 2 languages, it
begins to cause problems when you have 20 (visual annoyance, possible problem of
UI alignement)

but visual of 2.1.1 is nice :-)

# Variant 2.2:
This is my preferred view.  I'm not sure which one of the subvariant is the best
but I would eliminate the first one for the same reason as 2.3 (see below).
However, the user will click in order to load another page/content, then a link
like 2.2.2 would be better?

# Variant 2.3:
I'm against adding another big button in the UI.  The strength of Flamingo is
for me that it is far more visually light that Colibri.

# Variant 2.4:
This seems to be a good solution, as well as 2.2.  Just personal, I would go for
the 2.2 instead of 2.4 because language is part of the content and should be
displayed without clicking on a button.

This is only my point of view.

Hope this helps.

On Mon, Aug 18, 2014 at 06:34:26PM +0300, Ecaterina Moraru (Valica) wrote:
> Hi devs,
> 
> We have http://jira.xwiki.org/browse/XWIKI-10745 (Improve the display of
> available languages in Flamingo) which is related to
> http://jira.xwiki.org/browse/XWIKI-6402 (Separate Interface language and
> page language settings)
> 
> While in Flamingo we could just make the language links look better,
> without changing the functionality, for the future, the separation is
> something we might want to tackle, that's why I've created this proposal
> page
> http://design.xwiki.org/xwiki/bin/view/Proposal/InterfaceAndContentLanguageSeparation
> 
> I am interested in what you think about the variants.
> 
> Thanks,
> Caty
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs

-- 
Jean SIMARD <[email protected]>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to