Re: Migrating Enterprise Flex Application

[Alex Harui]

There is org.apache.royale.utils.ObjectMap instead of Dictionary, but it may 
not work correctly on IE11.

There is org.apache.royale.reflection.getQualifiedClassName and 
getQualifiedSuperclassName

There is org.apache.royale.textLayout instead of flashx.textLayout.

There is org.apache.royale.utils.BinaryData instead of ByteArray.  There is an 
IDataInput/iDataOutput but I think it needs refactoring.

If you don't want to port your flash.xml to E4x, you could write an emulation 
for it.

HTH,
-Alex

On 7/24/18, 5:07 AM, "Alina Kazi" <alina.k...@d-bz.com> wrote:

    Hi chembali,
    
    Like org.apache.royale.utils.Timer  instead of flash.utils.Timer  ,
    org.apache.royale.utils.Proxy instead of flash.utils.Proxy are API's
    available in different Projects(like Core)
    You can use them, If these classes fulfill your requirement  otherwise make
    mx emulations for them.
    
    You can use E4x instead of flash.xml
    
    Thanks,
    Alina Kazi
    
    -----Original Message-----
    From: chembali [mailto:chemb...@hotmail.com] 
    Sent: Tuesday, July 24, 2018 3:09 PM
    To: dev@royale.apache.org
    Subject: Re: Migrating Enterprise Flex Application
    
    How do I migrate the flash.util, flash.xml, flashx.text etc APIs in my
    existing application?
    
    
    
    --
    Sent from: 
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7Ca2127a412f674c94167a08d5f15e115f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636680308701005597&amp;sdata=4tyutKcCpsdLZRjAdB%2FI%2FRYCh08JCi9o3i0QtsfsHZ0%3D&amp;reserved=0