Subscribe by Email

Your email:

More from Allen Interactions:

e-Learning Leadership Blog 

e-Learning Case Studies and Demos

Connect with us!

Allen Interactions Facebook Page

 

e-Learning Authoring Research Blog

Current Articles | RSS Feed RSS Feed

Creating a Playful Environment for e-Learning

Share on Twitter Twitter | Share on Facebook Facebook | Submit to Digg digg it |  Add to delicious  delicious |  Submit to StumbleUpon StumbleUpon |  Share on LinkedIn LinkedIn | Submit to Reddit reddit 
Dr. Michael Allen, CEO, allen interactions

Dr. Michael Allen speaks about the future of Zebra and the future of authoring tools.

From http://www.brandon-hall.com/workplacelearningtoday/?p=8820

DevLearn 2009 

From Jay Cross 

Comments

The point that you made about the creation experience being fun because what we are creating should be engaging and fun is a great one. I wonder, what can be done to inject fun into the creation experience? 
 
Lately I've been spending quite a lot of time with a game creation tool called GameSalad <a>http://www.gamesalad.com (its Mac only and free if you don't care to publish to iPhone). I've found the creation experience to be quite fun and rewarding in GameSalad. As I step back and ask myself, why is this fun? I think one of the big factors is context.  
 
In GameSalad, whenever you're creating logic, it is always abundantly clear which object(s) that logic will impact. The result of the logic is also very easily viewable. All you have to do is click a little play button. There's no compile time--the object just appears on the screen with your logic/controls applied to it. That’s very cool. 
 
The other aspect that’s fun is dragging and dropping controls and logic, grouping things together and coming up with conditionals all WITHOUT having to write any code. 
 
The opposite of fun would have to be writing code which means having to learn a syntactical language - -blech...totally unfun.
Posted @ Thursday, February 04, 2010 11:05 AM by Dan Thatcher
Post Comment
Name
 *
Email
 *
Website (optional)
Comment
 *

Allowed tags: <a> link, <b> bold, <i> italics