On 10/18/16, 12:32 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi, >thanks Harbs, I cherry piclked the Yishay commit in my branch, and will >play with it. > >btw, I think the visible property, although maybe could be only one >implementation, seems to be the same philosophy right? >Not all buttons should be hidden, so following the criteria, seems a code >to aggregate as a bead. Don't want to originate a discussion about this, >but only one to expose that point. Yes, to be completely consistent, we would break out visible, x, y, width, height and even the strand into beads or separable objects. I don't know if it is worth it from a size and performance perspective, which is why I baked them in. The implementation of visible in each platform is much smaller than the bead. Really it is the different ways folks want to implement enable/disable that made me want it to be in a bead. It doesn't have to be in a bead for your MDL button. I only want the basic button to have it broken out. Folks are allowed to aggregate any set of beads into a default Button for their component set. -Alex
