Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of marcus.fritze@googlemail.com
 designates 74.125.83.47 as permitted sender)
References: <rqbg42ctv09d14haq1pm289e.1327516753036@email.android.com>
In-Reply-To: <rqbg42ctv09d14haq1pm289e.1327516753036@email.android.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <83079AC6-4D22-452A-9087-D35F3E8F2B89@googlemail.com>
Cc: Marcus Fritze <marcus.fritze@googlemail.com>
From: Fritze Marcus <marcus.fritze@googlemail.com>
Subject: Re: Port some mobile components to web
Date: Wed, 25 Jan 2012 19:52:49 +0100
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>

+1 for the callout

The callout is also very useful in a normal application.

Marcus Fritze

Am 25.01.2012 um 19:39 schrieb Tink <flex@tink.ws>:

> Hi Haykel
>=20
> I have some navigators in my whiteboard space as a proposal for web naviga=
tors with examples.
>=20
> You can use the 'mobile' component's on web as long as you include the SWC=
. Why a lot of them were put in a mobile specific SWC I don't know, but movi=
ng them ans creating some MXML based skins for them is something I'm interes=
ted in doing if the rest of the team agree.
>=20
> Tink
>=20
> Haykel BEN JEMIA <haykelbj@gmail.com> wrote:
>=20
>> I would suggest to port some of the mobile components to make them usable=

>> in web applications, especially the view navigators and some of the new
>> tablet components (callouts would be cool). I know it is possible to use
>> some of them in desktop applications, but why were they implemented for
>> mobile only in the first place and why they are not available for web?
>>=20
>> Haykel