Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rmhall/runway
Runway is a set of ActionScript and JavaScript libraries for leveraging the LeapMotion input device
https://github.com/rmhall/runway
Last synced: 3 months ago
JSON representation
Runway is a set of ActionScript and JavaScript libraries for leveraging the LeapMotion input device
- Host: GitHub
- URL: https://github.com/rmhall/runway
- Owner: rmhall
- Created: 2012-11-28T02:36:14.000Z (almost 12 years ago)
- Default Branch: master
- Last Pushed: 2013-01-30T03:30:54.000Z (almost 12 years ago)
- Last Synced: 2024-06-23T19:35:28.950Z (5 months ago)
- Language: ActionScript
- Homepage:
- Size: 2.63 MB
- Stars: 50
- Watchers: 17
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-actionscript-sorted - runway - Runway is a set of ActionScript and JavaScript libraries for leveraging the LeapMotion input device (File Formats / JavaScript)
README
Runway 0.1a for Leap Motion
===========================
Robert M. Hall, II - http://www.impossibilities.com/
----------------------------------------------------Runway is a set of Flash/ActionScript 3 and JavaScript apps/example code for leveraging data from the Leap Motion input device: http://leapmotion.com/
Runway also includes a Flash based polyfill for older browsers that lack native WebSockets support, so that JavasScript applications can also use the data from a Leap device.
See a short video of Runway in action here:
http://rhall.s3.amazonaws.com/runway_leapmotion_demo/runway_bridge_demo.mp4Revision History:
01/29/2013:
Humbled by Victor Norgren's (@logotype) LeapMotion AS3 lib here:
https://github.com/logotype/LeapMotionAS3
I officially concede to the maxim that there is always someone out there smarter, faster and more motivated than yourself. For the record, Victor even dropped me an email offering to collaborate on making something really special together, so he is also a gentleman. My hat is off to you kind sir. So, forthwith, I humbly suggest any and all interested parties, please peruse his library as a superior implementation. I plan on forking it for my own use and with that burden lifted, refocus my efforts on actual applications and demonstrations on how the Leap Motion device can be used with Flash. This repository will remain for further examples applications, historical purposes an to serve as a constant reminder to always do good and acknowledge that the best way to learn is from others smarter than yourself. :)
01/25/2013:
1. Removed dependency on Flex SDK, instead now includes mx.utils.Base64Encoder.as, also included source for the as3corlib in addition to binary .swc for anyone having problems compiling. (Thanks to Todd Greco @mrballistic for the improvement!)
01/13/2013:
1. Refactored to proper package class structure for ease of use, and diff/change tracking in github
2. Prepped to decouple Leap to AS3 websocket communications completely from demonstration code portion showing finger/pointable position - for ease of use - End goal is a simple exposure of the Leap frame data via an event or callback - then developer can act on however they see fit - coming in next commit probably
3. Change approach to removing pointables from stage in demo (to refine further later) - prepped to decouple demonstration usage from core communications for ease of use - see #2 above - coming in next commit probably01/11/2013:
1. Made some quick revisions to support the new json structure introduced with Leap Motion SDK 0.7.1
2. (Not included but coming soon - breaking apart .fla's to proper document class structure for better tracking of revisions on github, and compilation via mxmlc so no Flash IDE is required to compile)
12/11/2012:1. Added new polyfill shim .SWF and example in the JS folder. Allows Flash to act as a WebSocket polyfill for browsers that don't natively support Web Sockets
12/11/2012:
1. Changed the fingertip rendering to be driven by enter_frame instead of the ondata websocket event, to avoid unneccessary drawing/code execution
2. Removed setting visibility, and moved to add or remove child model - need to fine tune this
3. Prepped for making a standalone SWF to act as polyfill for browsers that lack support for WebSockets to allow JS access to Leap data12/01/2012:
1. Leap SDK 0.6.6 now includes its own WebSocket server on 6437, serving JSON based info on the data captured by the device - fantastic!
2. Removed old Python socketserver that was not a full WebSocket server implementation - it is now in the deprecated folder for reference/archival purposes
3. Include as3corelib and Worlize WebSocket implementation class dependencies see: AS3_REQUIREMENTS_README.txt document in AS3 folder.
4. Also requires free Flex 4.6.0 SDK libs - not included here due to size - AS3_REQUIREMENTS_README.txt has download links for all libs.
5. Completed support for two hands and all finger tip data
6. Now has a nice connect/disconnect button since the WebSocket server is more robust
7. Linked activate/deactivate handlers to connecting/disconnecting from socket server to avoid garbage, etc. when Flash throttles down when focus is lost to avoid issues with sockets
8. Core communications is now complete - can focus on leveraging data for various uses11/29/2012 (Initial public release against Leap SDK 0.6.5):
1. Functioning Python Socket server "Runway" to collect data from LeapMotion device, format into JSON and push out over a local socket port 8888.
2. Functioning Flash library to connect via sockets to Runway Socket Server and collect/push JSON data for use in ActionScript 3
3. Demo Flash file showing interaction, finger tip data renderingUSAGE:
1. Make sure Leap application is open and Leap device is plugged in, and ready
2. Open the runway_demo.fla in Flash CS6 and Publish Preview
3. Hit Connect button
4. Use the Leap with your hands - watch your finger tip points get rendered in real time :)
5. Extend, modify, improve and enjoy!
NOTE: The Leap SDK does not currently (as of SDK 0.7.1) come with a proper socket policy file server.
You will need to either set the proper permissions on your SWF locally, or run a socket policy file server.
A simple perl based solution is available here: http://www.lightsphere.com/dev/articles/flash_socket_policy.html
By default it is set to * for all sockets and * for all domains you can (should) adjust it from * to just port 6437
and any domains settings you might want to reflect. The Leap Motion SDK should come with a socket policy file server soon.1. For leveraing the polyfill Flash based shim for JavaScript communications in older browsers, see the JS folder and the example html file source.
Pre 0.6.6 SDK (Deprecated Version) USAGE:1. Drop the python/Runway.py python script in with your Leap libs in the Leap SDK folder
2. Launch it with: python Runway.py - App will start accepting connections
3. Publish the leap_test1.fla or open the leap_test1.swf - wiggle your fingers over your Leap and watch the fun
4. Observe output from terminal Runway.py app and Flash trace statements
5. Extend, modify, improve and enjoy!
TODO:1. DONE: Add support for additional "hands" or "tools" in Runway - currently only supports first hand present
2. DONE (No longer needed): Additional refinements and data points in Runway Python socket server, and AS3 bridge classes (Learn more Python!)
3. TODO: More actual demos of usage of the data for control/input, etc - getting the communication down first!
4. DONE: Add externalInterface methods to allow SWF to run faceless and act as a bridge to JavaScript - great for supporting older browsers with no websockets, or native plugins for LeapMotion
5. DONE: Now included as part of Leap SDK 0.6.6 built in Websocket server can be leveraged in JavaScript directly - see JS folder for example HTML/JS
6. MAYBE: (Now with built in WebSocket server in Leap this might not really be neccessary) Native Extension for Adobe AIR for Mac/PC to use native LeapMotion SDK to poll/collect data from LeapMotion for use in AS3/AIR apps.
NOTES:1. The Leap Motion SDK is in a state of flux as they refine things, expect changes an improvements there as they release updates.
So there you have it - all comments, criticisms welcome! Please log issues, pull requests, etc. Enjoy!