Re: Migrating Enterprise Flex Application

I generated the api reports for the components in my application. Please see the attached reports. Please review them. What should be my next steps? reportControlMgmt.txt reportDashboards.txt

Re: Migrating Enterprise Flex Application

Hi, I have downloaded the files and will turn it into a single combined report. Some next steps might be: -Look through the report files yourself for 3rd-party components and come up with a plan for replacing those. -Decide whether you want the UI to remain as similar as possible or whether you

No Touch support?

Hi, I'm looking how to provide touch support for Drawer so users can slide out. Is a default behavior in this kind of components. I'm seeing there's no TouchEvent or something similar. I think this is an important flaw, since not having this is like to say we are not prepared for mobile and in

Re: No Touch support?

Hi Carlos, You can use negative words like "flaw" if you want. But really, the fact is that nobody has had time to work on Touch support. Mainly because the folks interested in migrating to Royale from Flex have not required it yet. Drawer is cool, and new, but I don't know that migrating

Re: No Touch support?

Hi Carlos, Touch support is a can of worms. Basic touch support comes for free from Mouse Events. Anything more than that, gets very complex very quickly. I use Hammer.js in my own app to handle touch, and it works very well. https://hammerjs.github.io/ Harbs >

Re: No Touch support?

@harbs could that become a blog entry? On Wed, Jul 4, 2018, 2:19 PM Harbs, wrote: > Possibly. > > The way Hammer.js works is that you attach it to an element and create an > instance of it or a controller. The specific touch events need to be > specified. > > > On Jul 4, 2018, at 7:34 PM, Alex

Re: No Touch support?

Harbs, Can we wrap Hammer.js into more easily reusable TouchControllers in Royale? IMO, it doesn't matter if it is a can of worms. Royale hopefully makes it easy to replace TouchControllers. So you can write one that mostly works and if someone offers a better one at some point, you can

Re: No Touch support?

Possibly. The way Hammer.js works is that you attach it to an element and create an instance of it or a controller. The specific touch events need to be specified. > On Jul 4, 2018, at 7:34 PM, Alex Harui wrote: > > Harbs, > > Can we wrap Hammer.js into more easily reusable TouchControllers