incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxime Cowez <maxime.co...@gmail.com>
Subject Re: Flex Mobile components in desktop/browser applications
Date Thu, 20 Dec 2012 21:34:21 GMT
@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 <maxime.cowez@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 <zenkai_@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
> > >>
> > >>
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message