[svn:fx-trunk] 12068: Renaming Border to BorderContainer and BorderSkin to BorderContainerSkin

Question

Revision: 12068
Revision: 12068
Author:   [email protected]
Date:     2009-11-20 15:12:16 -0800 (Fri, 20 Nov 2009)
Log Message:
Renaming Border to BorderContainer and BorderSkin to BorderContainerSkin
Updated the files, stylesheet, manifest file and the basicTest tests.
QE notes: tests need updating
Doc notes: Docs need updating
Bugs: SDK-24300
Reviewer: Glenn
Tests run: checkintests
Is noteworthy for integration: Yes. Tests and tools will be impacted.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24300
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/defaults.css
    flex/sdk/trunk/frameworks/projects/spark/src/SparkClasses.as
    flex/sdk/trunk/frameworks/spark-manifest.xml
    flex/sdk/trunk/frameworks/tests/basicTests/BasicTests-config.xml
    flex/sdk/trunk/frameworks/tests/basicTests/BasicTests.mxml
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/BorderCont ainerExample.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/BorderContainer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/BorderContainerSkin.as
    flex/sdk/trunk/frameworks/tests/basicTests/spark/scripts/BorderContainerTestScript.mxml
    flex/sdk/trunk/frameworks/tests/basicTests/spark/views/BorderContainerTests.mxml
Removed Paths:
    flex/sdk/trunk/frameworks/projects/spark/asdoc/en_US/spark/components/examples/BorderExam ple.mxml
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Border.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/BorderSkin.as
    flex/sdk/trunk/frameworks/tests/basicTests/spark/scripts/BorderTestScript.mxml
    flex/sdk/trunk/frameworks/tests/basicTests/spark/views/BorderTests.mxml

Answer 1

We have also expierenced the same problem, or similiar even.
After reading the docs on the opensource website
http://opensource.adobe.com/wiki/display/flexsdk/Per-Module+Style+Management
you will find that there is a flag you can set on the compiler arguments as follows:
-isolate-styles=false
by doing this, i think this allows the modules to work as before, inheriting the styles by default from the application.
There seems to be a new way of using the StyleManager in the current release of Flex 4.
Let me know if this helps.
!Sharif