Return-Path: 
 <dev-return-27668-apmail-flex-dev-archive=flex.apache.org@flex.apache.org>
X-Original-To: apmail-flex-dev-archive@www.apache.org
Delivered-To: apmail-flex-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 0224FC97D
	for <apmail-flex-dev-archive@www.apache.org>;
 Fri, 21 Jun 2013 16:58:36 +0000 (UTC)
Received: (qmail 18880 invoked by uid 500); 21 Jun 2013 16:58:35 -0000
Delivered-To: apmail-flex-dev-archive@flex.apache.org
Received: (qmail 18863 invoked by uid 500); 21 Jun 2013 16:58:32 -0000
Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@flex.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@flex.apache.org>
List-Post: <mailto:dev@flex.apache.org>
List-Id: <dev.flex.apache.org>
Reply-To: dev@flex.apache.org
Delivered-To: mailing list dev@flex.apache.org
Received: (qmail 18855 invoked by uid 99); 21 Jun 2013 16:58:32 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 16:58:32 +0000
X-ASF-Spam-Status: No, hits=-2.3 required=5.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.35 as permitted sender)
Received: from [64.18.1.35] (HELO exprod6og115.obsmtp.com) (64.18.1.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 16:58:23 +0000
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by
 exprod6ob115.postini.com ([64.18.5.12]) with SMTP
	ID DSNKUcSGGM370HUEdgeYmfqZEsQeymYojIdv@postini.com;
 Fri, 21 Jun 2013 09:58:03 PDT
Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com
 [153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
 r5LGvxAI025411
	for <dev@flex.apache.org>; Fri, 21 Jun 2013 09:57:59 -0700 (PDT)
Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
 r5LGvw6A011762
	for <dev@flex.apache.org>; Fri, 21 Jun 2013 09:57:58 -0700 (PDT)
Received: from NAMBX02.corp.adobe.com ([10.8.127.96]) by
 nacas02.corp.adobe.com ([10.8.189.100]) with mapi; Fri, 21 Jun 2013 09:57:58
 -0700
From: Alex Harui <aharui@adobe.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Date: Fri, 21 Jun 2013 09:57:56 -0700
Subject: Re: Adding support for CSS background and borders
Thread-Topic: Adding support for CSS background and borders
Thread-Index: Ac5uoHseeLnW6puKSeSGr9GIJpSIEw==
Message-ID: <CDE9D356.C253%aharui@adobe.com>
In-Reply-To: 
 <CANcBHEAaZduEoFX5c0pQHdBMZYeP01pQTGD48yaPMdPU3kG9Mg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Checked: Checked by ClamAV on apache.org

Seems like you could create a CSSBackground component that subclasses Skin
that becomes the base class of every skin of your theme.  Since most
components don't have CSS background styles set, the code wouldn't do much
unless needed.

One possible gotcha would be any components who derive their size from the
background-image as these would probably be loaded externally and not
available at measure time.

On 6/21/13 3:18 AM, "flexcapacitor@gmail.com" <flexcapacitor@gmail.com>
wrote:

>In HTML and CSS you can specify the background and border on any container
>and I think on any control. So for a button or div you can do this:
>
><input style=3D"background:#ffffff url('img_tree.png') no-repeat right
>top;border:border:5px solid red;border-right-style:none;"
>type=3D"button"/>
>
>
>You can also point the background to an SVG file with
>url("button-up.svg").
>
>In my opinion, this is one area where Flex is sorely lacking. Is there a
>way to add support for this on every control? I know Border Container was
>created as an alternative to Group because of performance reasons. But is
>there a way to write it so that if it's not used it won't affect
>performance?