You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Olaf Krueger <ma...@olafkrueger.net> on 2018/01/07 21:33:57 UTC
[Understanding PAYG] Button: Why is there no "text" or "icon" bead
in order to compose a TextButton or IconButton?
Hi,
just for my understanding:
It seems to me that we can't compose a TextButton or an IconButton or a
TextIconButton by adding some beads to Button, something like this [1].
Instead, we have "TextButton" which feels for me a bit like an Express
component.
I just would like to know if I have a wrong understanding of PAYG [1] or if
those suggested beads just not implemented because nobody did it so far.
Thank you!
Olaf
[1]
<js:Button>
<js:beads>
<js:Text value="Test" />
<js:Icon src="/your/image/source/image.png" />
</js:beads>
</js:Button>
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Peter Ent <pe...@adobe.com.INVALID>.
Keep in mind that a Royale Button's base UI element is platform dependent.
On the HTML side, the element is a <button> and there is no view bead to
construct it. TextButtonView is a Flash platform class that makes the
actual UI button with its up/down/over states represented as separate
basic elements.
Button is a tricky one because it is so basic to the platform. In other
components, the base UI element is a <div> (HTML) or a
DisplayObjectContainer (Flash) and then what you actually see and interact
with are its children which are created by view beads. Not really the case
for Button.
‹peter
On 1/7/18, 9:16 PM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>You would add TextButtonView or ImageButtonView. Most Basic top-level
>components are an aggregation of a model and view and often a controller.
>Express aggregates "non-essential" and/or less type-safe beads as well to
>reduce the amount of bead-adding you have to do.
>
>Because the components have a model, the model needs to be PAYG and not
>have slots for data like labels and icons it doesn't need. The most basic
>button on some platforms does not have text or an icon because the visuals
>can be specified in CSS via background-image.
>
>HTH,
>-Alex
>
>On 1/7/18, 1:33 PM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>
>>Hi,
>>just for my understanding:
>>
>>It seems to me that we can't compose a TextButton or an IconButton or a
>>TextIconButton by adding some beads to Button, something like this [1].
>>Instead, we have "TextButton" which feels for me a bit like an Express
>>component.
>>I just would like to know if I have a wrong understanding of PAYG [1] or
>>if
>>those suggested beads just not implemented because nobody did it so far.
>>
>>Thank you!
>>Olaf
>>
>>
>>[1]
>><js:Button>
>> <js:beads>
>> <js:Text value="Test" />
>> <js:Icon src="/your/image/source/image.png" />
>> </js:beads>
>></js:Button>
>>
>>
>>
>>--
>>Sent from:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>y
>>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%
>>7
>>C6b87c66fff6b472d0c4b08d55616630d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%
>>7
>>C0%7C636509576506543643&sdata=DXTepjQ2JQlIO7IwMOtdfL2e30usYh3nMvgKSZ3mluE
>>%
>>3D&reserved=0
>
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Olaf Krueger <ma...@olafkrueger.net>.
Thanks Alex!
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Here's one article that is relevant [1]
[1] https://cwiki.apache.org/confluence/display/FLEX/Creating+Components
On 1/8/18, 11:48 AM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>>We've tried to write up things like this in the FlexJS wiki...
>
>Maybe I've overlooked some articles.
>I just started to move articles to the "FlexJS" category to make sure that
>we don't miss something when we'll move it to Royale...
>
>Thanks,
>Olaf
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C742c3cbcae74434d4f6308d556d0cc7d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636510377141330188&sdata=YlZYxB9WoczVS23472xeFAnGeqXSD3i6wKbwoP33KDQ%
>3D&reserved=0
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Olaf Krueger <ma...@olafkrueger.net>.
>We've tried to write up things like this in the FlexJS wiki...
Maybe I've overlooked some articles.
I just started to move articles to the "FlexJS" category to make sure that
we don't miss something when we'll move it to Royale...
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Alex Harui <ah...@adobe.com.INVALID>.
On 1/8/18, 12:50 AM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>>Because the components have a model, the model needs to be PAYG...
>
>I guess I have to start exploring the asjs source code a bit more soon...
>Is there any kind of documentation how those strands and beads are
>internally works and how they are implemented or which patterns are used?
We've tried to write up things like this in the FlexJS wiki. We are still
in the process of moving this information to Royale repos and updating it.
Volunteers are more than welcome to help.
Thanks,
-Alex
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>Cf9d19318ac754055ef1208d55674e03b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636509982339157503&sdata=1GkL2b5LB7luKj6sfudjkeK0APLLJnfkf4arakHhP0o%
>3D&reserved=0
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Olaf Krueger <ma...@olafkrueger.net>.
>Because the components have a model, the model needs to be PAYG...
I guess I have to start exploring the asjs source code a bit more soon...
Is there any kind of documentation how those strands and beads are
internally works and how they are implemented or which patterns are used?
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: [Understanding PAYG] Button: Why is there no "text" or "icon"
bead in order to compose a TextButton or IconButton?
Posted by Alex Harui <ah...@adobe.com.INVALID>.
You would add TextButtonView or ImageButtonView. Most Basic top-level
components are an aggregation of a model and view and often a controller.
Express aggregates "non-essential" and/or less type-safe beads as well to
reduce the amount of bead-adding you have to do.
Because the components have a model, the model needs to be PAYG and not
have slots for data like labels and icons it doesn't need. The most basic
button on some platforms does not have text or an icon because the visuals
can be specified in CSS via background-image.
HTH,
-Alex
On 1/7/18, 1:33 PM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>Hi,
>just for my understanding:
>
>It seems to me that we can't compose a TextButton or an IconButton or a
>TextIconButton by adding some beads to Button, something like this [1].
>Instead, we have "TextButton" which feels for me a bit like an Express
>component.
>I just would like to know if I have a wrong understanding of PAYG [1] or
>if
>those suggested beads just not implemented because nobody did it so far.
>
>Thank you!
>Olaf
>
>
>[1]
><js:Button>
> <js:beads>
> <js:Text value="Test" />
> <js:Icon src="/your/image/source/image.png" />
> </js:beads>
></js:Button>
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C6b87c66fff6b472d0c4b08d55616630d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636509576506543643&sdata=DXTepjQ2JQlIO7IwMOtdfL2e30usYh3nMvgKSZ3mluE%
>3D&reserved=0