incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kessler CTR Mark J" <mark.kessler....@usmc.mil>
Subject RE: [Component] Spacer
Date Fri, 21 Dec 2012 14:59:07 GMT
It's not really any different that the MX version, it just felt like it helped to complete
the spark component set.  That and it's only like half a dozen lines or so lol.

-----Original Message-----
From: Jeffry Houser [mailto:jeffry@dot-com-it.com] 
Sent: Friday, December 21, 2012 9:52
To: flex-dev@incubator.apache.org
Subject: Re: [Component] Spacer


  My personal opinion is that the MX Spacer does not need to be 
re-written as a Spark Component.  It won't game any benefit from being 
implemented using the Spark Architecture as it has no visual display.

  Is there a reason the MX Spacer won't work for you?  Would extending 
Rect be more efficient?

On 12/21/2012 9:44 AM, Kessler CTR Mark J wrote:
>     Just curious if we could add a simple component that used to exist in MX but not
in Spark.  The spacer component was just a simple UI extension.  We can do the exact same
thing now with the s:Rect (primitive), but it doesn't have an intuitive name.  I think it
would be nice to add the spacer back in.
>
>
>
> <s:Rect width="100%" />
>
> --Same as--
>
> <s:Spacer width="100%" />
>
>
> Class:
>
> //Declare package.
> package spark.components
> {
>     //Create child class of the Rect class.
>     public class Spacer extends Rect
>     {
>        //----------------------------------------
>        //  Constructor
>        //----------------------------------------
>
>        public function Spacer()
>        {
>           super();
>        }
>
>     }
>
> }
>
>
>
> -Mark


-- 
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust


Mime
View raw message