So as it happens, after most client meeting (client used very very loosely). It turns out the first way I was thinking about how to build this app wasn't exactly how it was originally vision. Honestly I was a little relieved, because what the new idea is made more sense to create. The only problem, how to pull it off? Read the rest of this entry »
For this one, you are going to need Flash CS3 or CS4 as far as I know. I don't know how FlashDevelop or Flex will translate. We will be using assets from the Library which are linked to AS files. I'm thinking it'd be best to go through the files. Read the rest of this entry »
I've been noticing on the NUIGroup forum there have been some kind words about what I've been doing on my site. I really do appreciate it, and feel kind of bad that I haven't kept up as much as I have when I started. Here's an idea of what I plan on experimenting on next. Incorporating RotatableScalable into apps and adding limits to the scaling and dragging. Getting a better understanding of exactly how RotatableScalable was created and functions. How about a multi-touch image magnifying glass? I've been currently working on how to get that up and running and I'm about 50% done, best guess of course. Moving along with more Google Map integration, searching and directions would be quite useful.
I've been working with the Touchlib library of multi-touch apps using Actionscript 3.0 to develop some of my own apps. This driving force behind what I've been doing is to get a general idea of how to start thinking about the code, and try to discern what works well and what does not. I began with making a simple interface to select an app to be dynamically loaded into the main flash movie. The buttons and information is built dynamically and after an app is selected a trigger is placed in the bottom right corner the user will need to hold down to being back the menu. I've used that menu to build a small collections of apps i have been experimenting with:
Rings, which works by extending RotatableScalable
Grey Lines, which uses TouchEvent.MOUSE_DOWN and TouchEvent.MOUSE_UP to read any blobs which appear on the stage
Squeegee, build an array of circles, then uses any blob information to rescale those circles based on their proximity to the blob, then uses the circles to mask an image which is revealed after you begin touching the screen
Cats Cradle, loops through all the blobs on the screen and draws a line in order of how the array of blobs is constructed. Good for studying how blobs are added an removed from the array
Physics, Flash Physics + Multi-touch -- a continued from the previous post
At the end of the video, I just wanted to give my thanks to NUIGroup, everyone there help me tremendously with getting my multi-touch hardware up and running. I hope to offer value by doing these experiments and letting the community use them as needed.
Here are some thoughts I normally have when coming up with experiments like this. How can this be different than just something you can do with just a mouse? It's one thing to get one touch point working and build an application around that. But how does it change when you can pretend there are 2 mouse cursors you can work with? Then 3? Then 4? What is the best way to optimize the code for these applications? How can I take this and build something useful for a business? Is a gaming environment the best option for thinking of commercialization opportunities?
I feel this technology has opened some interesting windows of opportunity.
And once again, I'd like to offer all my source code for the video above to anyone who'd like to dissect it.
Recent Comments