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
