Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 09460DECC for ; Thu, 20 Dec 2012 15:15:29 +0000 (UTC) Received: (qmail 18792 invoked by uid 500); 20 Dec 2012 15:15:28 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 18726 invoked by uid 500); 20 Dec 2012 15:15:28 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 18714 invoked by uid 99); 20 Dec 2012 15:15:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 15:15:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [69.167.147.50] (HELO franklin.liquidweb.com) (69.167.147.50) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 15:15:23 +0000 Received: from localhost ([127.0.0.1]:48905) by franklin.liquidweb.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1Tlhpr-0003jS-8p for flex-dev@incubator.apache.org; Thu, 20 Dec 2012 10:14:59 -0500 Received: from 71.161.204.120 ([71.161.204.120]) by franklin.liquidweb.com (Horde Framework) with HTTP; Thu, 20 Dec 2012 10:14:59 -0500 Message-ID: <20121220101459.10217f07b6vqnk37@franklin.liquidweb.com> Date: Thu, 20 Dec 2012 10:14:59 -0500 From: Michael Schmalle To: flex-dev@incubator.apache.org Subject: Re: Flex Mobile components in desktop/browser applications References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.8) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - franklin.liquidweb.com X-AntiAbuse: Original Domain - incubator.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - teotigraphix.com X-Get-Message-Sender-Via: franklin.liquidweb.com: authenticated_id: teotigra/from_h X-Source: X-Source-Args: X-Source-Dir: X-Virus-Checked: Checked by ClamAV on apache.org 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 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 > 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 : >> >> > 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 >> 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