You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2018/04/21 07:04:17 UTC
Jewel Button and TextField
Hi,
thinking in release 0.9.3 I believe I could make some changes to make the
Jewel API more user ready, since release is what we expect final users will
try and it's a good time to make this kind of changes. Regarding Jewel I
see the following issues:
* Button: I think people will find more familiar to deal with <j:Button/>
than with <j:TextButton>. Maybe in Basic Button can have more sense, but I
don't see it in Jewel, so I thinking in removing actual Button and rename
TextButton to Button. After 0.9.3 I expect to complete Button with more
needs like ability to handle icons (I suppose this will be a bead), make an
"outline" style, and handle sizes (large, medium, small,...). If you think
in some more needs let me know to add to this TODO (but after 0.9.3)
* TextField: I find "TextInput" will be a better name, since that will
match flex name and I think is more appropiate.
I think this will improve people coming from flex, and make the API more
friendly for users
--
Carlos Rovira
http://about.me/carlosrovira
Re: Jewel Button and TextField
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Yes, will look at Alex's fixes tonight.
Thanks,
Om
On Tue, Apr 24, 2018 at 4:29 PM, Carlos Rovira <ca...@apache.org>
wrote:
> Om, Alex,
>
> I'm done for 0.9.3 with this changes, are you still planning on make a
> release this days?
>
> closing for today.
>
> thanks
>
> Carlos
>
> 2018-04-24 17:19 GMT+02:00 Carlos Rovira <ca...@apache.org>:
>
> > Hi,
> >
> > I'm going to take advantage that the release has not yet been created to
> > make this refactor so 0.9.3 comes with this names correctly, hope to have
> > it in the next few hours
> >
> >
> > 2018-04-21 9:04 GMT+02:00 Carlos Rovira <ca...@apache.org>:
> >
> >> Hi,
> >>
> >> thinking in release 0.9.3 I believe I could make some changes to make
> the
> >> Jewel API more user ready, since release is what we expect final users
> will
> >> try and it's a good time to make this kind of changes. Regarding Jewel I
> >> see the following issues:
> >>
> >> * Button: I think people will find more familiar to deal with
> <j:Button/>
> >> than with <j:TextButton>. Maybe in Basic Button can have more sense,
> but I
> >> don't see it in Jewel, so I thinking in removing actual Button and
> rename
> >> TextButton to Button. After 0.9.3 I expect to complete Button with more
> >> needs like ability to handle icons (I suppose this will be a bead),
> make an
> >> "outline" style, and handle sizes (large, medium, small,...). If you
> think
> >> in some more needs let me know to add to this TODO (but after 0.9.3)
> >>
> >> * TextField: I find "TextInput" will be a better name, since that will
> >> match flex name and I think is more appropiate.
> >>
> >> I think this will improve people coming from flex, and make the API more
> >> friendly for users
> >>
> >> --
> >> Carlos Rovira
> >> http://about.me/carlosrovira
> >>
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
Re: Jewel Button and TextField
Posted by Carlos Rovira <ca...@apache.org>.
Om, Alex,
I'm done for 0.9.3 with this changes, are you still planning on make a
release this days?
closing for today.
thanks
Carlos
2018-04-24 17:19 GMT+02:00 Carlos Rovira <ca...@apache.org>:
> Hi,
>
> I'm going to take advantage that the release has not yet been created to
> make this refactor so 0.9.3 comes with this names correctly, hope to have
> it in the next few hours
>
>
> 2018-04-21 9:04 GMT+02:00 Carlos Rovira <ca...@apache.org>:
>
>> Hi,
>>
>> thinking in release 0.9.3 I believe I could make some changes to make the
>> Jewel API more user ready, since release is what we expect final users will
>> try and it's a good time to make this kind of changes. Regarding Jewel I
>> see the following issues:
>>
>> * Button: I think people will find more familiar to deal with <j:Button/>
>> than with <j:TextButton>. Maybe in Basic Button can have more sense, but I
>> don't see it in Jewel, so I thinking in removing actual Button and rename
>> TextButton to Button. After 0.9.3 I expect to complete Button with more
>> needs like ability to handle icons (I suppose this will be a bead), make an
>> "outline" style, and handle sizes (large, medium, small,...). If you think
>> in some more needs let me know to add to this TODO (but after 0.9.3)
>>
>> * TextField: I find "TextInput" will be a better name, since that will
>> match flex name and I think is more appropiate.
>>
>> I think this will improve people coming from flex, and make the API more
>> friendly for users
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Jewel Button and TextField
Posted by Carlos Rovira <ca...@apache.org>.
Hi,
I'm going to take advantage that the release has not yet been created to
make this refactor so 0.9.3 comes with this names correctly, hope to have
it in the next few hours
2018-04-21 9:04 GMT+02:00 Carlos Rovira <ca...@apache.org>:
> Hi,
>
> thinking in release 0.9.3 I believe I could make some changes to make the
> Jewel API more user ready, since release is what we expect final users will
> try and it's a good time to make this kind of changes. Regarding Jewel I
> see the following issues:
>
> * Button: I think people will find more familiar to deal with <j:Button/>
> than with <j:TextButton>. Maybe in Basic Button can have more sense, but I
> don't see it in Jewel, so I thinking in removing actual Button and rename
> TextButton to Button. After 0.9.3 I expect to complete Button with more
> needs like ability to handle icons (I suppose this will be a bead), make an
> "outline" style, and handle sizes (large, medium, small,...). If you think
> in some more needs let me know to add to this TODO (but after 0.9.3)
>
> * TextField: I find "TextInput" will be a better name, since that will
> match flex name and I think is more appropiate.
>
> I think this will improve people coming from flex, and make the API more
> friendly for users
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
--
Carlos Rovira
http://about.me/carlosrovira