https://github.com/johnlindquist/top-level-tools

top-level tools for ActionScript 3
https://github.com/johnlindquist/top-level-tools

Last synced: 4 days ago
JSON representation

top-level tools for ActionScript 3

• Host: GitHub
• URL: https://github.com/johnlindquist/top-level-tools
• Owner: johnlindquist
• Created: 2010-03-27T01:00:01.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2010-04-06T21:15:14.000Z (over 14 years ago)
• Last Synced: 2024-10-11T15:46:19.066Z (28 days ago)
• Language: ActionScript
• Homepage: http://pv3d.org
• Size: 425 KB
• Stars: 13
• Watchers: 3
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

• awesome-actionscript-sorted - top-level-tools - top-level tools for ActionScript 3 (Unsorted / Other API)

README

        
Top-Level Tools is a collection of package-level functions to make your ActionScript 3 life easier.

Package-level functions are slightly faster than static function calls and more convenient from your IDE as they're available anywhere with auto-complete. I initially considered building runnable classes with interfaces for each of these functions for best "out-of-the-box" performance, but decided it's just best for you to copy/paste these functions inline if you're seeking the best possible performance from these. (Considering starting an MXMLC ticket for supporting inlining to solve this problem completely)

A large part of the project is focusing on gathering utils from other open-source projects around the web. The list below deserves the proper credit for writing these great utils:

http://casalib.org/

http://code.google.com/p/sekati/

http://code.google.com/p/as3-commons/

http://jacksondunstan.com/

http://blog.soulwire.co.uk/

http://www.flightxd.com/flightframework/

http://destroytoday.com

http://code.google.com/p/as3corelib/

http://code.google.com/p/copyengine/

http://www.senocular.com/flash/actionscript/?file=ActionScript_3.0/

more to come...

TODO: 

1. Get community support

2. Gather util functions from around the web (always giving credit!)

3. Fully unit test each tool

4. Move tools that require behind-the-scenes mapping into a separate, more meaningful package. "maps?"

5. Optimize! Optimize! Optimize! Optimize! Optimize!