- 84 entries Alagad
- 12 entries Ant
- 167 entries ColdFusion
- 10 entries ColdSpring
- 20 entries Conferences and Events
- 1 entries Development Tools
- 5 entries Dynamic Programming
- 1 entries Flexmaniacs
- 52 entries General
- 4 entries Groovy
- 5 entries JRun
- 17 entries Jobs
- 17 entries Model-Glue
- 27 entries OO Development
- 52 entries Programming
- 31 entries Reactor For ColdFusion
- 13 entries SQL
- 14 entries The Server Side
- 7 entries Validat
- 8 entries Farcry CMS
- 32 entries Flex
- 10 entries Flex
- 3 entries Hibernate
- 3 entries jQuery
- 1 entries Presentations
- 1 entries Press
Subscribe to our The Alagad Technical Team Blog
About Matt LeGrand
Matt LeGrand is an accomplished user experience specialist with a primary focus on Adobe Flex and Air application development. Matt has been working with Flex since 2005 and Adobe Flash since 1999. His interest are in human computer interaction and interactive media research.
Author's Articles
Need a Gig? Alagad Needs a ColdFusion Contractor (like Today!)
If you’re a talented and motivated ColdFusion developer who has good Model-Glue experience and understand ColdSpring, I’ve got a job for you! We need someone who can immediately hop into the fray in an existing project, take their assignments and get coding.
The project is a large, enterprise application for a major, recognizable, company. We need someone who can dedicate at least 40 hours a week and can work during typical business hours.
This project is slated to last until March 31st. While it’s not terribly long, there is a chance the project could be extended or that additional projects may follow.
If you’re interested please send an email to me at dhughes@alagad.com.
Alagad is Hiring a User Interface Designer
The User Interface Designer is responsible for designing and producing professional software interfaces and website designs. This person will participate in the entire design process from start to finish, beginning with learning client requirements, establishing design direction, identifying and solving design challenges, creating modern and innovative interfaces, producing all required assets, and implementing designs with front-end code. In addition, the designer should have the ability to ensure acceptance of the design by the client and end user, making design modifications as necessary to accomplish this goal. The designer should possess excellent written and verbal communication skills, and the ability to maintain professional working relationships with clients, stakeholders and users.
Checking the Users Multi-Touch Capabilities
Adobe just released the beta version of Flash Player 10.1 on their 'labs' site. Previously I've written about the new multi-touch events and written a quick how to on displaying multi-touch events with the new Air 2 SDK and now I'm going to talk quickly about checking a users multi-touch capabilities.
Checking the users multi-touch capabilities is especially important because users hardware and multi-touch capabilities is going to vary widely as new monitors, mice and input devices trickle into the market place. As such, we'll need to adjust our application to take advantage of different 'MultiTouchInputModes'.
Here's the code I'm suggesting:
{
setTouchScreenType();
}
protected function addTransformListeners():void
{
this.addEventListener(TransformGestureEvent.GESTURE_PAN,
transformEventHandler, false, 0, true);
this.addEventListener(TransformGestureEvent.GESTURE_ROTATE,
transformEventHandler, false, 0, true);
this.addEventListener(TransformGestureEvent.GESTURE_SWIPE,
transformEventHandler, false, 0, true);
this.addEventListener(TransformGestureEvent.GESTURE_ZOOM,
transformEventHandler, false, 0, true);
}
protected function addTouchListeners():void
{
this.addEventListener(TouchEvent.TOUCH_BEGIN, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_END, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_MOVE, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_OUT, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_OVER, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_ROLL_OUT, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_ROLL_OVER, touchEventHandler, false, 0, true);
this.addEventListener(TouchEvent.TOUCH_TAP, touchEventHandler, false, 0, true);
}
protected function touchEventHandler(event:TouchEvent) : void
{
trace( event.toString() );
}
protected function transformEventHandler ( event :
TransformGestureEvent ) :void
{
trace( event.toString() );
}
protected function setTouchScreenType():void
{
if(Capabilities.touchscreenType == TouchscreenType.FINGER)
{
addTouchListeners();
Multitouch.inputMode = MultitouchInputMode.TOUCH_POINT;
}
else
{
addTransformListeners();
Multitouch.inputMode = MultitouchInputMode.GESTURE;
}
}
Before assuming that they have gesture capabilities we could also check if they are on Snow Leopard:
if(Capabilities.os.indexOf('Mac OS 10.6') !=-1 )
{
trace('Your kicking it with Snow Leopard');
}
I'm not sure how to check if they are on a laptop with a trackpad. Any ideas?
Any danger in just listening for all of these events? Well nothing life threatening. If the hardware isn't capable, the events simply don't fire. It's always a good idea to use weak references when listening for events and/or remove event listeners so that we're not inadvertently using up unneeded memory allocations.
So with this information we can somewhat accurately customize our application to take advantage of what type of hardware our users might be sitting behind. We might have a picture collage that reacts differently to the different type of hardware that it's viewed on for example.
If your company is interested in multi-touch or just want to talk. Drop us a note on our contact page.
