So far I have compatibility mode turned on and the Halo theme added. Working through the errors.
The latest is that I get a null pointer exception in HaloBorder
Main Thread (Suspended: TypeError: Error #1009: Cannot access a property or
method of a null object reference.)
mx.skins.halo::HaloBorder/get borderMetrics
mx.core::Container/get borderMetrics
mx.core::Container/get viewMetrics
mx.core::Container/get viewMetricsAndPadding
mx.containers.utilityClasses::BoxLayout/
http://www.adobe.com/2006/flex/mx/internal::widthPadding
mx.containers.utilityClasses::BoxLayout/measure
mx.containers::Box/measure
mx.core::UIComponent/measureSizes
mx.core::UIComponent/validateSize
mx.core::Container/validateSize
mx.managers::LayoutManager/validateSize
mx.managers::LayoutManager/doPhasedInstantiation
mx.managers::LayoutManager/doPhasedInstantiationCallback
This related question did not appear to get a response on the forums:
http://forums.adobe.com/message/3149760
Thanks for any tips.
On Mon, Oct 11, 2010 at 3:25 PM, Glenn Williams <gl...@tinylion.co.uk>wrote:
>
> [Attachment(s) <#12b9d6686db7c478_TopText> from Glenn Williams included
> below]
>
> hi
>
>
>
> I found it a simple process on a fairly large project we were working on.
>
>
>
> to just get it to compile you shouldn’t have any problems
>
>
>
> to then start adding spark.
>
>
>
> first change the application tag. <mx: <s: application
>
>
>
> that’s when the fun starts.
>
>
>
> the one thing I found useful to get your mx components looking how you
> expect, is to manually include the original halo css file. you can then use
> spark theme but still have any css of styling you’ve done on your mx
> components still work as you’d expect.
>
>
>
> I was about to start writing a list of ‘look outs’ but thought I’d have a
> look at your link first. it’s all in there, looks like a very good start
> anyway.
>
>
>
> our project was about 2500 source files and I think in total it was maybe a
> couple of days to have a spark application but, with all mx components and
> looking just like it was before the change. then it was just a matter of
> starting to replace some things.
>
>
>
> note. we did this as a test, the project was already complete and we used
> it to learn about the change from mx to s. it was quite simple (apart from
> needing to include the halo css default file by hand which caught us out.
> styles just weren’t doing what we expected, and as soon as we added the
> default.css from the halo directory all was well.
>
>
>
> One thing I will say – do it. Spark is in every way better.
>
>
>
> and once you have the luxury of starting a new project from scratch with
> the new spark architecture you’ll wonder how you ever managed without it.
> It’s a huge step forward in my opinion.
>
>
>
> it really is time to put flex 3 away and start enjoying the new framework.
> It’s wonderful to work with, and in all our tests just generally faster and
> more stable and uses less memory. In comparing the two there isn’t anything
> I miss about flex 3 when using flex 4. it’s worth the effort (well what
> little effort the change actually needs)
>
>
>
>
>
> if you have any trouble please feel free to email me off forum and we’ll
> help all we can.
>
>
>
> all the best
>
>
>
> glenn
>
>
>
>
>
> tiny*lion* development & design
>
>
>
>
>
> *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On
> Behalf Of *Richard Rodseth
> *Sent:* Monday, October 11, 2010 10:09 PM
> *To:* flexcoders@yahoogroups.com
> *Subject:* [flexcoders] Flex 3.5 to 4.1
>
>
>
>
>
> Can anyone give me a sense for how big an effort it is to port from Flex
> 3.6 to Flex 4 SDK, without (at first) taking advantage of any of the new
> features. In other words, just getting everything compiling and running as
> well as it did before, Halo components only.
>
> This recent article is helpful, but I'd like some more experience reports.
>
> http://www.adobe.com/devnet/flex/articles/flex3_to_flex4_transitioning.html
>
> Thanks
>
>
>
<<image001.jpg>>
