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" <flexcapaci...@gmail.com>: > 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&list=PLFBNT6gqr5u_NvUaLdHziGES_7Rw8-2pX&index=10&t=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
