Posted by Almost Noted on June 28, 2011
Posted by Almost Noted on June 25, 2011
I was checking adobe website after a long gap in time. And came across their PAYG option for their product Creative Suite 5.5 Master Collection. It is very convenient for people like me who can think twice before they buy CS 5.5 . Way to go Adobe!!
Posted by Almost Noted on September 24, 2009
Mogulus Technologies Pvt Ltd is hiring!! ..
Mogulus, headquatered in US, owns an excellent product called Livestream. Livestream is the most powerful live broadcast platform on the internet
Company/Product website :www.livestream.com
More about company :http://www.livestream.com/info/about
Page worth looking at :http://www.livestream.com/info/press
Company’s blog page:http://www.livestream.com/blog/
Below mentioned are the open positions
Senior Java Dev
Technical support Head
Please find the attached word ducument for more information .
The actual URL of the document is https://flexrays.files.wordpress.com/2009/09/mogulus_hiring_webdesign_dev_flex_java_techhead.doc
Mail your resume to firstname.lastname@example.org
Posted by Almost Noted on July 3, 2008
Error: An internal build error has occurred. Right-click for more information
I struggled finding the solution for this error. But you couldn’t guess!! the solution is very simple
Search for a switch statement without any cases. For example:
Remove that and recompile the application.
Boom!!!! The error disappears. It is as simple as that. I hope this is useful to you all.
Posted by Almost Noted on May 7, 2008
In this article I will be telling you how to creating a dynamically linked application i.e how to implement Flash Player cache feature by using RSLs with Flex Builder
But let us first know what is a statically linked application and a dynamically linked application
Statically linked application – Flex framework code and the application code will make the SWF file increasing the size of the SWF file
Dynamically linked application – Flex framework code will be added dynamically to the SWF code thus reducing its size
If you want to check the result of the above mentioned feature live the follow the steps
1. Create any flex application with some code
2. Get the true size of the application – Follow the steps
1. By default, Flex Builder adds debugging information to SWF files, so in order to see the true size of the application,
turn off the debugging information
2. To do this, add -debug=false to the Additional Compiler Arguments section of the Flex Compiler Properties dialog box
3. Check the size of the application by viewing the properties of the application’s SWF file created in the bin directory
Note down the size
4. Now go to Project Properties (right click on Flex project and select properties), then choose the Flex Build Path properties
and click the Library Path tab
5. In the Framework Linkage pop-up menu, change the link type from “Merged into code” to “Runtime shared library (RSL).”
Click OK to save the changes.
6. Build the project
7. Now check the file size of the SWF file. You will definitely be surprised!!!!
266268 bytes – BEFORE
– 125020 bytes – AFTER
141248 bytes – DIFFERENCE IN SIZE
When you choose the option to use RSLs, all of the debug information is removed.
So you can easily switch between a statically linked application and a dynamically linked application just by toggling the option in the Framework Linkage pop-up menu from “Merged into code” to “Runtime shared library (RSL).”
The framework RSL is the only RSL that is configured by default in the flex-config.xml file because every Flex application uses over 100K of framework classes. If you do add RSLs, the compiler will always load any RSLs you specify whether or not they are used by your application.
For more information on this check the following link
Posted by Almost Noted on May 7, 2008
I was reading an article from Adobe about How to increase the performance of the Flex application using the new Flash Player cache feature available in new Adobe Flash Player 9 Update 3 (9,0,115,0)
1. The Flash Player cache is a new feature available in Flash Player 9 Update 3 (9,0,115,0).
2. The cache allows files signed by Adobe to be cached by Flash Player.
3. These files end in the file extension .swz.
4. They can be reused in more than one domain, apart from the domain in which they originated
5. The SWZ file persists in the cache even after the browser is closed, provided that the end user does not change settings in
the Flash Player Settings Manager to reduce their caching ability
6. A SWZ downloaded in IE can also be used in Mozilla Firefox as it requires only one copy of the framework
7. In Flex 3 , the framework library code has been rolled into RSLs (Runtime shared library)
RSL can either be an SWZ or SWF, which can be loaded runtime instead of being statically linked into the application
Because of this, the application’s file size becomes smaller.
8. Once the Flex-signed RSLs are cached on a user’s machine from running one application, they are available for use by all other
applications, regardless of the original domain used to load the application.
Posted by Almost Noted on May 7, 2008
Four important points to take care of while building Flex Web Applications
1. Avoid use of too many containers in the flex application
Flash Player uses a hieratical display object graph. The deeper containers are nested the longer the rendering takes by hindering the performance of your application. As per Adobe it is 100 percent avoidable.
2. Avoid use of very long animations
Most animations are simply TOO LONG and they will annoy users. Developers should make sure that the animations have meaning and provide context.
3. Avoid use of complicated itemRenderers in List, Datagrid
As mentioned in the first point, ItemRenderer is one of the place where containers can get deeply nested. The number of item renderers which are rendered by the DataGrid is the number of visible rows times the number of visible columns. This slows down the applications. When complex layout logic is needed in an item renderer, it is best to use UIComponent (or other more low-level classes) and position the contents for that cell manually.
4. Make use of Runtime Shared Libraries (RSL)
Runtime Shared Libraries (RSL) is available for reducing the size of your applications.
Posted by Almost Noted on April 2, 2008
For example, applications can be developed using one or a combination of the following technologies:
* Flash / Flex / ActionScript
* PDF can be leveraged with any application
1. The new Adobe AIR runtime lets developers use Flex technology to build rich Internet applications that deploy to the desktop.
2. AIR applications run across operating systems
3. AIR applications are easily delivered using a single installer file
Creating an AIR application in Flex Builder 3
1. Install the AIR runtime (runtime for desktop)
2. Install Flex Builder 3
3. Follow the below link
The Adobe technology platform contains two primary runtimes
1. Flash Player is browser-based
2. Adobe AIR is desktop-based
AIR is built on top of Flash Player, so the Flash Player APIs are available within Adobe AIR
Consequently, Adobe AIR APIs are not available within Flash Player
The Flex framework is built on top of the Flash Player APIs, so it runs in both Flash Player and Adobe AIR. However, a number of Flex APIs take advantage of AIR APIs, and thus work only within Adobe AIR
Although the AIR security model is an evolution of the Flash Player security model, the security contract is different from the security contract applied to content in a browser. This contract offers developers a secure means of broader functionality for rich experiences with freedoms that would be inappropriate for a browser-based application.
AIR applications run with the same user privileges as native desktop applications
Adobe AIR Developer Center for Flex
Posted by Almost Noted on October 4, 2007
Shared Objects are used to store data outside of the Flash Player
There are two types of Shared Objects
1. Local shared objects – LSOs
2. Remote shared objects – RSOs
LSO is similar to browser cookies
But what are cookies..Cookies have got the ability to remember the user information so that the user doesnt have to manually login during each visit..
LSO Vs Cookies
LSOs are can store more data than cookies
LSOs never expire
LSOs arent transmitted between the client and the server
LSOs can store native ActionScript datatypes.
Uh!! Cool isnt it??
LSOs are to Flash (Call it Flash cookies)
Cookies are to web browsers
LSO files are saved to the client computer in a binary file ending with a .sol extension
Flash movies with in the same domain can read from or write to the .sol files by means of ActionScript’s flash.net.SharedObjects
The static getLocal() method is the mechanism by which LSOs are both created and opened for reading
var example : SharedObject = SharedObject.getLocal(“example”);
Remote Sharing Objects
RSOs are created using the static getRemote function. This returns a reference to an object that can be shared across multiple clients by means of a server, such as Flash Media Server. If the shared object does not already exist, this method creates one.
The following code shows how you assign the returned shared object reference to a variable:
var myRemote_so:SharedObject = SharedObject.getRemote(name, remotePath, persistence);
To create a shared object that is available only to the current client, use SharedObject.getLocal().
After calling this method, use SharedObject.connect() to connect the object to the application server, as shown in the following code:
var myNC:NetConnection = new NetConnection();
var myRemoteSO:SharedObject = SharedObject.getRemote(“mo”, myNC.uri, false);
To confirm that the local and remote copies of the shared object are synchronized, use the sync event.
All clients that want to share this object must pass the same values for the name and remotePath parameters.