Well I am here because I still care about the issue - interactive, open source education - but I still haven't figured out how it can possibly work.
My gut instinct is that the only viable community will look a lot like the open-source java community than the desktop linux community. There is a significant profit motive in the j2ee/spring/tomcat/jboss community and frankly I think it makes them better at listening to their customers.
I think it is really key to figure out how monetize tiny games stuff, just as jboss, spring source and others did with open source java tools.
I more than ever believe that html 5 is the way to go, not native android apps.
that s my 2 cents
My initial gut feel:
* Front end == HTML5+JS. Free.
* Back end == instrumentation, analysis, persistent game session,
integration with FB, etc. Not free.
--g
I believe in HTML5. This community is primarily intended for
developing HTML5 games.
Re: separation of data and gameplay, I think some of this is possible,
and some not. I might say "instructional material highly embedded,
assessment taking the shape of games that are auto-generated by data."
I've got some prototype code for pulling questions from a question
bank using the Moodle gift format and turning it into a set of rooms
in Akihabara. I'll have to polish that up a bit and push it into
Github.
Pulling from something like Full Marks (http://www.fullmarks.org.za/)
is potentially very interesting.
--g
--g
My biggest concern with XO activities is that they are very limited in
potential reach. HTML5 will, at some point, run on everything with a
browser -- even if that's not the case right yet.
What's the browser on the latest XO? Is it HTML5/Canvas compatible?
--g
Thanks Christian.
I've got a very particular vision of a very particular kind of game.
I'm sure it's not the only vision, but it's the one vision I've got
the passion to drive.
In the very near future -- as soon as I can free myself from my
current time sucks -- I'll be articulating this vision more fully,
with show and tell, examples, tutorials, IRC meetings, and so on and
so on. (The demo that pulls automagically from Github seems to be
broken, so the first thing I want to do is fix that, hopefully tonite.
Will ping all when it works.)
More coming soon.
--g
Well I am here because I still care about the issue - interactive, open source education - but I still haven't figured out how it can possibly work.
--
Funny you should mention that. I'm not a Ruby programmer but use Ruby
tools all the time. RSpec Book was recommended over at openSUSE when
I was putting time on that OS, before I turned full focus to Fedora.
If I were a programmer, this is the way I would approach the task. I
like the keyword from the the overview: "craftsmanship". Actually,
even at the shell script level, the ideas hold. Especially for an OS
release engineer, for such a large system release with lots of
dependencies, the process the book describes holds water still...
Thanks, Ed. Great recommendation.
- CB
Here's
Here's a question for you: have you considered how these widgeds are
connected to standards? Is there a pathway linking all these widgeds
together to a set of learning objectives? Or is that not a problem
you're interested in solving yet?
I'm *extremely* interested in the specific set of "mastering a chain
of skills in a narrative framework" -- thanks to C. Scott's blog post
yesterday which helped me articulate this idea.
--g