Alina is nearing the point of getting everything to compile. Now it is time to get things to "run". And later, we will try to get things to "run and look good".
I've been distracted by other things, but I hope get back to getting components to "run". Meaning, they show something on the screen, even if it is truly ugly, the wrong size, etc. It just shouldn't throw exceptions or show nothing. I've written up how I go about doing that here: https://github.com/apache/royale-asjs/wiki/emulation-components I've been using the mustella/tests/mxtests/basicTests as my test bed. You can look at recent commits to see how to enable tests. Fundamentally, we get things to "run" by borrowing beads from Basic and/orExpress. In many cases, functionality that the Flex SDK expects that Royale is still missing should be implemented as beads in Basic. So if the process I've described above sounds too unattractive, you can volunteer to create some of these missing beads. The only missing beads I can think of right now is the beads to make a ColorPicker. So creating a Basic ColorPicker would be useful. Yet another task is to see if Jewel views can be used on the Emulation components. That will hopefully be how we do the "run and look good" later. Thanks, -Alex On 6/7/18, 1:05 AM, "Harbs" <[email protected]> wrote: > IMO, if we all pitched in on emulation > Perfection can be the enemy of success. Sorry to be so selfish, but I am just trying to keep my job. Fair enough. If I were to pitch in with the emulation, what would you recommend I work on? Harbs > On Jun 6, 2018, at 9:24 PM, Alex Harui <[email protected]> wrote: > > IMO, if we all pitched in on emulation, we would have many more migrating users at the end of the year claiming that the UI is still a bit ugly. If we leave emulation to fewer people, then at the end of the year, we may not have gotten all of the emulation components up and running and so fewer people will try them. IMO, every day we don't make migration easier, we lose more potential users to other frameworks. > > I have proposed workarounds that will let us avoid Type Selector name collisions that won't take nearly as much of my time to assist with. Perfection can be the enemy of success. Sorry to be so selfish, but I am just trying to keep my job. You are not wrong to pursue new users who don't have apps to migrate. But I'm more certain that there are likely to be important Adobe customers in the group with apps to migrate than the group that will be new to Royale this year. > > My 2 cents, > -Alex
