I started my framework extending all Royale components that I need and adding a lot of properties (Flex style). Now I'm decoupling all this properties as beads (Royale style) on my own framework and I identify a few ones that could be on the Royale Framework because are so generic. For example Position and DataGridSort are two beads that I don't need any more to have on my own code and use directly from the Royale Framework.
Yes, font style is on a very gray area. Ususally defineded a css global level but there is a few use cases when we need to override the global style behaviour. On this place, I prefer to use a bead instead of working with style = .... But I understand and use my own bead. "finally nor related to this: for percentage width and height you don't need to write percentageWidth="100", you can do width="100%"" Humm. In Flex world I always did width="100%" but here I saw the percentageWidth property and I thought that it's the right way. Why we have this redundante property on the first place ? Carlos Rovira <[email protected]> escreveu no dia sábado, 12/09/2020 à(s) 15:54: > Hi, > > ok, we don't have any bead for font styling, but while padding or > positioning are things that is usual people tune in mxml or as3, font > changes used to happen at CSS level most of the time. Also, as we > separate MVC parts, we should try to separate views from styles (CSS) and > maybe in some cases skin (as we did in Flex 4 days). So adding as3 code to > mix in mxml font styling (or other font things) seems to me not the way to > go when organizing code in a final app (other things are quick examples) > > finally nor related to this: for percentage width and height you don't need > to write percentageWidth="100", you can do width="100%" > > El sáb., 12 sept. 2020 a las 16:42, Hugo Ferreira (<[email protected] > >) > escribió: > > > I'm talking in something like this: > > > > Bead: > > package pt.solidsoft.framework.components.beads > > { > > import org.apache.royale.core.IBead; > > import org.apache.royale.core.IStrand; > > import org.apache.royale.core.UIBase; > > > > public class FontItalic implements IBead > > { > > public function set strand(value:IStrand):void > > { > > (value as UIBase).style = "font-style: italic"; > > } > > } > > } > > > > Usage: > > ... > > <c:Label text="Italic text sample"> > > <c:beads> > > <fi:FontItalic/> > > </c:beads> > > </c:Label> > > ... > > > > The same for bold and font size OR a font bead > > > > Carlos Rovira <[email protected]> escreveu no dia sexta, > 11/09/2020 > > à(s) 19:08: > > > > > Ok, I thought you were talking about font-face and so on. > > > You have SizeControl and TextAlign beads, but I must say I want to > update > > > Sizecontrol a bit since sizes have changed a bit and that need to be > > > adjusted. > > > > > > El vie., 11 sept. 2020 a las 20:02, Hugo Ferreira (< > > [email protected] > > > >) > > > escribió: > > > > > > > Usually, the application has a default style defined globally thus > css, > > > etc > > > > ... but sometimes there are particular use cases where you need a > bold, > > > > italic or even different font size. > > > > A bead should not be an opition ? > > > > > > > > Carlos Rovira <[email protected]> escreveu no dia sexta, > > > 11/09/2020 > > > > à(s) 18:31: > > > > > > > > > No. that is usually done vía CSS or in AS3/MXML vía style property > or > > > > > fx:Style tag. > > > > > > > > > > > > > > > El vie., 11 sept. 2020 a las 18:29, Hugo Ferreira (< > > > > [email protected] > > > > > >) > > > > > escribió: > > > > > > > > > > > There is already a bead for color, font size and font style ? > > > > > > > > > > > > > > > > > > > > > -- > > > > > Carlos Rovira > > > > > http://about.me/carlosrovira > > > > > > > > > > > > > > > > > > -- > > > Carlos Rovira > > > http://about.me/carlosrovira > > > > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
