Actually, a lot of mobile features could be ported to desktop in the future, as it seems to me that the differences are going to be less and less with new desktop operationg systems and devices, e.g. windows 8 tablets and touch enabled laptops.
For example, the touch-enabled components (e.g. lists) and the DPI-based scaling feature of some mobile skins could probably be useful on the lastest touch-enabled laptop as well.. thoughts? 2012/11/21 Antonio Ortiz <zenk...@hotmail.com> > It will be great... :) > > > Date: Wed, 21 Nov 2012 15:30:27 +0100 > > Subject: Flex Mobile components in desktop/browser applications > > From: carlos.rov...@codeoscopic.com > > To: flex-dev@incubator.apache.org > > > > Hi, > > > > I'd like to ask the motivation behind mobile components (like > > ViewNavigator, CallOut,...) be only for mobile. > > > > For example, a ViewNavigator is a great component for wizard > > implementations having lot of sense in browser/desktop apps. The builtin > > transitions and push/pop functionality is really cool!. > > > > So what do you think about extend the use of mobile components to > > browser/desktop apps. > > Right now it could be done with some tricks like the ones described here: > > > > http://www.riagora.com/2011/08/flex-mobile-in-the-browser/ > > > > In my test I need mobilecomponents.swc and mobile.swc in the project to > get > > it work, but a tight implementation should avoid that separation and > bring > > at least new MXML skins for desktop/browser applications while maintain > > current mobile skins for mobile targets. So we could make some changes in > > this direction in order to get a more natural use. > > > > What do you think about it? > > > > > > -- > > Carlos Rovira > > Director de Tecnología > > M: +34 607 22 60 05 > > F: +34 912 35 57 77 > > http://www.codeoscopic.com > > http://www.directwriter.es > > http://www.avant2.es > >
