Comments on: The Flex 4 One-Step Migration Challenge

By: hasustorm

hasustorm — Tue, 23 Feb 2010 17:21:47 +0000

блядь дерьмо ебаное

By: unfortunate

unfortunate — Thu, 05 Nov 2009 06:29:56 +0000

I have a query, I import Flex 3 project into Flex 4 aka Flash BUilder 4 Beta 2, now my query is which componenet set flash will use, default Halo which I used in Flex 3 or Spark Components even without chanding the namespace. Namespcace is same: xmlns:mx=”http://www.adobe.com/2006/mxml”

pls help

By: dave

dave — Mon, 19 Oct 2009 19:41:59 +0000

Adobe is screwing us by not making Flex 3 to Flash Builder 4 import seamless and automatic. It’s that simple. How can they change all the packages and namespaces and not provide a migration utility. It pisses me off no end.

By: Bob Brubaker

Bob Brubaker — Sat, 03 Oct 2009 00:05:26 +0000

What is the current status of this initiative. It sounds like something that would be very useful.

By: Arnoud

Arnoud — Tue, 16 Jun 2009 03:59:05 +0000

Really needed? I dont know.
Covenient? Yesss!

By: takım elbise

takım elbise — Wed, 10 Jun 2009 08:42:11 +0000

thank yoı plp

By: Aral

Aral — Tue, 02 Jun 2009 11:54:24 +0000

Read Ben's latest retort here: http://blog.benstucki.net/?p=56. I've commented there.

By: Troy Gilbert

Troy Gilbert — Mon, 01 Jun 2009 20:23:21 +0000

I echo Ryan’s comment (and did so in the other thread and elsewhere). Where’s a concrete *example* of a migration pain? Please tell me you’ve actually done some migration work and encountered the pain, and that all of this hoo-haa isn’t based on simply your *expectation* of pain…

By: Ryan Campbell

Ryan Campbell — Mon, 01 Jun 2009 20:09:34 +0000

So you’ll spend time creating a logo for this post but no time showing real examples proving your complaints?

By: Aral Balkan - The change from Fx prefix to namespaces is an EPIC FAIL for Flex opportunity to concentrate on making Flex 3 to Flex 4 migration seamless

Sat, 30 May 2009 12:25:09 +0000

[...] to make Flex 3 to Flex 4 migration as easy as possible. As such, please read my follow-up post, The Flex 4 One-Step Migration Challenge and let’s try and make a list of the Flex 4 migration challenges for Flex 3 apps and try to address [...]