You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Carlos Rovira <ca...@codeoscopic.com> on 2012/11/21 15:30:27 UTC
Flex Mobile components in desktop/browser applications
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
Re: Flex Mobile components in desktop/browser applications
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
Which combinations are you missing?
-Nick
On Wed, Nov 21, 2012 at 10:09 AM, FRANKLIN GARZON <fg...@hotmail.com>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 some scenarios.
>
> Franklin Garzón
>
> Regional Development Manager
>
> MCITP Microsoft SQLServer
>
>
> *Si el hombre dejara de aprender entonces dejaría de existir*
>
> 094496862
>
>
> > From: zenkai_@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 15:30:27 +0100
> > > Subject: Flex Mobile components in desktop/browser applications
> > > From: carlos.rovira@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
> >
>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Alex Harui <ah...@adobe.com>.
On 11/21/12 7:09 AM, "FRANKLIN GARZON" <fg...@hotmail.com> 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't have control over that.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
RE: Flex Mobile components in desktop/browser applications
Posted by FRANKLIN GARZON <fg...@hotmail.com>.
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 some scenarios.
Franklin Garzón
Regional Development Manager
MCITP Microsoft SQLServer
*Si el hombre dejara de aprender entonces dejaría de existir*
094496862
> From: zenkai_@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 15:30:27 +0100
> > Subject: Flex Mobile components in desktop/browser applications
> > From: carlos.rovira@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
>
Re: Flex Mobile components in desktop/browser applications
Posted by Michael Schmalle <ap...@teotigraphix.com>.
Quoting Maxime Cowez <ma...@gmail.com>:
>> 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 CallOut will always appear underneath the Button and
> horizontally centered to the Button's center. The mobile CallOutButton has
> a lot more options.
We always program what we need. So offering it up intact, you never
know who will come and refine the edges.
The mobile callout is insanely complicated as well.
Mike
> On Thu, Dec 20, 2012 at 3:00 PM, Marcus Fritze <marcus.fritze@googlemail.com
>> wrote:
>
>> @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 <ma...@gmail.com>:
>>
>> > 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 <ze...@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.rovira@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
>> >>
>> >>
>>
>>
>
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
Re: Flex Mobile components in desktop/browser applications
Posted by Marcus Fritze <ma...@googlemail.com>.
Thank you Maxime. I will look into it.
Am 20.12.2012 um 22:34 schrieb Maxime Cowez <ma...@gmail.com>:
> @Marcus Here you go:
> https://github.com/RIAstar/CallOutFx
>
> It's not much to look at, but it's a starting point.
>
> @Mark That's right. But I used SkinnablePopUpContainer, which ads the
> flexibility of Spark skinning.
>
> Max
>
>
> On Thu, Dec 20, 2012 at 4:26 PM, Kessler CTR Mark J <
> mark.kessler.ctr@usmc.mil> wrote:
>
>>
>> If you wanted to build off a previous base for the popup with some
>> options, you could create a sub-component off of the "s:PopUpAnchor". It
>> works like a callout but is just a invisible container. Works great for
>> contextual overlays n such.
>>
>> -Mark
>>
>> -----Original Message-----
>> From: Maxime Cowez [mailto:maxime.cowez@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 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 CallOut will always appear underneath the Button and
>> horizontally centered to the Button's center. The mobile CallOutButton has
>> a lot more options.
>>
>>
>> On Thu, Dec 20, 2012 at 3:00 PM, Marcus Fritze <
>> marcus.fritze@googlemail.com
>>> wrote:
>>
>>> @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 <ma...@gmail.com>:
>>>
>>>> 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 <ze...@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.rovira@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
>>>>>
>>>>>
>>>
>>>
>>
RE: [Component] Spacer
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Good point besides the general sizing/measuring I am wasting the rest... it simplifies it a little too. I don't use the spacers often, but I do use them to solve quick layouts for clients who must have a things displayed in a certain way.
Class:
//Declare package.
package spark.components
{
import spark.primitives.supportClasses.GraphicElement;
//Create child class of the GraphicElement class.
public class Spacer extends GraphicElement
{
//----------------------------------------
// Constructor
//----------------------------------------
public function Spacer()
{
super();
}
}
}
-Mark
-----Original Message-----
From: Maxime Cowez [mailto:maxime.cowez@gmail.com]
Sent: Friday, December 21, 2012 10:50
To: flex-dev@incubator.apache.org
Subject: Re: [Component] Spacer
@Mark Instead of Rect, you'd better use GraphicElement directly (Rect
extends FilledElement extends StrokedElement extends GraphicElement). I
suppose the performance should be better than that of mx:Spacer because
that inherits from UIComponent and GraphicElement does not. Though I think
the gain would be marginal since you typically don't use Spacers all over
the place.
That said, I remember some discussion on this list on the topic of
composing behaviours into components rather than inheriting them. A Spacer
would in that case only have the measuring/sizing behaviour and nothing
more. Don't know whether anyone has made any progress in this field though.
@Jeffry I suppose that in time we may want to drop the mx components or at
least give a developer the option to only target the Spark component set.
In that case, you would require a complete Spark component set, containing
even such trivial components like a Spacer.
Re: [Component] Spacer
Posted by Maxime Cowez <ma...@gmail.com>.
@Mark Instead of Rect, you'd better use GraphicElement directly (Rect
extends FilledElement extends StrokedElement extends GraphicElement). I
suppose the performance should be better than that of mx:Spacer because
that inherits from UIComponent and GraphicElement does not. Though I think
the gain would be marginal since you typically don't use Spacers all over
the place.
That said, I remember some discussion on this list on the topic of
composing behaviours into components rather than inheriting them. A Spacer
would in that case only have the measuring/sizing behaviour and nothing
more. Don't know whether anyone has made any progress in this field though.
@Jeffry I suppose that in time we may want to drop the mx components or at
least give a developer the option to only target the Spark component set.
In that case, you would require a complete Spark component set, containing
even such trivial components like a Spacer.
On Fri, Dec 21, 2012 at 3:59 PM, Kessler CTR Mark J <
mark.kessler.ctr@usmc.mil> wrote:
> It's not really any different that the MX version, it just felt like it
> helped to complete the spark component set. That and it's only like half a
> dozen lines or so lol.
>
> -----Original Message-----
> From: Jeffry Houser [mailto:jeffry@dot-com-it.com]
> Sent: Friday, December 21, 2012 9:52
> To: flex-dev@incubator.apache.org
> Subject: Re: [Component] Spacer
>
>
> My personal opinion is that the MX Spacer does not need to be
> re-written as a Spark Component. It won't game any benefit from being
> implemented using the Spark Architecture as it has no visual display.
>
> Is there a reason the MX Spacer won't work for you? Would extending
> Rect be more efficient?
>
> On 12/21/2012 9:44 AM, Kessler CTR Mark J wrote:
> > Just curious if we could add a simple component that used to exist
> in MX but not in Spark. The spacer component was just a simple UI
> extension. We can do the exact same thing now with the s:Rect (primitive),
> but it doesn't have an intuitive name. I think it would be nice to add the
> spacer back in.
> >
> >
> >
> > <s:Rect width="100%" />
> >
> > --Same as--
> >
> > <s:Spacer width="100%" />
> >
> >
> > Class:
> >
> > //Declare package.
> > package spark.components
> > {
> > //Create child class of the Rect class.
> > public class Spacer extends Rect
> > {
> > //----------------------------------------
> > // Constructor
> > //----------------------------------------
> >
> > public function Spacer()
> > {
> > super();
> > }
> >
> > }
> >
> > }
> >
> >
> >
> > -Mark
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> 203-379-0773
> --
> http://www.flextras.com?c=104
> UI Flex Components: Tested! Supported! Ready!
> --
> http://www.theflexshow.com
> http://www.jeffryhouser.com
> http://www.asktheflexpert.com
> --
> Part of the DotComIt Brain Trust
>
>
RE: [Component] Spacer
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
It's not really any different that the MX version, it just felt like it helped to complete the spark component set. That and it's only like half a dozen lines or so lol.
-----Original Message-----
From: Jeffry Houser [mailto:jeffry@dot-com-it.com]
Sent: Friday, December 21, 2012 9:52
To: flex-dev@incubator.apache.org
Subject: Re: [Component] Spacer
My personal opinion is that the MX Spacer does not need to be
re-written as a Spark Component. It won't game any benefit from being
implemented using the Spark Architecture as it has no visual display.
Is there a reason the MX Spacer won't work for you? Would extending
Rect be more efficient?
On 12/21/2012 9:44 AM, Kessler CTR Mark J wrote:
> Just curious if we could add a simple component that used to exist in MX but not in Spark. The spacer component was just a simple UI extension. We can do the exact same thing now with the s:Rect (primitive), but it doesn't have an intuitive name. I think it would be nice to add the spacer back in.
>
>
>
> <s:Rect width="100%" />
>
> --Same as--
>
> <s:Spacer width="100%" />
>
>
> Class:
>
> //Declare package.
> package spark.components
> {
> //Create child class of the Rect class.
> public class Spacer extends Rect
> {
> //----------------------------------------
> // Constructor
> //----------------------------------------
>
> public function Spacer()
> {
> super();
> }
>
> }
>
> }
>
>
>
> -Mark
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [Component] Spacer
Posted by Jeffry Houser <je...@dot-com-it.com>.
My personal opinion is that the MX Spacer does not need to be
re-written as a Spark Component. It won't game any benefit from being
implemented using the Spark Architecture as it has no visual display.
Is there a reason the MX Spacer won't work for you? Would extending
Rect be more efficient?
On 12/21/2012 9:44 AM, Kessler CTR Mark J wrote:
> Just curious if we could add a simple component that used to exist in MX but not in Spark. The spacer component was just a simple UI extension. We can do the exact same thing now with the s:Rect (primitive), but it doesn't have an intuitive name. I think it would be nice to add the spacer back in.
>
>
>
> <s:Rect width="100%" />
>
> --Same as--
>
> <s:Spacer width="100%" />
>
>
> Class:
>
> //Declare package.
> package spark.components
> {
> //Create child class of the Rect class.
> public class Spacer extends Rect
> {
> //----------------------------------------
> // Constructor
> //----------------------------------------
>
> public function Spacer()
> {
> super();
> }
>
> }
>
> }
>
>
>
> -Mark
--
Jeffry Houser
Technical Entrepreneur
203-379-0773
--
http://www.flextras.com?c=104
UI Flex Components: Tested! Supported! Ready!
--
http://www.theflexshow.com
http://www.jeffryhouser.com
http://www.asktheflexpert.com
--
Part of the DotComIt Brain Trust
Re: [Component] Spacer
Posted by Carol Frampton <cf...@adobe.com>.
On 12/21/12 12 :08PM, "Alex Harui" <ah...@adobe.com> wrote:
>Don't you still need a class to have the name Spacer in ActionScript? I
>think the manifest trick only works in MXML.
>
True.
Carol
>
>On 12/21/12 9:05 AM, "Carol Frampton" <cf...@adobe.com> wrote:
>
>> I'm not commenting on whether or not there should be a s:Spacer but you
>> don't need a new class - you just need a new manifest entry to do the
>> mapping. If you look in frameworks/spark-manifest.com you will see
>>others
>> there.
>>
>> Carol
>>
>> On 12/21/12 9 :44AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>> wrote:
>>
>>> Just curious if we could add a simple component that used to exist in
>>> MX but not in Spark. The spacer component was just a simple UI
>>> extension. We can do the exact same thing now with the s:Rect
>>> (primitive), but it doesn't have an intuitive name. I think it would
>>>be
>>> nice to add the spacer back in.
>>>
>>>
>>>
>>> <s:Rect width="100%" />
>>>
>>> --Same as--
>>>
>>> <s:Spacer width="100%" />
>>>
>>>
>>> Class:
>>>
>>> //Declare package.
>>> package spark.components
>>> {
>>> //Create child class of the Rect class.
>>> public class Spacer extends Rect
>>> {
>>> //----------------------------------------
>>> // Constructor
>>> //----------------------------------------
>>>
>>> public function Spacer()
>>> {
>>> super();
>>> }
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> -Mark
>>
>
>--
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>
Re: [Component] Spacer
Posted by Alex Harui <ah...@adobe.com>.
Don't you still need a class to have the name Spacer in ActionScript? I
think the manifest trick only works in MXML.
On 12/21/12 9:05 AM, "Carol Frampton" <cf...@adobe.com> wrote:
> I'm not commenting on whether or not there should be a s:Spacer but you
> don't need a new class - you just need a new manifest entry to do the
> mapping. If you look in frameworks/spark-manifest.com you will see others
> there.
>
> Carol
>
> On 12/21/12 9 :44AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> wrote:
>
>> Just curious if we could add a simple component that used to exist in
>> MX but not in Spark. The spacer component was just a simple UI
>> extension. We can do the exact same thing now with the s:Rect
>> (primitive), but it doesn't have an intuitive name. I think it would be
>> nice to add the spacer back in.
>>
>>
>>
>> <s:Rect width="100%" />
>>
>> --Same as--
>>
>> <s:Spacer width="100%" />
>>
>>
>> Class:
>>
>> //Declare package.
>> package spark.components
>> {
>> //Create child class of the Rect class.
>> public class Spacer extends Rect
>> {
>> //----------------------------------------
>> // Constructor
>> //----------------------------------------
>>
>> public function Spacer()
>> {
>> super();
>> }
>>
>> }
>>
>> }
>>
>>
>>
>> -Mark
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: [Component] Spacer
Posted by Carol Frampton <cf...@adobe.com>.
I'm not commenting on whether or not there should be a s:Spacer but you
don't need a new class - you just need a new manifest entry to do the
mapping. If you look in frameworks/spark-manifest.com you will see others
there.
Carol
On 12/21/12 9 :44AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:
> Just curious if we could add a simple component that used to exist in
>MX but not in Spark. The spacer component was just a simple UI
>extension. We can do the exact same thing now with the s:Rect
>(primitive), but it doesn't have an intuitive name. I think it would be
>nice to add the spacer back in.
>
>
>
><s:Rect width="100%" />
>
>--Same as--
>
><s:Spacer width="100%" />
>
>
>Class:
>
>//Declare package.
>package spark.components
>{
> //Create child class of the Rect class.
> public class Spacer extends Rect
> {
> //----------------------------------------
> // Constructor
> //----------------------------------------
>
> public function Spacer()
> {
> super();
> }
>
> }
>
>}
>
>
>
>-Mark
[Component] Spacer
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Just curious if we could add a simple component that used to exist in MX but not in Spark. The spacer component was just a simple UI extension. We can do the exact same thing now with the s:Rect (primitive), but it doesn't have an intuitive name. I think it would be nice to add the spacer back in.
<s:Rect width="100%" />
--Same as--
<s:Spacer width="100%" />
Class:
//Declare package.
package spark.components
{
//Create child class of the Rect class.
public class Spacer extends Rect
{
//----------------------------------------
// Constructor
//----------------------------------------
public function Spacer()
{
super();
}
}
}
-Mark
RE: Flex Mobile components in desktop/browser applications
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Sounds good, look forward to trying it out when I get a moment.
-Mark
-----Original Message-----
From: Maxime Cowez [mailto:maxime.cowez@gmail.com]
Sent: Thursday, December 20, 2012 16:34
To: flex-dev@incubator.apache.org
Subject: Re: Flex Mobile components in desktop/browser applications
@Marcus Here you go:
https://github.com/RIAstar/CallOutFx
It's not much to look at, but it's a starting point.
@Mark That's right. But I used SkinnablePopUpContainer, which ads the
flexibility of Spark skinning.
Max
Re: Flex Mobile components in desktop/browser applications
Posted by Maxime Cowez <ma...@gmail.com>.
@Marcus Here you go:
https://github.com/RIAstar/CallOutFx
It's not much to look at, but it's a starting point.
@Mark That's right. But I used SkinnablePopUpContainer, which ads the
flexibility of Spark skinning.
Max
On Thu, Dec 20, 2012 at 4:26 PM, Kessler CTR Mark J <
mark.kessler.ctr@usmc.mil> wrote:
>
> If you wanted to build off a previous base for the popup with some
> options, you could create a sub-component off of the "s:PopUpAnchor". It
> works like a callout but is just a invisible container. Works great for
> contextual overlays n such.
>
> -Mark
>
> -----Original Message-----
> From: Maxime Cowez [mailto:maxime.cowez@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 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 CallOut will always appear underneath the Button and
> horizontally centered to the Button's center. The mobile CallOutButton has
> a lot more options.
>
>
> On Thu, Dec 20, 2012 at 3:00 PM, Marcus Fritze <
> marcus.fritze@googlemail.com
> > wrote:
>
> > @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 <ma...@gmail.com>:
> >
> > > 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 <ze...@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.rovira@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
> > >>
> > >>
> >
> >
>
RE: Flex Mobile components in desktop/browser applications
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
If you wanted to build off a previous base for the popup with some options, you could create a sub-component off of the "s:PopUpAnchor". It works like a callout but is just a invisible container. Works great for contextual overlays n such.
-Mark
-----Original Message-----
From: Maxime Cowez [mailto:maxime.cowez@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 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 CallOut will always appear underneath the Button and
horizontally centered to the Button's center. The mobile CallOutButton has
a lot more options.
On Thu, Dec 20, 2012 at 3:00 PM, Marcus Fritze <marcus.fritze@googlemail.com
> wrote:
> @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 <ma...@gmail.com>:
>
> > 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 <ze...@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.rovira@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
> >>
> >>
>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Maxime Cowez <ma...@gmail.com>.
> 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 CallOut will always appear underneath the Button and
horizontally centered to the Button's center. The mobile CallOutButton has
a lot more options.
On Thu, Dec 20, 2012 at 3:00 PM, Marcus Fritze <marcus.fritze@googlemail.com
> wrote:
> @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 <ma...@gmail.com>:
>
> > 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 <ze...@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.rovira@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
> >>
> >>
>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Marcus Fritze <ma...@googlemail.com>.
@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 <ma...@gmail.com>:
> 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 <ze...@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.rovira@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
>>
>>
Re: Flex Mobile components in desktop/browser applications
Posted by Cosma Colanicchia <co...@gmail.com>.
@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 <sc...@mac.com>
> Same here the week before last
>
> On Nov 21, 2012, at 10:23 AM, Maxime Cowez <ma...@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 <ze...@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.rovira@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
> >>
> >>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Scott Rowe <sc...@mac.com>.
Same here the week before last
On Nov 21, 2012, at 10:23 AM, Maxime Cowez <ma...@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 <ze...@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.rovira@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
>>
>>
Re: Flex Mobile components in desktop/browser applications
Posted by Maxime Cowez <ma...@gmail.com>.
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 <ze...@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.rovira@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
>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Alex Harui <ah...@adobe.com>.
On 11/21/12 7:08 AM, "Cosma Colanicchia" <co...@gmail.com> 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 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?
>
Yup, as long as you do it in a way that doesn't require functionality from
the latest runtimes. Folks still want to see Flex run on older players, all
the way back to 10.x
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Flex Mobile components in desktop/browser applications
Posted by Cosma Colanicchia <co...@gmail.com>.
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 <ze...@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.rovira@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
>
>
RE: Flex Mobile components in desktop/browser applications
Posted by Antonio Ortiz <ze...@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.rovira@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
Re: Flex Mobile components in desktop/browser applications
Posted by Cosma Colanicchia <co...@gmail.com>.
@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
supported on desktop and browser runtimes, probably reports an incorrect
value (at least on Windows, it seems locked to 72dpi)..
[1] http://www.adobe.com/devnet/flash/articles/multitouch_gestures.html
[2]
http://help.adobe.com/en_US/as3/dev/WS1ca064e08d7aa93023c59dfc1257b16a3d6-7ffe.html
[3]
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/Capabilities.html#screenDPI
2012/11/21 Harbs <ha...@gmail.com>
> 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 touch APIs or other
> > mobile infrastructure.
>
>
Re: Flex Mobile components in desktop/browser applications
Posted by Harbs <ha...@gmail.com>.
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 touch APIs or other
> mobile infrastructure.
Re: Flex Mobile components in desktop/browser applications
Posted by Alex Harui <ah...@adobe.com>.
On 11/21/12 6:30 AM, "Carlos Rovira" <ca...@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