search

microsoft / xaml-standard

XAML Standard : a set of principles that drive XAML dialect alignment
Other
805 stars 50 forks source link

Add Chronometer control #173

Open insinfo opened 7 years ago

insinfo commented 7 years ago

chronometer 1 chronometer 4 chronometer 3 chronometer 2

crutkas commented 7 years ago

@insinfo can you explain a bit why this isn't a custom control and it should be part of the standard? It isn't hard to implement.

insinfo commented 7 years ago

Yes it is true that it is something simple to implement, but we can make life easier for the developer because it is not ready to be used, that is what Google is doing.

crutkas commented 7 years ago

@insinfo what I saw was a variation of a text block for their implementation. What your showing above is a full blown UX. Is the ask here for parity with android?

https://developer.android.com/reference/android/widget/Chronometer.html

birbilis commented 7 years ago

In my view commonly needed controls should be modelled (PME - Property/Method/Event) in such a standard. MS seems to focus on just P and E here btw

crutkas commented 7 years ago

@birbilis. Start proposing methods on stuff you feel is needed. I am trying to help guide the conversation on important stuff versus variants of the same control that could be included in the base.

birbilis commented 7 years ago

What I mean is that common components' PME models should be defined using say C# interfaces (and interface-only [even multiple] inheritance) probably in a separate repo if that's out of scope

mossyblog commented 7 years ago

Why is this a still open issue?