My favorites | Sign in
Google
       
Details: Show all Hide all

Earlier this year

  • Nov 19, 2009
    issue 129 (Source error in FileMonitorEvent.as) Status changed   -   Fixed in commit 113
    Status: Fixed
    Fixed in commit 113
    Status: Fixed
  • Nov 19, 2009
    r113 (fixing issue 129, constructor argument named incorrectly) committed   -   fixing issue 129, constructor argument named incorrectly
    fixing issue 129, constructor argument named incorrectly
  • Sep 22, 2009
    issue 49 (JPGEncoder Poor Performance) changed   -  
    Status: Accepted
    Owner: thibault.imbert
    Labels: Priority-High Priority-Low
    Status: Accepted
    Owner: thibault.imbert
    Labels: Priority-High Priority-Low
  • Sep 22, 2009
    issue 18 (Need to add SHA512 Class) Status changed   -   We can leave this to as3crypto: http://code.google.com/p/as3crypto/
    Status: WontFix
    We can leave this to as3crypto: http://code.google.com/p/as3crypto/
    Status: WontFix
  • Sep 22, 2009
    issue 17 (Need SHA 384 Class) Status changed   -   We can leave this to as3crypto: http://code.google.com/p/as3crypto/
    Status: WontFix
    We can leave this to as3crypto: http://code.google.com/p/as3crypto/
    Status: WontFix
  • Sep 22, 2009
    issue 122 (Create interface for image encoding) commented on   -   Note, one thing to consider when thinking about whether we have a static encode method, or require the use the create an instance of the encoding class, is whether we plan to eventually support an asynchronous encode method / api. RIght now, I think this would be useful as encoding can be pretty CPU intensive, although some of the performance improvements we are considering might not make this as important. Anyways, we should consider this when designing the interface / api.
    Note, one thing to consider when thinking about whether we have a static encode method, or require the use the create an instance of the encoding class, is whether we plan to eventually support an asynchronous encode method / api. RIght now, I think this would be useful as encoding can be pretty CPU intensive, although some of the performance improvements we are considering might not make this as important. Anyways, we should consider this when designing the interface / api.
  • Sep 22, 2009
    issue 23 (Standardize the API for image encoders) changed   -  
    Owner: thibault.imbert
    Labels: Priority-High Priority-Medium
    Owner: thibault.imbert
    Labels: Priority-High Priority-Medium
  • Sep 22, 2009
    issue 88 (Detaied package overview) changed   -  
    Status: Accepted
    Labels: Priority-Low
    Status: Accepted
    Labels: Priority-Low
  • Sep 22, 2009
    issue 91 (DateUtil.toW3CDTF shifts milliseconds if millis<100) changed   -  
    Status: Accepted
    Owner: mikechambers
    Status: Accepted
    Owner: mikechambers
  • Sep 22, 2009
    issue 92 (Allow UTC instead of time zone offset in DateUtil.toW3CDTF) changed   -  
    Status: Accepted
    Owner: mikechambers
    Status: Accepted
    Owner: mikechambers
  • Sep 22, 2009
    issue 96 (Current download doesn't work on Windows systems) Status changed   -   What doesnt work? The zip file?
    Status: NeedMoreInfo
    What doesnt work? The zip file?
    Status: NeedMoreInfo
  • Sep 22, 2009
    issue 102 (AS3 JPGEncoder not work) Status changed   -   Can you post an example so we can reproduce the issue?
    Status: NeedMoreInfo
    Can you post an example so we can reproduce the issue?
    Status: NeedMoreInfo
  • Sep 22, 2009
    issue 122 (Create interface for image encoding) Owner changed   -  
    Owner: thibault.imbert
    Owner: thibault.imbert
  • Sep 22, 2009
    issue 112 (FileTarget class don't output logs to file formated as expec...) commented on   -   Fixed. Committed revision 112. Thanks for the report and patch.
    Fixed. Committed revision 112. Thanks for the report and patch.
  • Sep 22, 2009
    issue 112 (FileTarget class don't output logs to file formated as expec...) Status changed   -   This issue was closed by revision r112.
    Status: Fixed
    This issue was closed by revision r112.
    Status: Fixed
  • Sep 22, 2009
    r112 (Fixed issue #112.) committed   -   Fixed issue #112.
    Fixed issue #112.
  • Sep 22, 2009
    issue 113 (Code causes errors in FDT due to inappropriate use of 'final...) commented on   -   Fixed. Committed revision 111. Thanks for the report and patch.
    Fixed. Committed revision 111. Thanks for the report and patch.
  • Sep 22, 2009
    issue 113 (Code causes errors in FDT due to inappropriate use of 'final...) Status changed   -   This issue was closed by revision r111.
    Status: Fixed
    This issue was closed by revision r111.
    Status: Fixed
  • Sep 22, 2009
    r111 (Fixed issue #113.) committed   -   Fixed issue #113.
    Fixed issue #113.
  • Sep 22, 2009
    issue 115 (DateUtil.parseW3CDTF parses incorrectly when time has more t...) commented on   -   Fix. Committed revision 110. Thanks for the report and patch.
    Fix. Committed revision 110. Thanks for the report and patch.
  • Sep 22, 2009
    issue 115 (DateUtil.parseW3CDTF parses incorrectly when time has more t...) Status changed   -   This issue was closed by revision r110.
    Status: Fixed
    This issue was closed by revision r110.
    Status: Fixed
  • Sep 22, 2009
    r110 (Updated unit test to reproduce issue #115 Fixed issue #115) committed   -   Updated unit test to reproduce issue #115 Fixed issue #115
    Updated unit test to reproduce issue #115 Fixed issue #115
  • Sep 22, 2009
    issue 87 (StringUtil.replace Performance Comparison) Status changed   -   Fixed. Committed revision 109.
    Status: Fixed
    Fixed. Committed revision 109.
    Status: Fixed
  • Sep 22, 2009
    r109 (Changed replace implementation per issue #87 http://code.goo...) committed   -   Changed replace implementation per issue #87 http://code.google.com/p/as3corelib/issues/detail?id=87
    Changed replace implementation per issue #87 http://code.google.com/p/as3corelib/issues/detail?id=87
  • Sep 22, 2009
    issue 126 (Implement clone tests) Status changed   -   Fixed in revision 108.
    Status: Fixed
    Fixed in revision 108.
    Status: Fixed
  • Sep 22, 2009
    r108 (Refactored com.adobe.protocols.dict.* to use events in a way...) committed   -   Refactored com.adobe.protocols.dict.* to use events in a way more consitent with rest of library and ActionScript. Added test cases for all dict events.
    Refactored com.adobe.protocols.dict.* to use events in a way more consitent with rest of library and ActionScript. Added test cases for all dict events.
  • Sep 21, 2009
    r107 (Removed a trace call.) committed   -   Removed a trace call.
    Removed a trace call.
  • Sep 21, 2009
    r106 (Implemented clone method, and unit test for it.) committed   -   Implemented clone method, and unit test for it.
    Implemented clone method, and unit test for it.
  • Sep 21, 2009
    r105 (removed trace accidentally left in.) committed   -   removed trace accidentally left in.
    removed trace accidentally left in.
  • Sep 21, 2009
    r104 (Changed script reference to CoreLibTestRunnerClass.as) committed   -   Changed script reference to CoreLibTestRunnerClass.as
    Changed script reference to CoreLibTestRunnerClass.as
  • Sep 21, 2009
    r103 (renaming CoreLibTestRunner_script to CoreLibTestRunnerClass....) committed   -   renaming CoreLibTestRunner_script to CoreLibTestRunnerClass. Removing duplicate copy of CoreLibTestRunner
    renaming CoreLibTestRunner_script to CoreLibTestRunnerClass. Removing duplicate copy of CoreLibTestRunner
  • Sep 21, 2009
    r102 (Added a couple of additional property checks in the clone te...) committed   -   Added a couple of additional property checks in the clone test.
    Added a couple of additional property checks in the clone test.
  • Sep 21, 2009
    r101 (Added an additional check to make sure cloned instance is no...) committed   -   Added an additional check to make sure cloned instance is not same instance as original.
    Added an additional check to make sure cloned instance is not same instance as original.
  • Sep 21, 2009
    r100 (Implemented clone method, and unit test.) committed   -   Implemented clone method, and unit test.
    Implemented clone method, and unit test.
  • Sep 21, 2009
    issue 126 (Implement clone tests) reported   -   Right now, the unit tests fail because a bunch of clone tests for events have not been implemented. We need to implement these tests.
    Right now, the unit tests fail because a bunch of clone tests for events have not been implemented. We need to implement these tests.
  • Sep 21, 2009
    issue 120 (Drop support for Flash Player 9) commented on   -   One thing to keep in mind, is that whatever we do, it has to be easy to maintain (as we have few people working on the project). So, I dont want to maintain two branches / versions and releases.
    One thing to keep in mind, is that whatever we do, it has to be easy to maintain (as we have few people working on the project). So, I dont want to maintain two branches / versions and releases.
  • Sep 20, 2009
    issue 115 (DateUtil.parseW3CDTF parses incorrectly when time has more t...) changed   -  
    Status: Accepted
    Owner: christian.cantrell
    Status: Accepted
    Owner: christian.cantrell
  • Sep 20, 2009
    issue 125 (Create performance test suite (similar to unit tests)) reported   -   Could consider using the work grant skinner has done: http://www.gskinner.com/blog/archives/2009/04/as3_performance.html This would: 1. help make sure performance doesnt get worse 2. help us measure performance improvements progress
    Could consider using the work grant skinner has done: http://www.gskinner.com/blog/archives/2009/04/as3_performance.html This would: 1. help make sure performance doesnt get worse 2. help us measure performance improvements progress
  • Sep 20, 2009
    issue 124 (Look into deprecating or removing some utils APIs) reported   -   Need to do a pass on all of the utils apis, and look at deprecating or removing some. For example, do we really need a copyArray APIs in ArrayUtils? public static function copyArray(arr:Array):Array { return arr.slice(); } We should log bugs / issues for proposed changes to each utils class.
    Need to do a pass on all of the utils apis, and look at deprecating or removing some. For example, do we really need a copyArray APIs in ArrayUtils? public static function copyArray(arr:Array):Array { return arr.slice(); } We should log bugs / issues for proposed changes to each utils class.
  • Sep 20, 2009
    issue 123 (crypto performance improvements) reported   -   Look at performance optimizations for crypto apis.
    Look at performance optimizations for crypto apis.
  • Sep 20, 2009
    issue 122 (Create interface for image encoding) reported   -   Right now, JPGEncoder and PNGEncoder do essentially the same thing, but provide different API naming schemes to do it. For example, JPGEncoder uses a instance encode API, where as PNGEncoder, uses a static encode APIs. We should standardize the APIs, perhaps creating a formal interface for them. Might be worth looking at the Flex based encoding classes to figure out the interface that should be used (although these classes should not require Flex).
    Right now, JPGEncoder and PNGEncoder do essentially the same thing, but provide different API naming schemes to do it. For example, JPGEncoder uses a instance encode API, where as PNGEncoder, uses a static encode APIs. We should standardize the APIs, perhaps creating a formal interface for them. Might be worth looking at the Flex based encoding classes to figure out the interface that should be used (although these classes should not require Flex).
  • Sep 20, 2009
    issue 121 (Refactor Utils) reported   -   Consider refactoring utils.* classes to use static package methods. This would allow only the APIs needed to be compiled into a SWF. To maintain backward capatibility, we could keep the existing classes, and the apis could map to the static APIs. Need to determine what package structure would be.
    Consider refactoring utils.* classes to use static package methods. This would allow only the APIs needed to be compiled into a SWF. To maintain backward capatibility, we could keep the existing classes, and the apis could map to the static APIs. Need to determine what package structure would be.
  • Sep 20, 2009
    issue 112 (FileTarget class don't output logs to file formated as expec...) changed   -  
    Status: Accepted
    Owner: mikechambers
    Status: Accepted
    Owner: mikechambers
  • Sep 20, 2009
    issue 56 (Remove reference / reliance on Flex classes) commented on   -   We either need to remove the reliance on the flex classes, or move them into their own package so it is clear they rely on Flex (similar to what we do with the AIR classes).
    We either need to remove the reliance on the flex classes, or move them into their own package so it is clear they rely on Flex (similar to what we do with the AIR classes).
  • Sep 20, 2009
    issue 87 (StringUtil.replace Performance Comparison) changed   -   Note : need to make sure this doesnt break the unit tests.
    Status: Accepted
    Owner: mikechambers
    Note : need to make sure this doesnt break the unit tests.
    Status: Accepted
    Owner: mikechambers
  • Sep 20, 2009
    issue 120 (Drop support for Flash Player 9) reported   -   One thing we could consider doing is dropping support for Flash Player 9. This would allows us to take advantage of Vectors within some of the libraries, which could give some performance improvements. Before deciding to do this, we should do a pass through the code, and see if we would get any major improvements. Thoughts?
    One thing we could consider doing is dropping support for Flash Player 9. This would allows us to take advantage of Vectors within some of the libraries, which could give some performance improvements. Before deciding to do this, we should do a pass through the code, and see if we would get any major improvements. Thoughts?
  • Sep 20, 2009
    issue 108 (After unwatch a file in the FileMonitor the watch doesn't wo...) Owner changed   -  
    Owner: mikechambers
    Owner: mikechambers
  • Sep 20, 2009
    issue 113 (Code causes errors in FDT due to inappropriate use of 'final...) changed   -  
    Status: Accepted
    Owner: mikechambers
    Status: Accepted
    Owner: mikechambers
  • issue 11 (Call dispose() on BitmapData objects when done) reported   -   Its probably a good idea to call BitmapData.dispose() on BitmapData instances we the code is done with them, to ensure that the memory for them is reclaimed.
    Its probably a good idea to call BitmapData.dispose() on BitmapData instances we the code is done with them, to ensure that the memory for them is reclaimed.
  • issue 10 (Need way to specify whether to include overlapping array) commented on   -   This title is wrong. It should be: Need way to specify whether to include Angle data
    This title is wrong. It should be: Need way to specify whether to include Angle data