Personally, I don't think that providing any possible aggregations/specializations of existing components would be an improvement for the framework.
However, the framework provide a BorderContainer component that does a similar thing (except for the fact that it is also a container): provide styles to control skin behavior. As a side note, even if not strictly related, this make me think about a limitation see with current Spark skinning implementation: the relation between skins and styles. Sometime it would be useful to "configure" some skin visual properties directly from MXML using a style, but style must be declared by the host component (even if inherited by the skin, think about "borderColor" and "borderAlpha"). This force you to subclass and/or create a strong dependency between component and skin (leading to "theme warnings", such as "the style XXX could only be used with theme YYY"). My current workaround is to use CSS rules to assign styles directly to skin classes, but its far from perfect.. 2013/2/27 Harbs <gavha...@gmail.com> > So you think there should be a separate H/VRule and H/VRuleSkin? > > Is it really necessary to have it fully skinnable? > > I was just thinking of allowing to specify an alternate stroke (for > gradients, etc) and allow all the standard filters, etc. > > By default it would have a solid stroke, and you'd just specify the weight > along with the width and height of the component. > > Harbs > > On Feb 27, 2013, at 7:07 PM, Alex Harui wrote: > > > Yep, but the Spark philosophy might lean away from such "intelligence" > and > > styles and head towards skinning. > > > > > > On 2/27/13 8:56 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> > wrote: > > > >> Here is a link to the HRule and VRule. While these are the MX > versions, they > >> do have a good picture that shows what it can do under the sections > "Sizing > >> HRule and VRule controls" > >> > >> > http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7d > >> 96.html > >> > >> -Mark > >> > > > > -- > > Alex Harui > > Flex SDK Team > > Adobe Systems, Inc. > > http://blogs.adobe.com/aharui > > > >
