On 11/5/14, 12:49 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>I don't see how this would be a blocker. The functionality is all there, >the display is just a bit off on a few examples and >that probably only shows on specific instances. If I were RM, I'd label >this 'minor', file a JIRA and move on with the release. The Ardisia example sizing problem feels like a SecurityDomain issue. After you force a resize with the divided box, the app scales down to fit instead of resizing. Third-party content may not size correctly unless “import loaded” which I don’t think is the default. Does TDF try to do that? A grep of the source didn’t turn up any use of SWFLoader.trustContent or SecurityDomain. And, the third-party content needs a crossdomain.xml that permits it to be import-loaded. TDF and the Ardisia example could also use Marshall Plan techniques instead of giving permissions via crossdomain.xml. Of course, I could be wrong, but that’s been the case when I’ve seen symptoms like this in the past. Since we’re emphasizing third-party content in this release, I’d be tempted to say this is a blocker and we should fix the TDF code that loads third-party content. However, if nobody else thinks it is a blocker and can be fixed later, I’m willing to go along with the crowd. Meanwhile, I got the source package from the builds server and tweaked the approval script to allow it to work without PGP signatures and everything looks fine to me, so I’m good to go otherwise. How many other PMC members have looked at the source package? We need at least one more. And for everyone, especially the non-PMC members, time is running out to go explore http://apacheflexbuild.cloudapp.net:8080/job/flex-utilities_tour-de-flex-re lease/lastSuccessfulBuild/artifact/TourDeFlex/TourDeFlex3/src/index.html and let us know if you see any showstoppers before we finish this release. Thanks, -Alex
