(copied from another email thread; this one seems more appropriate). I created the Mobile kit. I did it separately because it was supposed to mimic how UINavigationController, UIViewController, and UITabController work on iOS (which I'm more familiar with than Android). But there is nothing specific in that kit (that I remember) which ties it to a mobile device. That's opposed to Storage kit, which is dependent on AIR to provide a file system on the SWF platform.
I think once we look into refactoring the packages, a lot of Mobile could be moved out. ‹peter On 11/2/17, 8:48 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote: >Hi, I think we should not differentiate between desktop and mobile. We >should make components ready for both platforms and differentiate desktop, >web, mobile or tablets mainly with CSS for sizes and in some case with >code >(i.e: DateChooser use to behave differently in desktop than mobile) > >2017-11-02 13:29 GMT+01:00 Yishay Weiss <[email protected]>: > >> >> >> For now, we would like to have an Apache Royale "ViewStack" equivalent >>but >> we do not know where to start. >> What do you think the parent component should be ? Could you give to us >> some cues ? >> > > >-- >Carlos Rovira >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2 >Fcarlosrovira&data=02%7C01%7C%7Cf4ef6800329a4b7db4f608d521f021cc%7Cfa7b1b5 >a7b34438794aed2c178decee1%7C0%7C0%7C636452237602199585&sdata=VJCP0F%2F%2BJ >Qg8fL0GOhl9VQNeocXe0y0flc2rpAYhgRI%3D&reserved=0
