One thing we have talked about from the beginning of SAIL design is
how to get multi-user learning experiences.
I'd like to keep my eye on this, as possibly one of the first non-pas
things to be developed.
Have any of you architects out there thought any deep thoughts about
this? What would be the best "first steps" to take in helping get
something up and running?
I'm thinking maybe of a local host that runs a dedicated SAIL pod
that "listens" to other client pods that may be running on laptops
that are hooked physically to a hub that connects a small group of
machines. Or maybe those users are logged in directly to the
groupware pod, and it is somehow a real time multiuser experience?
So I am wondering about solutions for these problems either in real
time (e.g., multi-user design space where 6 students watch each other
take the "pen" and draw sketches, and markup a common sketch or
concept map, etc)) or quasi real-time (ie, asynchronous, but fast, on
a local subnet - like a collaborative search tool where users do
google searches and "contribute" good resources to a common pool,
based on their individual searches.
I am trying to think through the overall space of this functionality,
to guide the design of much richer inquiry projects that start using
SAIL in more of a small group configuration. Its important to think
about these things as we move forward on the portal design, because
we need to make sure this user registration system carries the widest
possible spectrum of load (presumably by being relatively
lightweight, and thus demanding additional layers of functionality to
coordinate various kinds of research that *will be* coming...
1. For Design or group planning
A. Sketch (physical drawing)
B. Knowledge building
i. collaborative database of notes (a la "knowledge forum")
ii. concept maps
iii. wiki
2. For experimentation
A. Models and simulations
i. multiple people looking at the same running model, taking
turns controlling it, a la CoLab
ii. multiple people controlling different aspects of a
simulation or model, resulting in a common product projected on a
screen (a la "C5"/Mr. Vetro)
B. Data collection using probeware, handhelds, observations, etc.
i. create aggregated data over time, across geographical
regions
3. For peer exchange
A. Conferencing
i. presentations (e.g., powerpoint-like, or VNC?)
ii. real time video, audio, chat?
B. Student/teacher exchanges
i. Students can easily pass their work on to groups of peers
who wold evaluate, critique, etc
ii. Access by teachers to student efforts?
Obviously, just getting started with this effort. But wanted to ask
what people thought, in case it had bearing on our design of portal,
groups, multi-user pods, etc?
talk to you tomorrow online
-jim
On Jan 10, 2007, at 8:09 AM, [email protected] wrote:
>
> On Wed, 2007-01-10 at 01:00 -0500, Turadg Aleahmad wrote:
> > Incidentally, I'm pleased as a pickle to see unit testing of the
> GUI.
>
> Unfortunately this testing doesn't currently work with Maven. Maven
> uses its own classloader for the test dependencies, and this prevents
> the EasyMock lasses from being visible to the AWT. Which then
> makes the
> EasyMock crash. Laurel is looking into a work around. And then we'll
> have to try that work around on continuum.
>
> Scott
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---
