Comments on: Migrating From Flex 3 to Flash Builder 4: mx.core.Application

By: Ved

Ved — Mon, 04 Apr 2011 03:19:05 +0000

Thank you very much! o/

By: Jonathan Campos

Jonathan Campos — Fri, 12 Nov 2010 18:52:00 +0000

@jucelio odd, have you tried pulling the parameters into an object and seeing if they exist?

By: Jucelio

Jucelio — Fri, 12 Nov 2010 16:46:54 +0000

how to use FlexGlobals to get URL parameters.

In deprecated version was:

var filename:String = Application.application.parameters.filename;

but this mode don’t work in flex 4.1.

How i do it?

By: Jonathan Campos

Jonathan Campos — Wed, 29 Sep 2010 14:02:13 +0000

I'm not sure what your issue is. You can still use all the fx3 components that you previously used in your fx4 applications. If you are needing to add these styles to your components you can either skin them or you can extend the components and add the styles. Please let me know more about the issues you are having.

By: Nitika Agarwal

Nitika Agarwal — Wed, 29 Sep 2010 06:42:51 +0000

Hi,

I am Nitika Agarwal. Even I am working on flex and shifting my entire application from flex 3.5 to Flex 4.0. Your blog has been really helpful.

I am using lots of styling for my components which I cannot afford to change now because its a huge application and its client dependent. So I cannot change the look and field of it. I need to workaround of some styles for some controls like TextInput, Checkbox, Button. Please can you help me. Following is the list of controls for which I need a workaround.

Button – > fillColor, fillApha

Canvas -> borderThickness

ComboBox -> borderColor, fillColor, fillApha

TextArea -> backgroundColor, backgroundAlpha, cornerRadius

TextInput -> backgroundColor, backgroundAlpha,

All these properties are not allowed in mxml components and they are giving warnings in CSS files also. I have included namespaces also in the beginning of CSS file as:

@namespace “http://www.adobe.com/2006/mxml”;

@namespace mx “library://ns.adobe.com/flex/mx”;

@namespace fx “library://ns.adobe.com/flex/spark”;

@namespace flexlib “http://code.google.com/p/flexlib/”;

But it still gives the warnings and UI is not same as before. I am using FLex $ SDK with MX+Spark component set and Flex compatibility mode is unchecked.

Please help.

Thanks
Nitika

By: jeff

jeff — Mon, 26 Apr 2010 21:59:22 +0000

yup makes sense. may be a good time for me to get into as3signals.

By: Jonathan Campos

Jonathan Campos — Fri, 23 Apr 2010 21:56:42 +0000

@jeff For that the answer is simple, use events. The component shouldn’t be calling functions of its parent. Instead it should release an event that says “login” and the main event will be listening for that event. When the event handler receives the event then it will be time for the main application to handle it’s logic and make state changes as necessary.

HTH

By: jeff

jeff — Fri, 23 Apr 2010 21:51:26 +0000

Maybe the problem statement can be best summarized by saying ‘ How to best call functions in parent app mxml file from components?’

By: jeff

jeff — Fri, 23 Apr 2010 21:50:31 +0000

The specific example I am taking about is having a LoginScreen (which is an mxml component) that checks to see if you are logged in, then will change the application state (in the main application MXML file) to show a datagrid (another separate MXML component file). Just trying to work through best practices on how to architect my app, how to separate it into different parts, where to have the actionscript etc…

code example (simplifying my problem, 2 components trying to change app currentState) here:

http://www.jeffguthrie.com/dl/temp/StateManagment.fxp.zip

By: Jonathan Campos

Jonathan Campos — Fri, 23 Apr 2010 17:28:57 +0000

Also, think about using events more. If you are referencing your application in a component to execute a function, more than likely you need to make an event that the component releases, then the application’s event handlers can handle that event for the action that took place.