@maxime: true, but we should begin considering that touch interactions is starting to exist on notebooks and desktop.. AIR and FP supports this since some major releases (AIR 2 and FP 10 I think), Windows supports touch screen since version 7, and with version 8 someone is actually selling such kind of devices.. if I have a touch screen in a notebook, an O.S. supporting it, a runtime supporting it, why can't I use touch to scroll through a list just or to zoom an image, like I currently do on mobile phones and tables?
2012/11/21 Scott Rowe <scottr...@mac.com> > Same here the week before last > > On Nov 21, 2012, at 10:23 AM, Maxime Cowez <maxime.co...@gmail.com> wrote: > > > I'm no mobile expert so I don't know about other components, but I found > > myself rewriting a desktop version of Callout and CalloutButton just last > > week. > > Bear in mind that functionality may somewhat differ, especially when it > > comes to user interaction. For instance my desktop CalloutButton will pop > > the Callout on mouse rollover or click (can be configured), whereas the > > mobile version reacts to touch events (obviously). > > > > > > On Wed, Nov 21, 2012 at 3:41 PM, Antonio Ortiz <zenk...@hotmail.com> > wrote: > > > >> 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 > >> > >> >
