Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of apostolache.andrei@gmail.com
 designates 209.85.212.47 as permitted sender)
Received-SPF: pass (google.com: domain of apostolache.andrei@gmail.com
 designates 10.52.76.196 as permitted sender) client-ip=10.52.76.196;
MIME-Version: 1.0
In-Reply-To: 
 <CAHx6CxiGhDn=c66kOZZLpuxUsc-QP_58ttdQuJnVgNMJ_roodA@mail.gmail.com>
References: <992CCDCF-1DBC-4B94-AF4A-685A95AA6B9E@yahoo.com>
	<4F4D7893.3030908@leichtgewicht.at>
	<696DFB9E-55DB-4713-B825-02252BEC6D99@yahoo.com>
	<CAO0WCdv2pj6xD93f3egyu0b+A8mM7MvaOWK0HPQ8H4h+_SZdtQ@mail.gmail.com>
	<CAHx6CxiGhDn=c66kOZZLpuxUsc-QP_58ttdQuJnVgNMJ_roodA@mail.gmail.com>
Date: Wed, 29 Feb 2012 09:51:30 +0000
Message-ID: 
 <CAO0WCdugjfB_3FVsjX7Wu=_4h1R4TSwPduXRm1ROoy2d2-Fytw@mail.gmail.com>
Subject: Re: Desktop, mobile...tv/bluray
From: andrei apostolache <apostolache.andrei@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec5015d07b24fe904ba174957

--bcaec5015d07b24fe904ba174957
Content-Type: text/plain; charset=UTF-8

To have a tooltip on disable can be made by creating a custom button skin
or an custom button, which is not that hard.
I'm thinking of generic components, which you either use mx components and
lose performance, or build your own spark component.
One of the spark advantages was that couple of mx components now are
redundant (mx:Repeater can easily be a list with an itemRenderer). But, as
I point in my previous mail, is quite hard to skin the existing calendar to
fit both mobile and web development (and is quite easy and fast to build a
component that has the behavior of the calendar from Android 4, again, is
just a simple list with an item renderer and a tile layout).

On Wed, Feb 29, 2012 at 9:39 AM, manish sharma <minisharma17@gmail.com>wrote:

> Yup! I agreed that using mx with spark is not a good decision but there are
> some lack of functionality in spark components which is available in mx.
> i.e. in a simple spark button, you are not able to see tool-tip while it is
> disabled.
>
> so many developers has to use mx with spark due to these some lack of
> functionality.
>
> Thanks & Regards* **?*
> *MANISH SHARMA*
>
>
>
>
> On Wed, Feb 29, 2012 at 3:02 PM, andrei apostolache <
> apostolache.andrei@gmail.com> wrote:
>
> > We can start migrating components from mx to spark. At work we already
> > built something close to an Accordion, or a simpler and easier to skin
> > Calendar, suitable for mobile devices.
> > Anyone knows that using mx with spark is not a good decision.
> >
> >
> > On Wed, Feb 29, 2012 at 8:08 AM, Ariel Jakobovits <arieljake@yahoo.com
> > >wrote:
> >
> > > Thanks for the support Martin but some compatriots to work with me is
> > what
> > > I seek.
> > >
> > > Ariel Jakobovits
> > > ajakobov@adobe.com
> > > 650-350-0282
> > >
> > > On Feb 28, 2012, at 5:00 PM, Martin Heidegger <mh@leichtgewicht.at>
> > wrote:
> > >
> > > > On 29/02/2012 09:36, Ariel Jakobovits wrote:
> > > >> We have a list of components for desktop, and an emerging list of
> > > components designed for mobile. Anyone working with even lower power tv
> > and
> > > blueray devices that could benefit from even more lightweight
> components?
> > > > Who would not benefit of more components?
> > > >
> > > > yours
> > > > Martin.
> > >
> >
>

--bcaec5015d07b24fe904ba174957--