[forms-devel] forms-devel Digest, Vol 4, Issue 2
rina you
rina6350.you at gmail.com
Wed Aug 17 07:18:57 UTC 2016
Hello Brian,
Thank you for your reply.
Your opinion about event name is right.
The event name of CheckBox should be 'Checked'.
About the states of IsChecked, if CheckBox isn't checked, the value of
IsChecked will be false.
Could you share the reason that the IsChecked property should support
nullable value?
Thank you.
Best regards,
- Rina You
2016. 8. 17. 오후 3:32에 "Brian Lagunas" <brian.lagunas at live.com>님이 작성:
> I would name the event Checked, not Clicked. Clicking is not the same as
> checking.
>
>
>
> Will it not support 3 states? If so, the IsChecked property should be a
> Nullable<bool> (bool?)
>
>
>
> *Brian Lagunas*
>
> Senior Product Owner | Infragistics, Inc
>
> www.brianlagunas.com | @brianlagunas
>
>
>
> *From:* forms-devel [mailto:forms-devel-bounces at lists.dot.net] *On Behalf
> Of *rina you
> *Sent:* Wednesday, August 17, 2016 12:09 AM
> *To:* forms-devel at lists.dot.net; Jason Smith <jas at microsoft.com>
> *Subject:* Re: [forms-devel] forms-devel Digest, Vol 4, Issue 2
>
>
>
> Hello,
>
> I'd like to share a draft spec for CheckBox in the mailing list.
> And then, I will make a PR for CheckBox based on other opinions in this
> mailing list.
>
> * The CheckBox will inherit View and IFontElement and have a public
> constructor for initializing a new instance of the CheckBox class.
>
> * The CheckBox will have the following public fields for bindable
> properties:
> - public static readonly BindableProperty FontAttributesProperty :
> Identifies the FontAttributes bindable property.
> - public static readonly BindableProperty FontFamilyProperty :
> Identifies the FontFamily bindable property.
> - public static readonly BindableProperty FontSizeProperty :
> Identifies the FontSize bindable property.
> - public static readonly BindableProperty IsCheckedProperty :
> Identifies the IsChecked bindable property.
> - public static readonly BindableProperty TextProperty :
> Identifies the Text bindable property.
> - public static readonly BindableProperty TextColorProperty :
> Identifies the TextColor bindable property.
>
> * The CheckBox will have the following public properties.
> - public Font FontAttributes : A value that indicates whether the font
> of the checkbox is bold, italic or neither.
> - public String FontFamily : A value that indicates the font family
> which the checkbox font belongs to.
> - public Double FontSize : A value that indicates font size of the
> checkbox.
> - public bool IsChecked : A value that indicates whether this
> checkbox is checked or not.
> - public String Text : A value for the text that is displayed as
> the content of the checkbox.
> - public Color TextColor : A value that indicates the color for the
> text of checkbox.
>
> * The CheckBox will have an event.
> - public event EventHandler Clicked : This event occurs when the checkbox
> is checked.
>
> If you have any opinion about the draft spec for CheckBox, please, could
> you share your opinion?
> I look forward to hearing any opinions about this draft spec.
> Thank you.
>
> Best regards,
>
> - Rina You
>
>
>
> 2016. 8. 16. 오후 7:18에 "rina you" <rina6350.you at gmail.com>님이 작성:
>
> Hello,
>
> I am happy to hear this news from you.
> In this case, should I prepare the PR for CheckBox?
> I look forward to hearing your opinion.
> Thank you.
>
> Best regards,
>
> - Rina You
>
>
>
> 2016. 8. 16. 오후 4:26에 "Jason Smith" <jas at microsoft.com>님이 작성:
>
> In general we are on board with the creation of a general Checkbox
> control. I would love to see an API proposal here in the mailing list J
>
>
>
> *From:* forms-devel [mailto:forms-devel-bounces at lists.dot.net] *On Behalf
> Of *rina you
> *Sent:* Friday, August 12, 2016 12:57 AM
> *To:* forms-devel at lists.dot.net
> *Subject:* Re: [forms-devel] forms-devel Digest, Vol 4, Issue 2
>
>
>
> Hello all and Adam,
>
> Thank you for you opinion.
>
> I agree that the way using ListView you mention can be another way to
> provide a multiple selection of items.
> I also agree that this approach can provide better UX for ListView.
>
> However, how about considering the scenario that the number of item is one
> or two?
> If the number of item is one or two and app user can select one status
> between 'Checked' and 'Unchecked' in each item,
> Should app developer provide this UX with ListView?
> The development process of an app that this UX is provided with ListView
> takes more time than the procedure using a simple checkbox.
> The app should include more code line than an app using a simple checkbox.
>
> As you already know, checkBox have function to indicate two states which
> are 'checked' and 'unchecked' with text
> as well as function to provide multiple selections of items.
> So, checkBox could be useful control for providing user's selection
> between 'checked' and 'unchecked' about one or two items with text.
>
> Also, is this link(https://material.google.com/
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmaterial.google.com%2f&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4Q%2b7aBplhu%2bp8mercu%2b%2bNUx1aIzyNpnbyIsJiFQ%2fNjg%3d>)
> Google Material Design Guidelines you mention on a previous email?
> Actually, it is a little hard to find some opinion that guideline
> specially discourage checkbox.
> Instead, this design guideline describes well that checkbox is one of
> controls for allowing the user to select options.
> I'd like to share two link about checkbox in Google Material Design
> Guidelines.
> - https://material.google.com/components/selection-controls.html#
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmaterial.google.com%2fcomponents%2fselection-controls.html%23&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=uuf%2ferYU9MNszNei%2bznP66uRhu%2fud0LuPvVmV59R3mY%3d>
> - https://material.google.com/components/lists-controls.html#
> <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmaterial.google.com%2fcomponents%2flists-controls.html%23&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=KfVnIYNo1G7rgkZDPT1QhtIEgC8NAxF9wEAl%2fp3MBLU%3d>
> These two link describe definitely how checkbox can be useful for
> providing various UX to user.
>
> Thank you for sharing your opinion about checkbox again.
>
> Best regards,
>
> - Rina You
>
>
>
> 2016. 8. 12. 오후 1:27에 "S.H Choi" <flyofsky at gmail.com>님이 작성:
>
> ---------- 전달된 메일 ----------
> 보낸사람: "Adam Pedley" <adam.pedley at gmail.com>
> 날짜: 2016. 8. 11. 오후 9:15
> 제목: Re: [forms-devel] forms-devel Digest, Vol 4, Issue 2
> 받는사람: <forms-devel at lists.dot.net>
> 참조:
>
> Since Checkboxes are natively a part of Android and UWP, I think it could
> be good to expose them. iOS would probably need a toggle with a different
> image, or a button with a different selected state as I don't know of a
> native checkbox.
>
>
>
> Rina, while checkboxes can be good the specific scenario you mention for
> their use, such as a multiple select of items in a list is normally
> discouraged due to UX issues such as if you are selecting the item or
> ticking the checkbox. For this reason Google Material Design Guidelines
> specifically discourages them and I think other guideline do as well.
>
>
>
> Might I suggest when you select an item in the ListView or list of some
> kind you show a tick next to the item, or highlight the row in the list.
> This approach tends to go over better in a mobile UI and doesn't confuse
> selecting the list row, vs a control in the list.
>
>
>
> On Thu, Aug 11, 2016 at 10:00 PM, <forms-devel-request at lists.dot.net>
> wrote:
>
> Send forms-devel mailing list submissions to
> forms-devel at lists.dot.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.dot.net/mailman/listinfo/forms-devel
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.dot.net%2fmailman%2flistinfo%2fforms-devel&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=COmHaFaHLH2A44ihAEnHe039bjAHJumLWE4VaaBaNEA%3d>
> or, via email, send a message with subject or body 'help' to
> forms-devel-request at lists.dot.net
>
> You can reach the person managing the list at
> forms-devel-owner at lists.dot.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of forms-devel digest..."
>
>
> Today's Topics:
>
> 1. Add a CheckBox (rina you)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 11 Aug 2016 20:31:08 +0900
> From: rina you <rina6350.you at gmail.com>
> To: forms-devel at lists.dot.net
> Subject: [forms-devel] Add a CheckBox
> Message-ID:
> <CAGxJt92CwqbUrTT+2GzONiEWt4Rww6uzcYxd0RmW2gTyB8
> _snw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
> I'd like to add a CheckBox for allowing the user can select multiple
> options in the list.
> And a CheckBox is a specific control that has two states which are
> 'checked' and 'unchecked'.
>
> This CheckBox will have the following properties.
> - FontAttributes : A value that indicate whether the font of the checkbox
> is bold, italic or neither.
> - FontFamily : A value that indicate font family to which the font for
> checkbox text belongs.
> - FontSize : A value that indicate font size of checkbox.
> - IsChecked : A value that indicate whether this checkbox is checked or
> not.
> - Text : A text displayed as the content of the checkbox.
> - TextColor : A value that indicate the color for the text of checkbox.
>
> Also, this CheckBox will have an event.
> - Checked : This event occurs when checkbox is checked.
>
> Just like other controls, the CheckBox is a very common control.
> Xamarin will be able to provide richer function in many application, if
> this control is added on xamarin.
> I will look forward to hearing your opinion.
> Thank you.
>
> Best regard,
>
> Rina You
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.dot.net/pipermail/forms-devel/
> attachments/20160811/1d65b820/attachment-0001.html
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.dot.net%2fpipermail%2fforms-devel%2fattachments%2f20160811%2f1d65b820%2fattachment-0001.html&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=F3ZKhgRVqaAzspFC4Nt3Q%2bjl%2fIguNAF%2btNlflyzq8QY%3d>
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> forms-devel mailing list
> forms-devel at lists.dot.net
> http://lists.dot.net/mailman/listinfo/forms-devel
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.dot.net%2fmailman%2flistinfo%2fforms-devel&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=COmHaFaHLH2A44ihAEnHe039bjAHJumLWE4VaaBaNEA%3d>
>
>
> ------------------------------
>
> End of forms-devel Digest, Vol 4, Issue 2
> *****************************************
>
>
>
>
> _______________________________________________
> forms-devel mailing list
> forms-devel at lists.dot.net
> http://lists.dot.net/mailman/listinfo/forms-devel
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.dot.net%2fmailman%2flistinfo%2fforms-devel&data=01%7c01%7cjas%40microsoft.com%7cb3c1d44ecf3042c9df2308d3c2863d6f%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=COmHaFaHLH2A44ihAEnHe039bjAHJumLWE4VaaBaNEA%3d>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/forms-devel/attachments/20160817/4eeff5be/attachment-0001.html>
More information about the forms-devel
mailing list