In theory, yes, the Royale SWF Compiler can produce Flex SWFs. The SWF Compiler is based on the same code that Adobe uses in the AIR SDK to compile AS to SWFs for AIR. Apache Flex committers added MXML support. We have a unit test that compiles the Apache Flex SDK SWCs.
Might there be bugs? Sure. But the Royale SWF compiler may find errors in your code that the Flex MXMLC did not catch. Trying to get Flash Builder to use a Royale SDK to compile a Flex SWF is a bit tricky because Flash Builder assumes your Flex project wants to use the SWCs in the chosen SDK folder, so you would have to change a lot of complier arguments to get it to work. But it should be more easy to swap a compiler from the command-line or Ant. The SWF compiler just takes source code and SWCs and produces a SWF. Royale has its own set of SWCs. Flex SWCs are a different set. So everything we write for Royale SWCs doesn't understand Flex, but that's independent of the compiler. HTH, -Alex On 2/18/18, 11:44 PM, "serkan....@likyateknoloji.com" <serkan....@likyateknoloji.com> wrote: > >Then is it possible to change the sdk of FlexBuilder to Royale and use ? > >Quoting Piotr Zarzycki <piotrzarzyck...@gmail.com>: > >> Alex, >> >> Are you saying that our SWF compiler is capable to compile Flex app? >> Wow didn't know. I thought everything what is written in Royale doesn't >> understand Flex. :) >> >> Piotr >> >> On Mon, Feb 19, 2018, 08:35 Alex Harui <aha...@adobe.com> wrote: >> >>> Hi Alina, >>> >>> What I'm asking is that you take your original code without porting it >>>at >>> all and run the Royale Compiler's SWF compiler. It should be able to >>> produce the same SWF you are deploying now. It might catch errors >>>that the >>> Flex MXMLC compiler does not catch. We need a successful SWF output >>>so we >>> know the compiler visited all APIs. Once you can get a SWF out, then >>>later >>> I will provide you with an updated Royale SWF compiler that will also >>> output an API usage report. >>> >>> Thanks, >>> -Alex >>> >>> From: Alina Kazi <alina.k...@d-bz.com> >>> Reply-To: "users@royale.apache.org" <users@royale.apache.org> >>> Date: Sunday, February 18, 2018 at 10:37 PM >>> >>> To: "users@royale.apache.org" <users@royale.apache.org> >>> Subject: RE: Substitutes in Apache Royale >>> >>> Hi Alex, >>> >>> >>> >>> Sure, >>> >>> I’m compiling the code with the royale compiler. Porting basic >>>components >>> that are available in Royale. >>> >>> >>> >>> Thanks >>> >>> Alina >>> >>> >>> >>> *From:* Alex Harui [mailto:aha...@adobe.com <aha...@adobe.com>] >>> *Sent:* Monday, February 19, 2018 11:16 AM >>> >>> >>> *To:* users@royale.apache.org >>> *Subject:* Re: Substitutes in Apache Royale >>> >>> >>> >>> Hi Alina, >>> >>> >>> >>> While I work on the compiler API report feature, you could start now >>> trying to get your code to compile with the royale compiler from the >>> command line. I think you can run the bin/mxmlc from the Royale >>>releases >>> with the same options you use with Flex MXMLC. >>> >>> >>> >>> Give it a try and let us know. >>> >>> -Alex >>> >>> >>> >>> *From: *Alina Kazi <alina.k...@d-bz.com> >>> *Reply-To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Date: *Sunday, February 18, 2018 at 8:29 PM >>> *To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Subject: *RE: Substitutes in Apache Royale >>> >>> >>> >>> Hi Alex, >>> >>> >>> >>> I’ll be waiting for your response. >>> >>> >>> >>> Thanks, >>> >>> Alina >>> >>> >>> >>> >>> >>> *From:* Alex Harui [mailto:aha...@adobe.com <aha...@adobe.com>] >>> *Sent:* Friday, February 16, 2018 2:02 AM >>> *To:* users@royale.apache.org >>> *Subject:* Re: Substitutes in Apache Royale >>> >>> >>> >>> Hi Alina, >>> >>> >>> >>> I can't guarantee that you will be in production in six months, but I >>> believe we can help you get to the point where every screen shows up >>>and >>> fills with data and we are fixing bugs in corner cases. We might >>>also be >>> chasing down memory leaks and things like that. My strategy for >>>lots of >>> things is to do the big things first and polish it later. For >>>example, I >>> recently pushed some basic Virtual Item Renderer support for Royale, >>>but >>> I'm pretty sure it will have bugs in corner cases, like deleting things >>> when scrolled to the bottom. But most apps start at the top and it >>>will >>> get you going and we'll fix those corner cases later. >>> >>> >>> >>> I want to finish up some infrastructural things in Royale over the next >>> couple of weeks, then I will adjust the compiler to generate an API >>> report. Once we see what that looks like, I should be able to help >>>take >>> the sample code you provided and make it work in Royale. So maybe in a >>> month or so, you'll see more activity around your code. Right now I >>>need >>> to clean up a few things so we can be more efficient working with you. >>> >>> >>> >>> You won't need an IDE to generate the API report. If you know what >>> compiler settings you are using for your Flex app, you can just run a >>> Royale compiler from the command-line with the same arguments. I >>>believe >>> that we are likely to make compiling your Flex app with the Royale >>>compiler >>> one of the steps in migrating. The Royale compiler will catch some >>>syntax >>> issues that the Flex compiler does not. >>> >>> >>> >>> More later, >>> >>> -Alex >>> >>> >>> >>> *From: *Alina Kazi <alina.k...@d-bz.com> >>> *Reply-To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Date: *Thursday, February 15, 2018 at 2:13 AM >>> *To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Subject: *RE: Substitutes in Apache Royale >>> >>> >>> >>> Hi Alex, >>> >>> Thank you so much. You gave me hope that I can achieve my target on >>>time >>> and at least I am working in right direction. >>> >>> At most places I'm using getItemAt(0) to access the element in >>> ArrayCollection. >>> >>> At some places myArrayCollection[0].propertyname to access it >>> >>> >>> >>> If you will modify the Royale compiler, I will definitely try >>>compiling my >>> Flex app with the Royale compiler and generate a report of APIs used. >>> >>> Currently I am using Visual Studio Code and apache royale 0.9.0 >>>release is >>> installed.I will need your guidance which IDE and apache royale release >>> should I use to generate that report. >>> >>> >>> >>> Thanks, >>> >>> Alina Kazi >>> >>> *From:* Alex Harui [mailto:aha...@adobe.com <aha...@adobe.com>] >>> *Sent:* Thursday, February 15, 2018 1:40 PM >>> *To:* users@royale.apache.org >>> *Subject:* Re: Substitutes in Apache Royale >>> >>> >>> >>> Hi Alina, >>> >>> >>> >>> Other than ArrayCollection, that looks right. There will be sorting >>> classes eventually. >>> >>> >>> >>> I think there are two buckets of things that you are going to need: >>> >>> >>> >>> Things we haven't written yet: >>> >>> - DividedBox/Container (mostly done) >>> >>> - Menu/MenuBar >>> >>> - VariableRowHeight >>> >>> - Editable DataGrids >>> >>> - Sorting? >>> >>> >>> >>> Things we have written, but aren't packaged in a way that makes >>>migration >>> easy: >>> >>> - TitleWindow >>> >>> - Canvas >>> >>> - ArrayCollection >>> >>> >>> >>> For ArrayCollection, do you use array indexing (myArrayCollection[0]) >>>or >>> do you access it as getItemAt(0)? >>> >>> >>> >>> You have so many files to port, it is tempting to create a Spark-ish >>>and >>> MX-ish component set. They wouldn't be fully backward compatible but >>>would >>> try to implement the most commonly used APIs. I'm wondering what >>> percentage of Flex APIs you actually used in your app. If I modify the >>> Royale compiler, could you try compiling your Flex app with the Royale >>> compiler and generate a report of APIs used? >>> >>> >>> >>> Thanks, >>> >>> -Alex >>> >>> >>> >>> *From: *Alina Kazi <alina.k...@d-bz.com> >>> *Reply-To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Date: *Wednesday, February 14, 2018 at 11:06 PM >>> *To: *"users@royale.apache.org" <users@royale.apache.org> >>> *Subject: *Substitutes in Apache Royale >>> >>> >>> >>> Hi, >>> >>> >>> >>> I have replaced few imports in Apache Royale Project after comparison >>>in >>> terms of functionality. >>> >>> As you all are more familiar to Flex and Apache Royale. >>> >>> Are these correct substitutes? >>> >>> import org.apache.royale.html.Alert; //instead of import >>>mx.controls.Alert; >>> >>> import org.apache.royale.events.CloseEvent; // instead of import >>> mx.events.CloseEvent; >>> >>> import org.apache.royale.net.events.FaultEvent; // instead of import >>> mx.rpc.events.FaultEvent; >>> >>> import org.apache.royale.net.events.ResultEvent; //instead of import >>> mx.rpc.events.ResultEvent; >>> >>> import mx.collections.ArrayCollection; //very similar to >>> org.apache.royale.collections.TreeData >>> >>> import mx.collections.Sort; // No Alternate found >>> >>> import mx.collections.SortField;// No Alternate found >>> >>> import mx.managers.PopUpManager; //org.apache.royale.core.IPopUp or >>> .IPopUpHost >>> >>> import org.apache.royale.utils.StringUtil;// instead of import >>> mx.utils.StringUtil; >>> >>> >>> >>> Reference: >>> >>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachefl >>>exbuild.cloudapp.net%3A8080%2Fjob%2FRoyale_ASDoc_Example%2FlastSuccessfu >>>lBuild%2Fartifact%2Fexamples%2Froyale%2FASDoc%2Fbin%2Fjs-debug%2Findex.h >>>tml&data=02%7C01%7Caharui%40adobe.com%7C483fe468971247eea76508d5776c9a5d >>>%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636546230705532569&sdata=V >>>NBmWZbyHO%2Fh5U2voIAmm%2FsPSdv565bw35NVUMu1mic%3D&reserved=0 >>> >>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapachef >>>lexbuild.cloudapp.net%3A8080%2Fjob%2FRoyale_ASDoc_Example%2FlastSuccessf >>>ulBuild%2Fartifact%2Fexamples%2Froyale%2FASDoc%2Fbin%2Fjs-debug%2Findex. >>>html&data=02%7C01%7Caharui%40adobe.com%7C2a0f4a052bf44496feaf08d57444554 >>>2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636542759199500428&sdata= >>>A9xjrAppjUqWDkvAJTgSHhOOW3ZlkZPPZTD5%2BG4eexw%3D&reserved=0> >>> >>> >>> >>> Thanks, >>> >>> Alina Kazi >>> >>> >>> > > >-- >Serkan Taş >Mobil : +90 532 250 07 71 >Likya Bilgi Teknolojileri >ve İletişim Hiz. Ltd. Şti. >https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&; >data=02%7C01%7Caharui%40adobe.com%7C483fe468971247eea76508d5776c9a5d%7Cfa7 >b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636546230705532569&sdata=4Z5Ifjw9l >iSfQczC8xq5sxviRJ8HTzjzUAgGTZMfxfc%3D&reserved=0 > >-------------------------------------- >Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece >yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını >taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın >içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız >kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden >siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu >mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul >etmez. > >This electronic mail and any files transmitted with it are intended >for the private use of the persons named above. If you received this >message in error, forwarding, copying or use of any of the information >is strictly prohibited. Please immediately notify the sender and >delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz. >Ltd. Şti. does not accept legal responsibility for the contents of >this message. >-------------------------------------- >
