Hi Mandeep, We definitely need more folks to pitch in and write tests. Only now are we getting to the point where tests would be helpful. Earlier, significant changes could be made and would require re-writing a lot of tests.
So, if you and others can contribute tests, that would be great. -Alex From: Mandeep Sarma <muveryd...@gmail.com> Reply-To: "users@royale.apache.org" <users@royale.apache.org> Date: Wednesday, August 14, 2019 at 9:59 AM To: "users@royale.apache.org" <users@royale.apache.org> Subject: Re: RoyaleStore broken with sdk 0.96 Hi Carlos, I was in no way trying to challenge the intelligence of the methods being used to develop Royale, I was simply trying to understand why it’s broken. And my question was more on trying to understand why the development of Royale breaks old code, for example several examples no longer work, at least for me. I’m only trying to evaluate the potential future risks in case something breaks due to changes in the SDK and whether I'll be able to fix them or not. If I came across as criticizing anything or anyone I apologize. Mandeep. On Wed, Aug 14, 2019 at 4:12 AM Carlos Rovira <carlosrov...@apache.org<mailto:carlosrov...@apache.org>> wrote: El mié., 14 ago. 2019 a las 5:54, Mandeep Sarma (<muveryd...@gmail.com<mailto:muveryd...@gmail.com>>) escribió: This brings up another question, doesn't the way in which Royale is being developed significantly increase the risks to future Royale SDKs breaking applications in lengthy development (large applications) ? I ask because Royale is being considered as a platform to convert a Flash Player app. Can you elaborate more on what you think the way in which Royale is being developed can cause problems? We are in 0.9.6 version, still not 1.0, so still code that need to be followed and requires people to be "connected" to what community is doing. My personal opinion is that we'll reach a point when Royale will be very stable and many or most of the core things will hardly change in the future. Other will still need to be evolved even more towards other major versions (2.0...) In my case, I use to recompile example apps like Tour de Jewel, and my personal Apps to see if changes break something. Sometimes this happen, but is inevitable if we want to progress. Some times things where set in a temporal shape or was implemented as better as contributors can in the amount of time invested, or simply put in that shape as a first step to be iterated in the future... Since Royale is a complex framework, don't see other way with the current set of people working on it, but it will be interesting to know more about what you think and propose other ways. Thanks -- Carlos Rovira http://about.me/carlosrovira<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C2efc4c273ee84e26be4008d720d8bafc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637013987539875703&sdata=6RqgWV6i8rguJA01i0CvwomB55y9KR581KSeeP%2FSgjU%3D&reserved=0>
