> On 10/25/13 3:43 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >>Next I got really bold and decided to try a bit of Mustella: >>'./mini_run.sh tests/components/Label'. This got me 2 compile errors >>on a mysterious character in 2 of the AS files. > Yeah, MXMLC lets a particular Unicode linebreak character through that > Falcon currently doesn't. Because FB doesn't show you that linebreak, I > decided not to try to make Falcon handle that, but we certainly could.
Yes, some were linebreaks, that look like they came from 'older' FB or other IDE - since it didn't occur in my major project that was brought through multiple versions; but they did occur in code I downloaded for a recent addition. But they weren't all linebreaks. Some were at the start of a line (after the whitespace) and reported like this: ?if (this) { ^ Where the question mark turned out to be an 'invisible' character. >>didn't move when I deleted it), 255 tests ran, most of which failed. >>The failures were mostly bitmap compares, so I ran -createImages. This >>got rid of most failures: 240 tests pass, 15 fail. From a very quick >>look at the bitmaps, it looks to me that the 'bad' images are sharper >>than the baselines. > There is no embedded font support in Falcon at this time, so running > Mustella is guaranteed to generate a lot of failures. I suppose that some > energetic person could make a branch that doesn't have the embedded font > libraries and use MXMLC and generate all new baselines and fix > AssertPropertyValues that expect numbers based on embedded font metrics > and then prove that Falcon can run and pass all of these tests, but maybe > it would be better to either add in the ability to handle the Adobe font > libraries, or write an embedded font library that can be used both for > Falcon and for MXMLC so we can remove another dependency on Adobe > proprietary stuff. Ok, that first option sounds worth a try; not to entire thing, that would have to be automated somehow, but a proof of concept, like with the Label I was looking at. How do I remove embedded font support? Just download the SDK and answer 'no' to a question during the build, or do I need to manually remove/change stuff? >>I think this is all very impressive, and I think with a little more >>work, and A LOT MORE TESTING, we are getting close... > Agreed. Not sure how to do that "more testing" other than having folks > try it. Well, making sure Mustella runs 'fairly' and passes would be 'a lot' of testing... But yes, we should work towards allowing people to play with this... Maybe create something that can overlay Falcon over an otherwise fully build SDK? > And so next for me is BasicTests with the new MXML codegen, then getting > my internal customer's huge app to get off the ground with the new MXML > codegen, and then, getting the huge app to cross-compile with FalconJX. I must have missed something... Is there another new MXML codegen? Something that's currently not included in Falcon? > I also want to teach Falcon to pick up FB project properties, and there > are some other Falcon bugs that need fixing. Not sure what order I'm > going to work on this stuff. > > Any and all help is appreciated. Will chip in where I can. First thing will be looking into Mustella, if you can explain the 'remove embedded font support' thing, please. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl