Yes with 450 screen that’s a big job, air or the local wed browse is the simple approach
We went with royal, the design approach is the same as flex, we started by creating 1 to 1 components, the new compounded are JS CSS SVGS in our case about 30 components The royal component architecture is identical to flex so your front end logic does not need to change, we had a simple, MVC design As for AS3 we used a converter to TrueType, the code logic is the same, we used a tool and a bit manual work, we took the operation to add testing We do have a simpler application, 30 screens that generated about 1000 screens , we planned on 6 man months work, we are 3 into the project and on track, we will end up with a stand application, in the sweet spot of the industry, royal will never be in the sweet spot for the industry It is a big hit on cost and time, but we have a future, this app has been running is some form or other for 20 plus years, this is our 3rd rewrite we started with a desk top products toolbook 1995, which was good for 15 years, then we moved to flex 2010, and html5 from 2200 Happy to provide detailed information if you need Scott Sent from my iPad > On 22 Jun 2019, at 17:03, Blake McBride <blake1...@gmail.com> wrote: > > Hi. Thanks for the response. I have some questions below. > >> On Sat, Jun 22, 2019 at 10:42 AM Scott <sc...@matheson.it> wrote: >> >> AIR is a good option but you have the update install problems, the >> solutions are out there and air will do auto update etc ... >> >> Google web frame work well, you install a browser, that looks a desk top >> app but run the flex app like today, I have tried this and it work well the >> WebKit stuff is not difficult >> >> With the new commercial owners of air etc you should be able to come to a >> deal on the desk top install of flash, I have talked to Andrew about this >> approach >> >> In our case we had the skills and due to timing we went for a UX port to >> HTML5 but keeps all the as3 code, we converted to TrueType in less that 1 >> day >> > > Since my Flash front-end talks to the back-end with SOAP & REST, I am able > to create an equivalent HTML front-end without changing the back-end. But > that is essentially a re-write of the front-end, and with 450 screens, > that's a bit of a task. I do not understand what you mean by "keeps all > the as3 code" since the required JavaScript code for the HTML is very > different. I also don't know what "converted to TrueType" means since > that's just a font. > > > >> Royal is an option but to hard and IMHO a dead end, in a few years your be >> porting again >> >> >> >> Sent from my iPhone >> >>> On 22 Jun 2019, at 16:25, Blake McBride <blake1...@gmail.com> wrote: >>> >>> Greetings, >>> >>> I have a large Flex(3.5)/Flash app that (obviously) runs under a browser. >>> Since the Flash player is going away, I am wondering if I should consider >>> AIR. What are my other options? What's easiest? >>> >>> Thanks. >>> >>> Blake McBride >> >>
