On 11/21/12 6:30 AM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> wrote:
> 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?
>
Justin already moved BusyIndicator from mobile to spark.swc. You are
welcome to move others as long as they don't require touch APIs or other
mobile infrastructure.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
