CFBundleDisplayName in app descriptor
Hey all: When creating a new app on Apple's App Store Connect the app title must be globally unique which caused us to create a longer name that wasn't taken. This results in our app name being truncated with ellipses beneath the app icon on the device desktop. We want to set a shorter name that will display beneath the icon, and Apple supports just that by simply setting this element in Info.plist: CFBundleDisplayName Keiretsu But Adobe designed the AIR SDK (specifically ADT) to prevent us from defining this element in the application.iPhone.InfoAdditions section of the application descriptor file for iOS. This is documented on this page: https://help.adobe.com/en_US/air/build/WSfffb011ac560372f-5d0f4f25128cc9cd0cb-7ffe.html I tried anyway, and ADT threw this fatal error: "error 105: application.iPhone.InfoAdditions contains an invalid value" This seems like a pretty big miss on Adobe's part not to support this in ADT. Just seems this should be supported in InfoAdditions. I wonder why Adobe didn't do this. Perhaps Harman will listen and fix ADT. I'm trying to figure out how to submit this to Harman. I know it seems like a tiny issue, but we've created dozens of apps in the past several years, and finding unique names on App Store Connect that aren't taken and don't truncate on the desktop is a very real issue for us. We have written scripts to unzip, update Info.plist, and zip/sign before but this shouldn't be so difficult. Thoughts? Erik
Re: Flex web deployment...
Hey look this out I found also something pretty cool it seems that Silverlight is also back :) https://opensilver.net/announcements/introducing-opensilver.aspx 10.03.2020, 17:03, "Ramazan Ergüder Bekrek" : > To see the talk about the tech with demos you can watch this : > https://www.youtube.com/watch?v=7JUs4c99-mo=youtu.be > > 10.03.2020, 16:18, "Carlos Rovira" : >> Thanks for sharing, sounds good, but still nothing real until it will be >> launched, and at that time I think people will need to evaluate it to see >> if it works as expected. For what they say it will only work on Chrome, >> that's not bad... and the idea itself seems promising. But time will tell >> if it goes to real >> Thanks for let us know! :) >> >> El mar., 10 mar. 2020 a las 15:44, Ramazan Ergüder Bekrek (< >> e.bek...@yandex.com>) escribió: >> >>> From my researches I found out that it will be possible to run Flash/Flex >>> applications after 2020 inside of the browser due to this new technology >>> which will use WebAssembly. >>> >>> >>> https://medium.com/leaningtech/preserving-flash-content-with-webassembly-done-right-eb6838b7e36f >>> >>> Maybe we don't need to freak out at all anymore. >> >> -- >> Carlos Rovira >> http://about.me/carlosrovira
Re: GUI IDE need.
This is just my idea and my intuition tells me that the FB DV was built as an SWF app which was loaded inside of eclipse like a browser SWF what if we decompile its source code and just inject it in Moonshine editor? 11.03.2020, 19:57, "QA" : > Hi, I agree that a GUI IDE is needed or would be beneficial. I've > planned Royale as an export target for Web Export but it's been on the > backlog. I've mentioned this in another post but Web Export is a plugin > for Adobe XD that exports artboards to the web. Currently it supports > exporting markup to HTML and CSS. > > XD supports all the layout, positioning and design features used for > prototyping. > > To support Royale more fully would require some work but it would be > much less work to add in support than write your own design view. > > YouTube playlist > https://www.youtube.com/playlist?list=PLFBNT6gqr5u_NvUaLdHziGES_7Rw8-2pX > > Documentation > https://velara-3.gitbook.io/web-export/ > > More comments inline... > > On 3/9/20 11:28 PM, Alex Harui wrote: >> While it may be that someone offers a GUI IDE some day for Royale, there is >> are some other approaches, one that has been prototyped, and one that wasn't >> possible with Flash Player. >> >> IIRC, one prototype adds some things to your app that allow you to edit the >> x/y/width/height in your MXML and immediately see the results in the browser. > > Web Export has a live export feature so that as you make changes it > updates live in the browser (for HTML). > > https://www.youtube.com/watch?v=kfQQkxi8eG4=PLFBNT6gqr5u_NvUaLdHziGES_7Rw8-2pX=10=0s > > You can have it update the MXML in an existing file or have it write the > MXML document each time it changes. > >> The other approach is to write a bead that can track your MXML from the >> browser so you can use the browser tools to modify the UI and hit some >> button that will then update the MXML. >> >> There are some limitations to these approaches which is why none are >> available at this time. The main one is that use of view states greatly >> complicates these approaches (as it does for a GUI IDE as well). So one >> question for you, are you using view states (mx:State)? > > XD supports states in a way. What I've seen from users is they have > different pages and manually switch between them. I think the way XD > creates it's live prototypes is listing all property changes. That > information can be stored in State markup. > > If you (or other Flex devs) want to join me on adding Royale support to > Web Export I can add you to the github project and you'll be about one > year further along towards a GUI. > > Jude
Re: GUI IDE need.
Alex: Having not written a GUI IDE, I am a Monday morning quarterback in this regard, but it seems to me; If Royale's intention is to start as its base most/all of Flex's language then FB would be conceptually a great place to start. However this would only be true were one to use Eclipse as the underlying architecture for the IDE. Obviously all of the compiling/transpiling & connections to the browser would need to be rewritten. But the GUI and the intellisense stuff would all be done. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 2:00 PM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: GUI IDE need. FB DV is Flash Builder Design View. I don't think there is much FB code that is useful to the current teams building a Royale IDE. I don't know what the future of FB is, but I don't think there will be future releases. But some of the principles behind FB's DV, could be applied to live-editing in Royale and I think it would be better than having it in an IDE. Of course, I could be wrong... -Alex On 3/11/20, 10:04 AM, "Paul Stearns" wrote: Alex: Not to sound too ignorant, what is "FB DV?" What is Adobe doing with FlashBuilder? If they are deprecating Flash, what use do they have for FlashBuilder? That might be a good code base for a Royale GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:56 AM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: GUI IDE need. I hear what you are saying, but I am hopeful that we can build that into your app sort of like an automated testing plugin. Royale will eventually need to support other automated testing libraries and other code that "disappears at production". One of the reasons for having "beads" underneath the components is so that we can more easily add/remove helpful pieces of code to enhance productivity. IIRC, the FB DV was essentially running your app loaded into a DV Flex app. I am hopeful that Royale is set up so that you can essentially plug in DV functionality into your app (instead of wrapping it, which caused occasional issues in FB). -Alex On 3/11/20, 8:48 AM, "Paul Stearns" wrote: I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
Hi, I agree that a GUI IDE is needed or would be beneficial. I've planned Royale as an export target for Web Export but it's been on the backlog. I've mentioned this in another post but Web Export is a plugin for Adobe XD that exports artboards to the web. Currently it supports exporting markup to HTML and CSS. XD supports all the layout, positioning and design features used for prototyping. To support Royale more fully would require some work but it would be much less work to add in support than write your own design view. YouTube playlist https://www.youtube.com/playlist?list=PLFBNT6gqr5u_NvUaLdHziGES_7Rw8-2pX Documentation https://velara-3.gitbook.io/web-export/ More comments inline... On 3/9/20 11:28 PM, Alex Harui wrote: While it may be that someone offers a GUI IDE some day for Royale, there is are some other approaches, one that has been prototyped, and one that wasn't possible with Flash Player. IIRC, one prototype adds some things to your app that allow you to edit the x/y/width/height in your MXML and immediately see the results in the browser. Web Export has a live export feature so that as you make changes it updates live in the browser (for HTML). https://www.youtube.com/watch?v=kfQQkxi8eG4=PLFBNT6gqr5u_NvUaLdHziGES_7Rw8-2pX=10=0s You can have it update the MXML in an existing file or have it write the MXML document each time it changes. The other approach is to write a bead that can track your MXML from the browser so you can use the browser tools to modify the UI and hit some button that will then update the MXML. There are some limitations to these approaches which is why none are available at this time. The main one is that use of view states greatly complicates these approaches (as it does for a GUI IDE as well). So one question for you, are you using view states (mx:State)? XD supports states in a way. What I've seen from users is they have different pages and manually switch between them. I think the way XD creates it's live prototypes is listing all property changes. That information can be stored in State markup. If you (or other Flex devs) want to join me on adding Royale support to Web Export I can add you to the github project and you'll be about one year further along towards a GUI. Jude
Re: GUI IDE need.
FB DV is Flash Builder Design View. I don't think there is much FB code that is useful to the current teams building a Royale IDE. I don't know what the future of FB is, but I don't think there will be future releases. But some of the principles behind FB's DV, could be applied to live-editing in Royale and I think it would be better than having it in an IDE. Of course, I could be wrong... -Alex On 3/11/20, 10:04 AM, "Paul Stearns" wrote: Alex: Not to sound too ignorant, what is "FB DV?" What is Adobe doing with FlashBuilder? If they are deprecating Flash, what use do they have for FlashBuilder? That might be a good code base for a Royale GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:56 AM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: GUI IDE need. I hear what you are saying, but I am hopeful that we can build that into your app sort of like an automated testing plugin. Royale will eventually need to support other automated testing libraries and other code that "disappears at production". One of the reasons for having "beads" underneath the components is so that we can more easily add/remove helpful pieces of code to enhance productivity. IIRC, the FB DV was essentially running your app loaded into a DV Flex app. I am hopeful that Royale is set up so that you can essentially plug in DV functionality into your app (instead of wrapping it, which caused occasional issues in FB). -Alex On 3/11/20, 8:48 AM, "Paul Stearns" wrote: I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
Alex: Not to sound too ignorant, what is "FB DV?" What is Adobe doing with FlashBuilder? If they are deprecating Flash, what use do they have for FlashBuilder? That might be a good code base for a Royale GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:56 AM To: "users@flex.apache.org" , "pa...@compuace.com" Subject: Re: GUI IDE need. I hear what you are saying, but I am hopeful that we can build that into your app sort of like an automated testing plugin. Royale will eventually need to support other automated testing libraries and other code that "disappears at production". One of the reasons for having "beads" underneath the components is so that we can more easily add/remove helpful pieces of code to enhance productivity. IIRC, the FB DV was essentially running your app loaded into a DV Flex app. I am hopeful that Royale is set up so that you can essentially plug in DV functionality into your app (instead of wrapping it, which caused occasional issues in FB). -Alex On 3/11/20, 8:48 AM, "Paul Stearns" wrote: I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
One little remark/experience from my side as kind of argument against pure live-editing and hot-reload: There is high risk you get in a "try and error mode"; without spending sufficient time on thinking! Several times it happened to me that I ran in a "change-test-change" loop for about an hour, always thinking "now I got it". But after a walk to the restrooms, or even better: a night of sleep, and digesting things and spending some time on thinking... The solution was there within minutes. At the end: Nothing is black and white ;-) Regards Hans Am 11.03.2020 um 16:47 schrieb Paul Stearns: I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
I hear what you are saying, but I am hopeful that we can build that into your app sort of like an automated testing plugin. Royale will eventually need to support other automated testing libraries and other code that "disappears at production". One of the reasons for having "beads" underneath the components is so that we can more easily add/remove helpful pieces of code to enhance productivity. IIRC, the FB DV was essentially running your app loaded into a DV Flex app. I am hopeful that Royale is set up so that you can essentially plug in DV functionality into your app (instead of wrapping it, which caused occasional issues in FB). -Alex On 3/11/20, 8:48 AM, "Paul Stearns" wrote: I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
I think we will have to disagree on this. Three things (that I can think of quickly), which would be difficult without a GUI; I use quite regularly the alignment capabilities of the IDE, where I select multiple items and align right, left, bottom, middle , top & center. If I have 20 fields on a form I want to align I can't do it visually using the immediate display technique. Additionally when I am initially designing my form, the code may not be complete enough to be displayed in a browser. I will also often grab multiple items and move them around the screen, with their relative positions intact. Selecting multiple items and then modifying multiple properties for the selected items. Doing all of this manually is a waste of valuable developers time, and a step back into the dark ages. Yes having something that displays your changes in near real-time is better than nothing, but hardly a replacement for a good GUI IDE. Paul R. Stearns Advanced Consulting Enterprises, Inc. 15280 NW 79th Ct. Suite 250 Miami Lakes, Fl 33016 Voice: (305)623-0360 x107 Fax: (305)623-4588 From: Alex Harui Sent: 3/11/20 11:19 AM To: "users@flex.apache.org" Subject: Re: GUI IDE need. On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Re: GUI IDE need.
On 3/11/20, 4:43 AM, "Olaf Krueger" wrote: Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. Hence my hope that someone will make live-editing of Royale MXML work. IMO, Any IDE DesignView equivalent that doesn't use a browser to render is going to have fidelity issues. Live-editing has the potential to be even better than hot-reload for some scenarios. Of course, I could be wrong... -Alex
Running Flash/Flex in WebAssembly using CheerpX
For those who overlooked the post of Ramazan Ergüder [1], I think it's worth to move this information to its own thread. Thanks for sharing, Ramazan! In short, amongts other things, CheerpX is working on "Extending the life of Flex, AS3 and AS2 Flash content with WebAssembly virtualization". https://medium.com/leaningtech/preserving-flash-content-with-webassembly-done-right-eb6838b7e36f https://medium.com/leaningtech/running-flash-in-webassembly-using-cheerpx-an-update-d500b6fbc44e https://www.youtube.com/watch?v=7JUs4c99-mo=youtu.be https://www.leaningtech.com/pages/cheerpx.html [1] http://apache-flex-users.246.n4.nabble.com/Flex-web-deployment-tp18087p18101.html -- Sent from: http://apache-flex-users.246.n4.nabble.com/
Re: GUI IDE need.
Hi Paul, >If however you want to design highly usable business applications deployed to thin clients (to use an ancient phrase) you need GUI tools to be productive. Not agree. Modern JS frameworks are supporting "hot reload" (Royale not yet) which means the browser view is refreshing automatically after any code change/compilation... and depending on the framework and project, this just takes seconds or milliseconds. So, you see the results in near realtime instead of waiting for the compiler and restarting your app all the time. >If you are designing traditional web applications where everything is stacked and the user scrolls forever then yes you can do that without a GUI IDE. I think these days it is is more a design/UX decison if you go with a "one page scroll" approach. Nobody stops you from implementing complex UIs using HTML/CSS/JS. JS frameworks (including Royale) are "component driven" like Flex. So, breaking down complex apps into reusable components has become the standard in web development. >My initial test application (very simplistic) for Royale can be found here... As Carlos mentioned, I guess you should be able to implement this by using Royale/Jewel or any other JS framework out there. But with Flex, we were used to had anything (or most of the things) we need within the SDK. With JS development (including Royale) you might want to use 3rd party (UI) libaries in order to increase quality and productivity. Just my 2 cents, Olaf -- Sent from: http://apache-flex-users.246.n4.nabble.com/
