Sounds good, look forward to trying it out when I get a moment.
-Mark
-Original Message-
From: Maxime Cowez [mailto:maxime.co...@gmail.com]
Sent: Thursday, December 20, 2012 16:34
To: flex-dev@incubator.apache.org
Subject: Re: Flex Mobile components in desktop/browser applications
xime.co...@gmail.com]
>> Sent: Thursday, December 20, 2012 10:09
>> To: Marcus Fritze
>> Cc: flex-dev@incubator.apache.org
>> Subject: Re: Flex Mobile components in desktop/browser applications
>>
>>> Are you willing to share your code of your CallOutButton?
&g
l overlays n such.
>
> -Mark
>
> -Original Message-
> From: Maxime Cowez [mailto:maxime.co...@gmail.com]
> Sent: Thursday, December 20, 2012 10:09
> To: Marcus Fritze
> Cc: flex-dev@incubator.apache.org
> Subject: Re: Flex Mobile components in desktop/browser applicatio
om: Maxime Cowez [mailto:maxime.co...@gmail.com]
Sent: Thursday, December 20, 2012 10:09
To: Marcus Fritze
Cc: flex-dev@incubator.apache.org
Subject: Re: Flex Mobile components in desktop/browser applications
> Are you willing to share your code of your CallOutButton?
Sure, I'll try to set u
Quoting Maxime Cowez :
Are you willing to share your code of your CallOutButton?
Sure, I'll try to set up a repo on GitHub as soon as I find some time.
and maybe submit to the Apache Flex?
I'm afraid my implementation is a little bit too "ad hoc" for that. It was
created to serve one use ca
> Are you willing to share your code of your CallOutButton?
Sure, I'll try to set up a repo on GitHub as soon as I find some time.
> and maybe submit to the Apache Flex?
I'm afraid my implementation is a little bit too "ad hoc" for that. It was
created to serve one use case only.
For instance, the
@maxime
Are you willing to share your code of your CallOutButton and maybe submit to
the Apache Flex?
Thanks
Marcus
Am 21.11.2012 um 16:23 schrieb Maxime Cowez :
> I'm no mobile expert so I don't know about other components, but I found
> myself rewriting a desktop version of Callout and Call
@alex
I see, I haven't tried it but it should be ok: the docs states that touch
APIs are part of the Flash Player (since 10.1), see [1] and [2].
I think that the DPI scaling functions are part of the Flex components, but
they probably rely on the value of Capabilities.screenDPI [3] which, while
s
That's a good move. I recently wanted that in a web app. I ended up using an
embedded swf to play a busy animation…
Harbs
On Nov 21, 2012, at 7:19 PM, Alex Harui wrote:
> Justin already moved BusyIndicator from mobile to spark.swc. You are
> welcome to move others as long as they don't require
On 11/21/12 6:30 AM, "Carlos Rovira" 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
On 11/21/12 7:08 AM, "Cosma Colanicchia" wrote:
> 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 la
On 11/21/12 7:09 AM, "FRANKLIN GARZON" wrote:
>
> Also will be great in paralell way, if the customization of entry keyboard for
> mobile support more combinations, this will helpfuly for confort of client in
I think the keyboard types are part of the runtimes and not in Flex code, so
we don'
@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
kin
Same here the week before last
On Nov 21, 2012, at 10:23 AM, Maxime Cowez 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, e
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
>
> Franklin Garzón
>
> Regional Development Manager
>
> MCITP Microsoft SQLServer
>
>
> *Si el hombre dejara de aprender entonces dejaría de existir*
>
> 094496862
>
>
> > From: zenk...@hotmail.com
> > To: flex-dev@incubator.apache.org
> >
dejaría de existir*
094496862
> From: zenk...@hotmail.com
> To: flex-dev@incubator.apache.org
> Subject: RE: Flex Mobile components in desktop/browser applications
> Date: Wed, 21 Nov 2012 08:41:50 -0600
>
> It will be great... :)
>
> > Date: Wed, 21 Nov 2012
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
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, Ca
19 matches
Mail list logo
