[GitHub] carlosrovira commented on issue #360: ActionScript conversion examples?

[GitBox <gi...@apache.org>]

carlosrovira commented on issue #360: ActionScript conversion examples?
URL: https://github.com/apache/royale-asjs/issues/360#issuecomment-450546396
 
 
   > The real reality would be to release the flash plugin open source to let users decide what to change or not, with clear and transparent long term agenda
   
   @ROBERT-MCDOWELL , I was in that boat some years ago. I thought Adobe fails on donating Flash to some foundation around 2005 to 2010, so all the big players will "control" the most ubiquitous piece of code on the internet to show client content and make it a true standard that works cross all browsers. At that time Adobe didn't do that, that makes Apple and Steve Jobs start a marketing thread that initiated the reallity we live today.
   
   Nowadays, is useless think about open sourcing Flash Plugin, since is a plugin and Browser vendors doesn't want a plugin, so even making it Open Source, will not solve the Flash Plugin reality, that is to turn year after year in an obsolete piece of code. Today is already a nightmare to develop and debug against Flash. That's a fact, and nothing will make that change.
   
   So as Alex's says, to all people out there, not only you, the only real path that could make you work against something that will build up for the future is to join us, and help this effort (or other that you consider the best option for you). In my experience doing several hours working in Royale is that you can migrate with some plan in mind. It will cost many time, It's not easy at all. But you can do it, and regretting about something none of use can control, is not making things change, just loose your time, as we did all this years complaining. Another important point is that, in my humble opinion, all people that wants to migrate will need to get involved in this project, since they will need to work in the things they need, while others do other tasks. But is impossible that our current team could do 100% of the things people currently need. So the only real path is to join and start assuming hours and cost to this project. In the long term, that cost will proven as needed. That's what we did at Codeoscopic and I think we're getting to migrate from Flash with 70-80% of the original code, taking into account that we want to update our clients with latest UX and UI conventions that are not in Flex (Drawers, responsiveness, mobile-table-desktop...)
   
   I think is a good time to join us. My advice is: Get on Board now! we have a technology that is working nowadays. We'll be putting our first royale client migrated from Flex in a month or so. We have it at 90%, so is clear is possible...doesn't make sense to me regretting about how things will done by companies and take this opportunity to control your future, now exporting to JS and some day to WASM, when we work in that target.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services