Hi Ulrich, While it would be great if we could do all of these things in the order you listed, it is important to understand that Royale is not a corporate-driven product like Flex was at Adobe. I’m the only person who is currently able to contribute full-time. Everyone else contributes when they can. Apache projects are volunteer-driven. There is no way a team of part-time volunteers can commit to a release plan or max out Royale’s compatibility with Flex any time soon. Or even test Royale like Adobe tested Flex.
Instead, the contribution model has to change. Every person wanting to migrate their Flex app to Royale should plan to have at least one person under their control learn how to fix bugs and write tests and add compatibility features to Royale. Doing so gives you control over the future of Royale. There won’t be some “other corporation” you have to plead with to have them fix a bug or add a feature. Instead, those of you who are stakeholders because you have Royale apps will be able to make the changes you need when you need it, and no “other corporation” can suddenly take almost all of the developers away from the project. IMO, we need more contributors first, in order to make the rest happen, and the best source of these new contributors are the folks using Royale. Yes, that makes it harder in some ways than just using Royale, but if you are one of the early experts in Royale, and Royale becomes popular, you will have a competitive advantage over everyone else. My 2 cents, -Alex From: "[email protected]" <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, November 7, 2018 at 11:47 PM To: "[email protected]" <[email protected]> Subject: Re: Royale vs other frameworks Hello, I think before including other technologies there are more important things: · Work towards 1.0 release. Create a features/release plan. · Max out compatibility to currently existing Flex projects in the IT industry. Many many companies have customer tailored Adobe Flex applications. Easyly transfering them to web would bring alot of support. · Improve stability before adding features. The developers love the maturity of Flex. · Find more contributers · Find more users · May be create a company around Royale offering consultancy services and addon components. And it would most importantly open Royale up for investors. Currently we are also exploring Royale to 1. convert existing apps and 2. give our dev team something they are used to. Ulrich Müller Dipl. Inf. CARNET GmbH Chemnitz, Germany www.carnet-gmbh.de<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.carnet-gmbh.de%2F&data=02%7C01%7Caharui%40adobe.com%7Cb9d6f3655d5f4062defd08d6454e5f15%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636772600241049370&sdata=MWAivJPeL3UA79kw7U0XJc%2Bj3%2Fxtqe0Q5B797aB50JM%3D&reserved=0> Von: Carlos Rovira <[email protected]> Gesendet: Mittwoch, 7. November 2018 23:54 An: [email protected] Betreff: Re: Royale vs other frameworks Hi, El mié., 7 nov. 2018 a las 21:09, Fréderic Cox (<[email protected]<mailto:[email protected]>>) escribió: Thanks for clarifying this a bit more Carlos, it is an interesting topic for me as the company I work for is in some trouble and if I should find a new job (unsure at the moment) then it can be that I need to use typescript, react or angular .. as the entire dev community seems to use these days. Nobody has heard of Royale, so I'm planning to look into also because I like the workflow with AS3 and MXML. is clear that now the game is Angular, React and VueJS. Royale will need more time to be considered by more people. I expect that as me and others can get real apps written in Royale, people will want to enter Royale. I can say that I think now is a good time. But if you are making a change, I'm afraid you'll need to go with the stablished JS frameworks. Consultancy companies shell what is hot, since is what clients demand. In my company, since we shell products and services (not technology itself), we can go with Royale, since our clients don't know how is done, and it doesn't matter for them, while works ;) So for us, Royale is the clear winner. I see similar concepts so far in those Js frameworks I recently started to pick up, I'm not very skilled in them yet so can't compare it yet. Truth is there are not that many actionscripts developers anymore so I think part of Royale's succes would be to embrace typescript. I'm with you, Royale will be a real option with two things: 1) TypeScript support 2) More NodeJS support (We support NodeJS, but I think we need real world testers that know Royale and signal if we need to improve things, and I'm sure will be some things to improve for sure) How would such a thing be achieved? I wouldn't know where to start at this point to be honest :-) If you refer to add TS support, you can start it as a hobby project trying to get some fun. Some points I'll do: 1) you'll need to be confortable with Royale, install repos, build with Maven and ANT, build SDK from repos. Use VS Code with you SDK and try some example, for example Jewel Example. I think this is a must, don't know how much of this you still know, if not invest some time trying it. I think is funny 2) Browser compiler code and localize AS3 grammar, and related classes and read in the wiki how compiler works with this. I think Alex wrote something in the wiki. You can always ask here. I still does not have the knowledge in that field (hope to acquire at some time as I end my work in other parts), but others could help you 3) now TS: I think TypeScript grammar should be probably available in a license that we can use so the work should be to bring it to the project and wire it in the compiler, so .ts files will be recognized and could be analyzed, processed and compiled. Don't know how much time/effort could be this, but again, you can ask here. If you take that seriously and make some PRs with some quality and people see your commits are reliable (don't break things, and don't need to editing, or few editing) you can become committer and continue on your own. If I have time, I think that would be a very cool and fun task to do, but I'm buried in other tasks, and I think I have work in Royale for years, and others too, so I think we need help on that field to make that happen. Thanks and hope you're encouraged to participate! :) -- Carlos Rovira http://about.me/carlosrovira<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cb9d6f3655d5f4062defd08d6454e5f15%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636772600241059379&sdata=mlk8Xk7vgQQ%2BZkH7j1p8cAjHf3e%2FyyOrc15kKJVGvE8%3D&reserved=0>
