I’m trying to work on the TLF performance issues, and for some reason I can’t
seem to get trace statements to work when I build textLayout.swc. I tried
editing both the flex-config.xml file in flex-sdk/frameworks as well as the
config.xml file in flex-tlf. Nothing seems to help.
Suggestions?
H
http://matrix3d.github.io/assets/html5/flexjsstage3d/bin/js-release/indexg.html
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/spriteflexjs-support-bitmapfill-tp50535.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I got it to work. It looks like “clean” in FB was not working. Manually
deleting the bin-debug folder is necessary for some reason...
On Dec 7, 2015, at 12:19 PM, Harbs wrote:
> I’m trying to work on the TLF performance issues, and for some reason I can’t
> seem to get trace statements to work
Well if we are moving some of the stuff around, but want to allow people to
still find it... Should we make the utils and AS3commons its own namespace /
library to make it an easier transition for people? Then they would just have
to add a new header property to access the previous components
OK. I’m working on this, and I just added a comment to the JIRA with my
preliminary observations. Kind of interesting...
I’m going to need to find the source of the old TLF to compare. I don’t want to
use 4.9.1 because that code just had a band-aid. I assume Adobe's 4.6 code was
working correct
On 24/11/15 19:00, OmPrakash Muppirala wrote:
And do you think I can close this issue as fixed for now?
The Mustella tests are still failing...
Tom
It looks like I don’t need 4.6. There’s a 3.0 branch in the Git repo which
seems to have ti working correctly.
On Dec 7, 2015, at 3:19 PM, Harbs wrote:
> OK. I’m working on this, and I just added a comment to the JIRA with my
> preliminary observations. Kind of interesting...
>
> I’m going to
Concerns like these were also brought up in the discuss and vote in
May/June 2013. We could run another discuss and vote. I noticed in the
prior vote that more than one non-binding vote was cast by folks who are
either now committers and/or PMC members. And it could be that the few
folks who did
On 12/7/15, 5:33 AM, "Tom Chiverton" wrote:
>On 24/11/15 19:00, OmPrakash Muppirala wrote:
>> And do you think I can close this issue as fixed for now?
>
>The Mustella tests are still failing...
My understanding of the situation is:
1) I'm still not sure we have the right solution in the repo
To me it makes to have mx labels in the MX charts. If we create some
spark charts, using spark labels would make sense. However you would have to
embed the fonts again. The downside to not embedding the fonts and just using
what your default font is, the tests would show bitmap compare
On 12/7/15, 9:07 AM, "Kessler CTR Mark J"
wrote:
>
>To me it makes to have mx labels in the MX charts. If we create
>some spark charts, using spark labels would make sense. However you
>would have to embed the fonts again. The downside to not embedding the
>fonts and just using what you
flex-sdk_release-candidate - Build #122 - Successful
Changes since last build:
No changes
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/122/.
i thinks it is just a lib.it in the github is good.why put it to flex?
the flex should clear.
if the flex can not use the lib from github,should fixed,it is a bug.
why put some lib in flex?
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/DISCUSS-Adopting-AS
13 matches
Mail list logo
