One of the stances I take towards PLEs is (not surprisingly) that they are in some sense amenable to personalisation. Tinkering with my VLE Library demo 'course' just now (if you aren't of the OU and you want a guest ticket, mail me, and I'll see what I can do) I started wondering about the extent to which instructors are allowed to add widgets of their own choosing to the VLEs in their own institutions, or whether they can only incorporate modules from an 'approved list'; or maybe whether they have to go to someone in their academic computing service who looks after the VLE, and asks them to configure a course with the various optional functional modules that are supported.
What prompted this thought was this agenda item for the forthcoming Moodle Moot hackfest
Page-Based Chat Roster and WhiteboardThe COVCELL project is developing a chat module (based on jabber) for Moodle. Chat rosters are to be generated on a per-page basis, so that anyone who is logged in and is viewing a particular page will be able to see who else is viewing that page and start a chat session with them. Group chat will be supported and it will be possible to use a whiteboard (based on Coccinella) in the chat.
More information can be found at:
* http://covcell.cms.hu-berlin.de/tracov/wiki/Phase_I
* http://covcell.org/
Err - 2 minutes later - like this embedded Gabbly chat box, perhaps?
(Hmm - that Gabbly feed from Library VLE Demo page suggests a security issue to me... the page requires authentication to get in, but the feed is public. Also, the address of the feed appears to be http://feed.gabbly.com/vledemo.open.ac.uk/course/view.php?id, and the same adress is given for the actual chat box. Now my course is actually id=69...so I wonder - if someone on another course had a Gabbly chat box, would we share the same discussion? i.e. will Gabbly only act Moodle installation wide, and not within particular pages?
Okay - so maybe Gabbly chat can't be used out of the can as a page based chat roster (or maybe it could if there was a sensible and informative URL/addressing structure in Moodle?) For the sake of 35 mins installation, and 20 mins blog posting (!), I think it was worth it though...
Anyway - what this suggests to me is that maybe there is another dimension to the *LEs? That is, environments that support the inclusion of arbitrary HTML/js widgets that are not neceassrily part of the VLE configuration?
To my mind, these look set to take off this year, e.g. with the impending widgetbox widget exchange (I love a phrase in their elevator pitch - syndicating functionality) or Snipperoo universal widget (see also the ZDNet post).
So how about thinking about PLEs in this way - as envirnments in whcih a) instructors and/or b) students are allowed to include gadgets/widgets in the environment if they so wish?
For example, at the moment I'm adding all sorts of gadgets to my Moodle account - and I hope the demo VLE continues to allow me that freedom.
But several questions arise:
1) in the production environment, will course team members be allowed to add artbitrary HTML content to their Moodle course directly?
2) will CT members be allowed to add Javascript enriched pages to their course?
3) will CT members be allowed to embed 3rd party HTML/js widgets to their course?
PS Hmmm - maybe they'll follow the MySpace approach...:
MySpace has taken a step to increase security that disables a key method for third party vendors to spread their services inside the online social network. The company is using new code in a new version of flash that disables outgoing links from flash widgets and it is pushing users to install the blockable version of flash by requiring that they do so in order to view MySpace hosted video. ... Just as javascript has been unusable in MySpace, most flash objects are also now unable to link out to third party sites when viewed with Flash player 9. ... This means that the “get this widget” function so key to the viral spread of a growing industry of MySpace widgets will soon be unavailable.Reported on Techcrunch Posted by ajh59 at July 22, 2006 02:58 PM