Hugo, I'm not sure where I have seen this but I think Serkan who migrating his app has it on the GitHub.
Serkan please correct me if I'm wrong. Maybe it can help, depends where he is with his migration... Piotr On Fri, Nov 16, 2018, 5:10 AM Alex Harui <[email protected]> wrote: > Yeah, it is a lot to learn. Did you ever make patches to the Flex SDK > framework code? > > I will try to put together a step-by-step tutorial on the next component I > get to run. I'm not sure there is only one path to take, but maybe. Until > I get to that, you can try looking at the change history in MXRoyale around > a component that you think is similar to one you need. > > HTH, > -Alex > > On 11/15/18, 4:52 PM, "hferreira" <[email protected]> wrote: > > Yes. I read before posted. > In a conceptual point of view is a good material. > Explains the approach. > Create the component without implementation, surrounding Royale API > (the > important is the emulation like an interface, the > content/implementation can > and should be different from Flex SDK, using directly Royale API as > match as > possible). > And on the finish like, code the implementation. > Also, I understand now, that correctly MXRoyale it's very uggly > because the > intention is first to compile a big project (recently done), then put > the > things work (components implementation) and only then maybe try to > simulate > more or less the Flex SDK UI. > > Perhaps, it's just me, but for someone inexperience with Royale API, > breads, > etc ..., became lost (or worst can follow to do a bad implementation) > without a code sample guide. > > But if there are guys that are doing this successful, perhaps it's > just me. > > > > -- > Sent from: > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cc046da5127e44ea591b308d64b5dd615%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636779263730583017&sdata=04xS6uZzR8rVOlCILO%2B9%2BRsnVkmoWThOX9ADUqXibwo%3D&reserved=0 > > >
