I continue to be amazed that any serious software development company would
choose to use a development IDE that was released in 2011 and has not been
updated since 4.7 in 2012. It's a poor business decision, plain and simple,
IMHO.
A few years ago, after extensive research and frustration with
Erik,
FWIW we're not a "serious software development company", we're a shipping
company. I suspect most here are dealing with Flex as a legacy solution. I'm
certain that using legacy tooling in order to support legacy software isn't
rare. I'm also certain that it's foolish to comment on the
Hey Jeff:
Sorry, didn't mean to insult. My bad. Just that you led with...
"At my organization, we've used Flex for probably 10 years now and we have what
I think may be one of the largest Flex codebases (over 200k lines of source)."
If it quacks like a duck... LOL.
But I see your type of quest
I have just started to move an Adobe Flex 4.6.0 to Apache Flex, but cannot
get mx:VDividedBox or mx:DividedBox to be recognized. I built the sdk by
unzipping the Apache Flex 4.16.1 SDK, and then overlaying the AIR 27 SDK.
Is there something I am missing?
http://ns.adobe.com/mxml/2009";
