/* note:
to avoid to create a hard reference to Application.application
we get the class by reflection
*/ var appclass:Object = getDefinitionByName("mx.core::Application"); if( appclass.application != null) {
_app = appclass.application; } /* Flex 4:
Use of Appliction.application has been replaced by
FlexGlobals.topLevelApplication
this will make tracking in flex 4 possible
*/ else {
appclass = getDefinitionByName("mx.core::FlexGlobals");
_app = appclass.topLevelApplication }
_app.addEventListener(Event.ADDED_TO_STAGE, _factory );
So now it works!
The compiled version of the above can be downloaded here. -happy coding
A good friend and colleague of mine, Paw Suddergaard, pointed me towards PngGauntlet for optimizing png’s.
I just gave it a shot and saved the users for around 100k download on one large png. This is an interesting tool to put in your toolbox for the optimization part of your development cycle.
I recently made a Flex application that stores information in regular cookies. I found this util that enables you to set cookies from within Flex by injecting Java Script into the wrapper. You can get it here.
I then proceeded to test my application, and everything was smooth sailing. That is, until I switched primary browser from FF to Chrome. Then all of a sudden my cookies was not working in my local test environment, but fine in the deployed solution.
The root cause of this I found out is a deliberate decision from Google to not enable cookies from local files. I did not bother to read why that is, but found their solution to the problem: Include the following sting as a parameter to chrome: –enable-file-cookies
In these days of rapid development, and increasingly complex RIA applications, quality of code is more important than ever. Being complex applications, means that tracking down and fixing bugs in your system will be increasingly time consuming.
There are a lot of ways to help your self to write better quality code. One of such is to select a framework and adhere to the rules of that framework, thereby ensuring that your code is consistent throughout the entire application and equally important, consistent throughout the entire development team. I will not go in to the whole framework debate in this post, just quickly mention that for my part the PureMVC framwork has proven tedious and complicated to use in a consistent fashion..
Another measure you can take, to ensure higher code quality is code review. This technique ensures that no sloppy code enters production. This however can be a very tedious task if performed manually. It has also dawned on me as being (at least for most part of your day to day coding scenarios) somewhat stupid, as the quality of the code should not be up for subjective judgment rather analyzed by machines, again to ensure quality and to have unbiased opinions on the quality.
Here at Hello, we have been trying the FlexPMD for hudson/ teamcity to render some form of quality output when the CI process is run. This gives us measurables for the current state of the code at every build (triggered in our case by SVN commits), and reduces the code-review to looking at a list of issues detected by the FlexPMD.
Now FlexPMD has been released as an eclipse plugin. This is GREAT news! It means, that every developer can get feedback on every build about the state of the code he is currently working on. The impact is IMHO much greater than having the feedback posted on a results site for a given CI server, as it tends to be corrected faster when the feedback is provided in context to what you are doing. Even more important is to have this kind of feedback available to you very early in the development process, so that errors done at the early state doesn’t multiply in the system during development.
So without further ado: The plugin can be downloaded from adobe here.
I’ve been working a bit with LCDS, and have had a few issues that I would like to share, so that you may save some of the time I’ve wasted goofing around
First off. If you want to run you LCDS on a windows machine, but as a service ( meaning that the server keeps running after you log off the system; the case for server setups ) there is a service.bat file in the \lcds\tomcat\bin, you can use to install a LCDS service on your system. Usage is: “service install [service name]” where you obviously replace the [service name] with a name of your choosing.
That service can then be started in the service config, or just set to automatic.
Second. If you wish to develop against a server other than localhost, you just type in that server info, in the initial project server configuration page.
In my case an example is:
This however requires for you to have set sharing for the folder containing the project on the particular server.
Secondly, in order for flash builder to be able to publish the datamodel to your server you need to set the JDBC Datasource in the general properties for the model. In my case the string is: java:/comp/env/jdbc/jukebox. The connection string can be found here:
I hope this helps those of you who wish to do development of LCDS applications on another machine than localhost.
Today I allocated my self some time to look into things on my ever growing todo list. I’ve been lookin at the Spicelabs Flex framework called Parsley. It looks promising, and several people state, that it is very similar to Swiz, so that developers coming from that framework should be quick to catch up!
Information about the framework can be found here.
I will be finding time to look further in to this exiting framework very soon!
