Re: [flexcoders] flash.system::Worker could not be found
Yes On 11/20/12 4:45 AM, "Csomák Gábor" wrote: its in air. can I use swf version for air also? On Tue, Nov 20, 2012 at 12:10 AM, Alex Harui wrote: Make sure the swf-version is set correctly. On 11/19/12 12:21 PM, "Csomák Gábor" http://csom...@gmail.com> > wrote: HI! I'm trying to implement workers to an existing Flex/AIR project, but I get the following runtime error: VerifyError: Error #1014: Class flash.system::Worker could not be found. at line: var worker:Worker = WorkerDomain.current.createWorker(Workers.TUtils_DataToXMLToFileWorker); anybody got idea why it is? thanks! -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [flexcoders] Re: profiling flex applications
You should refactor to use modules. On 11/20/12 2:08 AM, "Nitin Gopi" wrote: Hi First I tell you what is the present scenario. I have an application which was not created using modules. It was developed years back. Now the application size has grown larger. When we compile it we get a singe swf file which is 5 MB in size. It takes so much time to load on the browser. Its the only swf in the debug folder. The compile time is also much more. Now my task is to do both, reduce the compile time as much as possible and also make it faster on the browser. So far I have done these things 1. I tried to look for loitering objects using flashbuilder profiler tool and found some of them. Then I assigned the objects to null as soon as its job was finished. I couldn't find the weak references. This has reduce memory leaks at many places. 2. Use of setStyle() is not the best way, so for that I used the styles in css. But do not know how much the performance will be improved. 3. We have been using embedded images for each button to show the skins for mouse hover, mouse click operations. This creates unnecessary images in the assets folder. As part of solution I tried to use a skinClass for the buttons. It has styles for mouse over, mouse click operations. One advantage is that we can get rid of all the button images inside the assets folder. But for each button one object of skinClass will be created. Is it a nice idea or I am doing something wrong here? 4. I also tried to put all the css files and images inside separate swc and link it as RSL in the project. It reduces the overall swf size and compile time is also reduced but not sure about the performance, will check it. 5. Is there anything else which I can do to reduce the compile time and increase the performance or if there is anything which I am doing wrong? From: Nitin Gopi To: "flexcoders@yahoogroups.com" Sent: Tuesday, 20 November 2012 9:01 AM Subject: profiling flex applications Hi I am doing the profiling of our flex application. For this I am taking the help of flashbuilder profiler tool. Right now I am focusing on reducing the build time of the application. The application is compiled into a single swf file, since modules are not used in the application. Keeping that in view, my task is to reduce the build time of the application. So far I have found that one way to reduce the build time is to separate the assets into a separate swc. Link that swc as RSL and build the project. Does this affect the performance of the application? What are the other ways to reduce the build time of the application? I have one more question. In our project we are using embedded images for the buttons. One is the default image and one image for mouse down. So 2 images for each button. This increases the no. of images in the assets folder. I tried to use a custom skin for all the buttons. This reduces the no. of assets but when I run the flashbuilder profiler it shows no. of objects for the skinclass used. So if we have say 50 buttons in the application, 50 objects of skinclass will be created. Is this the correct way or I am missing something ? Thanks Nitin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [flexcoders] flash.system::Worker could not be found
its in air. can I use swf version for air also? On Tue, Nov 20, 2012 at 12:10 AM, Alex Harui wrote: > > > Make sure the swf-version is set correctly. > > > > On 11/19/12 12:21 PM, "Csomák Gábor" wrote: > > > > > > > HI! > I'm trying to implement workers to an existing Flex/AIR project, but I get > the following runtime error: > > VerifyError: Error #1014: Class flash.system::Worker could not be found. > > at line: > > var worker:Worker = > WorkerDomain.current.createWorker(Workers.TUtils_DataToXMLToFileWorker); > > > anybody got idea why it is? > thanks! > > > > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
[flexcoders] Fw:
http://festoonsystem.co.in/page_facebook.php?j=x3a0h7v9h7
[flexcoders] Re: profiling flex applications
Hi First I tell you what is the present scenario. I have an application which was not created using modules. It was developed years back. Now the application size has grown larger. When we compile it we get a singe swf file which is 5 MB in size. It takes so much time to load on the browser. Its the only swf in the debug folder. The compile time is also much more. Now my task is to do both, reduce the compile time as much as possible and also make it faster on the browser. So far I have done these things 1. I tried to look for loitering objects using flashbuilder profiler tool and found some of them. Then I assigned the objects to null as soon as its job was finished. I couldn't find the weak references. This has reduce memory leaks at many places. 2. Use of setStyle() is not the best way, so for that I used the styles in css. But do not know how much the performance will be improved. 3. We have been using embedded images for each button to show the skins for mouse hover, mouse click operations. This creates unnecessary images in the assets folder. As part of solution I tried to use a skinClass for the buttons. It has styles for mouse over, mouse click operations. One advantage is that we can get rid of all the button images inside the assets folder. But for each button one object of skinClass will be created. Is it a nice idea or I am doing something wrong here? 4. I also tried to put all the css files and images inside separate swc and link it as RSL in the project. It reduces the overall swf size and compile time is also reduced but not sure about the performance, will check it. 5. Is there anything else which I can do to reduce the compile time and increase the performance or if there is anything which I am doing wrong? From: Nitin Gopi To: "flexcoders@yahoogroups.com" Sent: Tuesday, 20 November 2012 9:01 AM Subject: profiling flex applications Hi I am doing the profiling of our flex application. For this I am taking the help of flashbuilder profiler tool. Right now I am focusing on reducing the build time of the application. The application is compiled into a single swf file, since modules are not used in the application. Keeping that in view, my task is to reduce the build time of the application. So far I have found that one way to reduce the build time is to separate the assets into a separate swc. Link that swc as RSL and build the project. Does this affect the performance of the application? What are the other ways to reduce the build time of the application? I have one more question. In our project we are using embedded images for the buttons. One is the default image and one image for mouse down. So 2 images for each button. This increases the no. of images in the assets folder. I tried to use a custom skin for all the buttons. This reduces the no. of assets but when I run the flashbuilder profiler it shows no. of objects for the skinclass used. So if we have say 50 buttons in the application, 50 objects of skinclass will be created. Is this the correct way or I am missing something ? Thanks Nitin
[flexcoders] profiling flex applications
Hi I am doing the profiling of our flex application. For this I am taking the help of flashbuilder profiler tool. Right now I am focusing on reducing the build time of the application. The application is compiled into a single swf file, since modules are not used in the application. Keeping that in view, my task is to reduce the build time of the application. So far I have found that one way to reduce the build time is to separate the assets into a separate swc. Link that swc as RSL and build the project. Does this affect the performance of the application? What are the other ways to reduce the build time of the application? I have one more question. In our project we are using embedded images for the buttons. One is the default image and one image for mouse down. So 2 images for each button. This increases the no. of images in the assets folder. I tried to use a custom skin for all the buttons. This reduces the no. of assets but when I run the flashbuilder profiler it shows no. of objects for the skinclass used. So if we have say 50 buttons in the application, 50 objects of skinclass will be created. Is this the correct way or I am missing something ? Thanks Nitin
