?
avatar brianteeman
brianteeman
23 Jul 2016

Is there a reason for the difference between these two layouts?
If not then we should standardise on one of them (preferably the menu version for me)

Article Options View

articleoptions

Menu Options View

menuoptions

avatar brianteeman brianteeman - open - 23 Jul 2016
avatar ggppdk
ggppdk - comment - 23 Jul 2016

Besides the options themselves , that should be ?same? and have same order

besides the above, UI good practice directives,
suggest to use radio buttons for up to 4-5 choices, (unless texts are too long),
right ?

avatar brianteeman
brianteeman - comment - 23 Jul 2016

I am happy with both of the displays I just want us to chose one single
style

On 23 July 2016 at 15:58, Georgios Papadakis notifications@github.com
wrote:

Besides the options themselves , that should be ?same? and have same order

besides the above, UI good practice directives,
suggest to use radio buttons for up to 4-5 choices, (unless texts are too
long),
right ?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#11262 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8bT0863_VhvEThJswx2BSye-3lh2ks5qYh4VgaJpZM4JTWUm
.

Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/

avatar ggppdk
ggppdk - comment - 23 Jul 2016

besides the above, UI good practice directives, suggest to use radio buttons for up to 4-5 choices, (unless texts are too long),

to be honest, i very much dislike unneeded drop-downs having only 3-4 options

Disadvantages

  • More difficult to read all of them at once or to search for a string !!
  • if you want to find available options of any of them you need to 2 clicks, 1 to open and read, 2nd click to close, radio needs zero clicks
  • if you want to change you need 2 clicks, radio needs 1 click
avatar dgt41
dgt41 - comment - 23 Jul 2016

I totally agree with George on this one, this a common practice and there is a trent to abandon dropdowns lately. I would guess the UX/UI team could accomplish this easy task...

avatar brianteeman
brianteeman - comment - 23 Jul 2016

It's an easy task and I'm happy to do it. I guess my original question was
to see if there was a reason I couldn't see for these two views to be
different

avatar ggppdk
ggppdk - comment - 24 Jul 2016

suggest to use radio buttons for up to 4-5 choices, (unless texts are too long)=phrases,

For phrases the radio-set must be have a vertical placement without the btn-group !!

  • otherwise it is best to remain a select drop down !!

i did not suggest to convert drop-down selects that contain 3-5 phrases into a horizontal radio-set !
it will be quite difficult to read !

[EDIT]

  • also a case like "above" , "below" can not be made a radio-set without a new CSS styling, now if you make radio and add: btn-group

because it will be "red / green" which is meaningless

avatar dgt41
dgt41 - comment - 24 Jul 2016

@ggppdk yes context is essential but I am just pointing:
screen shot 2016-07-24 at 21 29 43
part of this great article: https://uxdesign.cc/design-better-forms-96fadca0f49c#.hgv8q1eoa

Also it is very hard to ditch selects especially in cases like:
screen shot 2016-07-24 at 21 35 30

avatar ggppdk
ggppdk - comment - 24 Jul 2016

Yes, i was going to link that article

and i am revising my data forms and configuration forms lately,
and that is why also posted here too

avatar brianteeman brianteeman - change - 25 Jul 2016
Labels Added: ?
avatar brianteeman
brianteeman - comment - 25 Jul 2016

I am going to have a play at this over the next few days. Some of the issues without selects (i agree they are bad) is the mobile view. Also I wonder if we need to use red/green at all - why not just use a single colour to indicate the selected option

avatar brianteeman brianteeman - change - 28 Jul 2016
Category Templates (admin)
avatar brianteeman brianteeman - change - 3 Aug 2016
Status New Discussion
avatar brianteeman
brianteeman - comment - 7 Sep 2016

Closed as we have a PR see #11968

avatar brianteeman brianteeman - change - 7 Sep 2016
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2016-09-07 12:15:38
Closed_By brianteeman
avatar brianteeman brianteeman - close - 7 Sep 2016

Add a Comment

Login with GitHub to post a comment