Ok, so for now, I'll go with Basic inheritance and will follow naming conventions. Then we can have a Jewel-Express set...
thanks for your advice Carlos 2018-03-02 21:19 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>: > The reason for a separate Button vs TextButton is that there are (or will > be) lots of buttons that never have text so there is no point to creating > text elements/nodes for them. Such as the up/down in NumericStepper, > play/record/pause in Video/Audio components, bold/italic/underline in a > Rich Text Editor. In the Jewel set and for Basic, you are welcome to > propose different names if you think that Button really should have text > support and, maybe, a GraphicOnlyButton should be the base for non-text > Buttons. The names don't matter much to me. The PAYG pattern does matter. > > In Express, there can be a single Button that has text and image support > built-in. > > And if we do emulations of mx:Button and s:Button, those will have text > support built-in. And using Jewel for the default look there would > probably be a good thing. > > My 2 cents, > -Alex > > On 3/2/18, 11:48 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote: > > >Hi, > > > >let me know what do you think about : > > > >* Should Button in Jewel UI Set be named as "Button" or "TextButton"? > >(I see more natural a "Button" that a "TextButton") > > > > > >* Should the main Button in Jewel UI Set inherit from TextButton in > >"Basic" > >or "Express"? > >(that means to have "enabled", "toolTip"...) > > > > > >responses to some of this question could be interpreted or applied to more > >Jewel components and how to deal with it as I create them > > > >Thanks > > > > > >-- > >Carlos Rovira > >https://na01.safelinks.protection.outlook.com/?url= > http%3A%2F%2Fabout.me%2 > >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com% > 7C28c42f8bcea94c1779f708d5 > >80769af2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > 7C636556169279454673&s > >data=uDCo5Tc34xNdnWtmFYSv2PDHgOXsvberO2TvHZyPVaw%3D&reserved=0 > > -- Carlos Rovira http://about.me/carlosrovira
