User tests: Successful: Unsuccessful:
The tags, note and version note fields should have a span12 (to be full width) (and any other text field you want full width).
All select fields should not have this.
None of the fields should have the 'small' class.
And those classes should be added in XML wherever possible ;-)
PS: Note and Version note is not the same.
Having all fields get span12 makes it uglier and less easy to differentiate between the options (we did the tests).
Also, some field types don't work well with span12, like date selection fields and the yes/no btn-groups (too wide on wide screens).
So we only use span12 on only text fields that can use the full width. So fields that generally (can) contain more than one word.
@nonumber thanks again.
so only the text fields using class="inputbox" should have class="inputbox span12" ? (I hope i understand you correct)
EDIT: and the other fields there are not a text field should not use span12?
@infograf768 thanks but i cant find the span12 class at a xml file for this or i'm wrong there?
Not sure all text fields have a class="inputbox" as that class isn't used for anything in isis. Not sure if hathor uses it. But the class is pretty much forgotten.
I think @infograf768 means that the Maximum Articles field could use a class="input-mini". Otherwise I have no idea what he means. Fields on the right look fine to me.
What field is fine? No idea what you are talking about or what you are trying to fix/change.
No, like I said:
So we only use span12 on only text fields that can use the full width. So fields that generally (can) contain more than one word.
So on text fields like notes, yes, use span12
.
On a text field that is meant to only hold a few characters, like the 'Maximum articles' field, use the input-mini
. Or input-small
for fields that should contain 0-10 characters.
So on text fields like notes, yes, use span12.
On a text field that is meant to only hold a few characters, like the 'Maximum articles' field, use the input-mini. Or input-small for fields that should contain 0-10 characters.
ok. I will update the patch for this later. I start now to find out what fields should have span12 and which not :)
If i ready i update this here :)
Thanks again :)
Here the Link:
http://www.jah-tz.de/jb/joomlacode/span12.png
if this is ok i will change the PR for this
Thanks
@zero-24 Looking purely on the image http://www.jah-tz.de/jb/joomlacode/span12.png :
Alignment of drop-downs and btn-groups look good.
That's at a given width, same for all ?, and version notes and tags will adapt to the span12 width, while drop-downs and btn-groups will stay that width ?
Would be good to take one of the views with tags and version note and show how they adapt to the width (showing right window border too).
That's at a given width, same for all ?, and version notes and tags will adapt to the span12 width, while drop-downs and btn-groups will stay that width ?
yes
Would be good to take one of the views with tags and version note and show how they adapt to the width (showing right window border too).
Seems all good to me.
Looks good.
Related picture from tracker: http://downloads.joomlacode.org/trackeritem/8/5/4/85487/bugs_at_edit_views.png :