Do you mean that in Donut we'll see Calendar application rewritten and its look closer to the current Contacts style?
Actually, I thought about it a little bit. It seems to me that Contacts form is more convenient in case when you have many optional/ multiple (I mean you may have from 0 to many values) fields. However, in case when when all (or the most of) fields are mandatory and single (like we have in case with event), those plus/minus buttons look redundant. So I hardly imagine Event form in the current Contact form style. On May 29, 8:11 pm, Romain Guy <[email protected]> wrote: > Follow what Contacts does :) > > On Fri, May 29, 2009 at 9:05 AM, Andriy Zakharchuk > > > > <[email protected]> wrote: > > > Hello All, > > > I know there were a lot of topics like this created earlier, but most > > of them haven't got any response. I'd like to raise this topic once > > again and probably ask more concrete questions. > > > I need to create several forms which allow users entering data. Form > > allows entering text (EditText), numbers (EditText with appropriate > > input method), boolean fields (CheckBox), choose some options from a > > list (Spinner) etc. From my previous UI development experience I > > learned that users expect similar behaviour/loo'n'feel in similar > > situations. > > > I tried to figure out form designing guidelines looking at built-in > > Android applications. There were two applications which have forms: > > Contacts and Calendar. Unfortunately I was unable to define any rules > > which are common for both applications. > > > From the layout point of view, Contacts uses ListView-like form which > > looks like a settings form, whereas Calendar uses traditional form > > with labels and input controls. > > > Choice of an option from a list is implemented differently: > > - Contacts - Ringtone field - is implemented as a ListPreference > > widget; > > - Calendar - Repetition field - is implemented as a TextView (label) + > > Spinner. > > > Boolean field entry is implemented differently: > > - Contacts - Incoming calls field - implemented as a > > CheckBoxPreference; > > - Calendar - All day flag - implemented as a TextView (label) + > > CheckBox. > > > So my question is what approach should I use when designing forms for > > data entry application? Should my forms look like an Event form or > > like a Contact form? > > > It would be great if somebody from Android team read this message. I > > see that Android UI evolves, so probably you can give us (developers) > > some hint about further (planned) UI modifications which help us to > > design consistent UI. > > > Thank you in advance. > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
