Hi Lee,
I have ported an application from Flex 3 to Flex 4 and here are the points I
can remember:
- The good news is you don't need to replace the halo components with
their spark equivalents at the beginning
- You should use the Spark theme and correct any errors to be ready to go
with Flex 4 skinning
- Some styles are not supported anymore with Spark and need to be handled
differently
- Where you need containers with borders and background colors/images use
the spark BorderContainer (bg colors don't work with Canvas, that was the
case for me, I don't know if this is general)
- You will need to add namespaces for styles, for the beginning you can
simply define the mx namspace as the default namespace:
- @namespace library://ns.adobe.com/flex/mx;
- You must change all StyleManager references with styleManager (new
property of UIComponent)
- Don't reference modules by class name, use interfaces instead. For
example if you have a module called MyModule and load it with a ModuleLoader
loader, don't do var module:MyModule = loader.child as MyModule to
access it. Define an interface, i.e. IMyModule, make MyModule implement it
and do var module:IMyModule = loader.child as IMyModule. Otherwise you can
have many strange runtime errors. For the start you can also disable per
module styles with the compiler option '-isolate-styles=false' until you
have finished correcting these module issues.
- You have to use the new syntax for states and transitions. Always use
the spark transitions ans effects as they work much better than the halo
ones.
I think that's it for now!
I hope it helps,
Haykel Ben Jemia
Allmas
Web RIA Development
http://www.allmas-tn.com
On Fri, Apr 23, 2010 at 12:54 PM, Lee Jenkins l...@datatrakpos.com wrote:
Anyone know of significant gotchas when going from Flex 3 to Flex 4?
Thanks,
--
Warm Regards,
Lee
