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 <aha...@adobe.com.INVALID> Sent: 3/11/20 2:00 PM To: "users@flex.apache.org" <users@flex.apache.org>, "pa...@compuace.com" <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
