Not so easy, many things to do but, yes, too long time on my list, I'll see
that this week
-----Message d'origine-----
From: Justin Mclean (JIRA)
Sent: Monday, March 11, 2013 1:33 AM
To: dev@flex.apache.org
Subject: [jira] [Updated] (FLEX-33386) Style Declaration Matching Tuning -
Inlining
[
https://issues.apache.org/jira/browse/FLEX-33386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-33386:
---------------------------------
Labels: Performance easyfix (was: Performance)
Style Declaration Matching Tuning - Inlining
--------------------------------------------
Key: FLEX-33386
URL: https://issues.apache.org/jira/browse/FLEX-33386
Project: Apache Flex
Issue Type: Improvement
Components: Styles
Reporter: RJ Camarillo
Assignee: Frédéric THOMAS
Priority: Minor
Labels: Performance, easyfix
Fix For: Adobe Flex SDK Next
Attachments: mx.styles - inlined.zip
One of the most executed calls during the lifetime of a Flex UIComponent
is the matching of style declarations (i.e. state change, component
initialization, etc).
As such, it is one that the community has monkey-patched often in order to
attain speed-ups even for just a little.
This is one of the improvements done to achieve that end. Instead of doing
method calls to the different style classes (i.e. CSSCondition,
CSSSelector, CSSStyleDeclaration), the StyleProtoChain class has been
modified to perform matching inline as much as possible.
The implementation is not perfect and I'm sure it can be improved further
with the help of the bigger community. For example, the
matchingDecls.sortOn("selectorIndex", Array.NUMERIC) call could be improve
to use one of the faster sort algorithms out there. There are also some
methods calls that are not inlined.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
