so I just added a Unit-Test that will be run on every example. As usually
problems in the recent past seem to have shown their effect on the examples
most prominently, I have setup a test to check for the SWF and WAR binaries of
each of the examples. This doesn't check if the built SWFs and WARs actually
work, but it detects if they are there and are not empty. I guess as time goes
by we can extend that test to do more detailed checks.
Von: Harbs <harbs.li...@gmail.com>
Gesendet: Donnerstag, 13. Oktober 2016 11:05:04
Betreff: Re: [FlexJS] super method calls broken?
We finally managed to get our project to build by extracting the js files from
the SWC and copying them to where the JS files used to be in the nightly which
we are building against.
That’s a pretty poor work-around. We need instructions on how to get the new
SWCs to work in Flash Builder.
On Oct 13, 2016, at 11:24 AM, Harbs <harbs.li...@gmail.com> wrote:
> It doesn’t “just work”. We’re having a lot of trouble figuring out everything
> that changed.
> This is really frustrating. We’ve wasted a couple of days chasing our tails
> dues to things changing.
> I don’t see any js files being generated in the latest version of develop. I
> know there as some discussion about changing the JS SWCs for easier use of
> libraries. Did that change using the Framework? We have scripts which copy
> updated asjs files to use while we’re developing, but they don’t seem to work
> Right now, we cannot get anything done because we can’t get asjs to compile
> and work right… :-(
> On Oct 13, 2016, at 9:21 AM, Alex Harui <aha...@adobe.com> wrote:
>> On 10/12/16, 11:12 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>> I obviously have not been following well enough.
>>> What was the reason for this change?
>> Lizhi found that the previous way of accessing the super setter or getter
>> was significantly slower.
>> But if everything was compiled with the same version of the compiler, it
>> should "just work".