SJ, the New and Returning user pattern is a very good application for this.
I’m not against multiple columns, and think it makes sense in case of many inputs to fill in, specially if u can group the related ones. My suggestion would be to align the labels above the inputs. This makes the grid stronger and IMO is easier to map the fields. Thanks, Gabriel > On Sep 23, 2016, at 9:06 AM, Greg Sheremeta <gsher...@redhat.com> wrote: > > > > On Fri, Sep 23, 2016 at 8:02 AM, Roxanne Hoover <rohoo...@redhat.com > <mailto:rohoo...@redhat.com>> wrote: > To offer a differing opinion to Greg, I prefer even my address fields to be > single column. I will say, frequently, because I'm usually filling out my own > address, it all autofills for me. > > +1. I use Lastpass, but for those times it fails ... > > > Thinking more generally, the case of multi-column address forms is not > uncommon - tabbing would be a priority. > > On Fri, Sep 23, 2016 at 3:22 AM, Greg Sheremeta <gsher...@redhat.com > <mailto:gsher...@redhat.com>> wrote: > SJ, > > I agree with the conclusion! I sat with it for several minutes, and thought > to myself -- hmm, I hate all multi-column forms. Then I looked at the address > form -- yep, hated it. Then I thought about wanting to fill out my address -- > hm, I hate it when the last name field is under the first name. Gah, the zip > should always be next to the city! Oh, so, I don't hate it! It's exactly > correct! lol > > And the login/reg is perfect, I'd say ubiquitous. It needs no further > discussion IMO and can just get stamped as a pattern :) > > Once again, great work! > > Greg > > > On Fri, Sep 23, 2016 at 2:44 AM, SJ Cox <sj...@redhat.com > <mailto:sj...@redhat.com>> wrote: > Hello UXD and PatternFly community, > > Would love to get your input on when, if ever, multi-column forms are okay. > > This sprint the PatternFly team is working on the conceptual design for multi > column forms. In the case of multi column forms, it’s mostly best practice > to avoid their use. The main problem is that using multiple columns within > forms could cause the potential for users to interpret the fields > inconsistently. > > However, there are a couple exceptions that seem to be acceptable. > > - The main exception for using multi-column forms that cause the least amount > of confusion were strictly for name and address fields. > > <Screen Shot 2016-09-22 at 11.23.59 PM.png> > > - The second exception is when there are two different form choices. User > must choose to fill out one or the other. In this case, when the forms > fields are shown next to each other in a multi column format, there is little > confusion as long as the distinction of the two form choices are clear. > > <Screen Shot 2016-09-22 at 11.06.08 PM.png> > > Would love to hear your thoughts and input on this topic. Are there any > other scenarios that are acceptable? Do you agree with the conclusion? > > Thank you!! > SJ > > Sarah Jane Cox > User Interaction Designer > User Experience Design Team > > Red Hat, Inc. > <http://www.redhat.com/about/whoisredhat/redhatstories.html?intcmp=70160000000TB9vAAG&;> > > > _______________________________________________ > Patternfly mailing list > Patternfly@redhat.com <mailto:Patternfly@redhat.com> > https://www.redhat.com/mailman/listinfo/patternfly > <https://www.redhat.com/mailman/listinfo/patternfly> > > > > > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gsher...@redhat.com <mailto:gsher...@redhat.com> > > > > > -- > Greg Sheremeta, MBA > Red Hat, Inc. > Sr. Software Engineer > gsher...@redhat.com <mailto:gsher...@redhat.com> > _______________________________________________ > Patternfly mailing list > Patternfly@redhat.com <mailto:Patternfly@redhat.com> > https://www.redhat.com/mailman/listinfo/patternfly > <https://www.redhat.com/mailman/listinfo/patternfly> Gabriel Cardoso UX designer @ Red Hat
_______________________________________________ Patternfly mailing list Patternfly@redhat.com https://www.redhat.com/mailman/listinfo/patternfly
