aharui commented on issue #648: Tasks to Reach 1.0 URL: https://github.com/apache/royale-asjs/issues/648#issuecomment-570484113 IMO, having a recent successful migration in production on MXRoyale is the key to 1.0 and new users. That's why that is the only thing I'm working on (because others are thankfully working on PAYG in Basic). Fancy CSS doesn't matter to MXRoyale migration because it didn't exist in Flex, so I won't be working on that. I am not a marketing/business person nor a fortune-teller, but my guess is that our new users in 2020 will be folks migrating Flex projects. The reason I focus on MXRoyale is because, as every day ticks off the calendar in 2020, the time left to migrate gets shorter. Every bug I fix in MXRoyale makes the time to migrate shorter. While I am glad that Carlos and others have worked on Jewel, work on Jewel does not shorten the time to migrate as much as work on MXRoyale. Folks who use Jewel must have the time/money to rethink their UI. Fewer people will have that time in 2020. I am hopeful we will get enough of MXRoyale running to get someone into production early in 2020 and attract more users. Then I would encourage those users that when they have time to give their app a new look to use Jewel, or if they like Royale and want to start new projects to use Jewel. And hopefully some will start new projects and start talking about how great Jewel and Royale are and that will bring in folks without any footprint in Flex. Of course, I could be wrong. Anyway, back to MXRoyale bugs...
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
