Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of olegsivokon@gmail.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CBAB3173.3EFB1%aharui@adobe.com>
References: 
 <CAJQBtgm-XEbmNuO0sj3TDzE80OXsdpkC7a9yLQcL_3nZkbOvmA@mail.gmail.com>
	<CBAB3173.3EFB1%aharui@adobe.com>
Date: Wed, 11 Apr 2012 23:39:34 +0300
Message-ID: 
 <CAJQBtgnwGWC3u_PuJY+KjK_o0EV5MyrcNwLFzoSL=7HaRSBMPQ@mail.gmail.com>
Subject: Re: Framework: what do I need to do to initialize styles
From: Left Right <olegsivokon@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=14dae9340f83b7069304bd6d3c2e

--14dae9340f83b7069304bd6d3c2e
Content-Type: text/plain; charset=ISO-8859-1

> Registering the CSSStyleDeclaration in a SystemManagerImpl
I think you meant StyleManagerImpl (style, not system), right? If so, how
do I tell if it's registered? It does too many things you could call
"register".

Below are things that "register" something:
registerInheritingStyle
registerSizeInvalidatingStyle
registerParentSizeInvalidatingStyle
registerParentDisplayListInvalidatingStyle
registerColorName

and things related to loading (and possibly registering)

loadStyleDeclarations
loadStyleDeclarations2

However, of the register* functions none does anything important - they
could be easily combined into one function that simply puts a style name
into hash - they don't do anything beyond that. I think I tried calling all
of them with arguments I could imagine they might take.

load* functions seem to be related to the situation when style declarations
are loaded from elsewhere. I hoped they would help, but they outsource all
real work elsewhere, and then from that elsewhere it goes elsewhere else
few times, and it ends nowhere (? I can't find what they actually do).

So, I'm afraid to conclude none of this functions actually binds the styles
tree to the display list (this is absolutely a miracle to me - I've no idea
how it happens today. It used to be simpler in Flex 3).

> component look up
What do you mean when you say "look up"?... can you be more specific? The
area of source code related to styles is extremely lengthy and lacking
direction there are too many classes involved, and, unfortunately,
components themselves play a very minor role in the process... When
component gets the style through getStyle() they finds some of it, but,
possibly, not all of it, they only find _skin_ if I set it by hand,
otherwise they dont, but I can't set skins to all part of the component.

This is roughly what happens:

component.setStyle("skinClass", someClass);
component.getStyle("skinClass"); // undefined

Now, I can make a particular component find it's skin by calling
component.styleChanged("skinClass"); but this doesn't help child components
find their skins. I.e. there's a label in the button - so while the button
finds it's styles, the label doesn't (and I can't call styleChanged on it).

--14dae9340f83b7069304bd6d3c2e--