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.and...@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 <arielj...@yahoo.com > >wrote: > > > Thanks for the support Martin but some compatriots to work with me is > what > > I seek. > > > > Ariel Jakobovits > > ajako...@adobe.com > > 650-350-0282 > > > > On Feb 28, 2012, at 5:00 PM, Martin Heidegger <m...@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. > > >
