royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Royale AMF not working on SWF side
Date Tue, 02 Oct 2018 16:20:33 GMT
Hi Carlos,

It is fine to have two different examples.  I don't really care what they are called.  Please
make sure the Jewel version does not output SWF so it is clear there are no expectations that
the SWF version will work correctly.

Unless you or other volunteers have the time to get Jewel to work in SWF (I did get some functionality
working so it didn't just crash), any time you want to add Jewel to an example it will be
better to fork it and change the build configuration so it no longer outputs SWF.


´╗┐On 10/2/18, 12:56 AM, "Carlos Rovira" <> wrote:

    Hi Alex,
    I think we should duplicate the example so we can have a Basic version and
    a Jewel version. We're publishing examples on social networks and good
    looking interface in crucial. So if we want both things we only can fork
    and have *RemoteObjectAMFTest* and *RemoteObjectAMFTestJewel* or
    *RemoteObjectAMFTest* and *RemoteObjectAMFTestBasic*
    Maybe the later is better since we published the other name as the one that
    uses the good looking interface
    El mar., 2 oct. 2018 a las 2:55, Alex Harui (<>)
    > At some point the RemoteObjectAMFTest broke for SWF.  This is rather
    > annoying as it was a good test bed for debugging the compiler output and
    > comparing the JS code to the SWF code.  One thing that broke it was
    > upgrading the UI to use Jewel components because Jewel isn't working that
    > well in SWF.  Our examples should work on both SWF and JS with a few
    > exceptions where the app was designed for JS only, like MDL examples.  I'm
    > tempted to rip the Jewel components out of this example and go back to
    > Basic.
    > -Alex
    Carlos Rovira;;sdata=iLNMMNxKbreKppRqugiCEuEt8d7pslxFq77ntG%2FlgiI%3D&amp;reserved=0

View raw message