Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

>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:

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

On 1/8/18, 12:50 AM, "Olaf Krueger" 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

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

Keep in mind that a Royale Button's base UI element is platform dependent. On the HTML side, the element is a 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.

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

>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

Re: [Understanding PAYG] Button: Why is there no "text" or "icon" bead in order to compose a TextButton or IconButton?

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