Speaking of Murugan, he has a great post up about making wikis work offline and points to the nice Wiki2Go tool. At SLN, we think having offline capabilities are valuable for faculty (and, personally, I think they are at least as valuable for students as well). As Murugan points out, there is some common ground with the road warrior. I think we have to assume that higher ed learners are road warriors, in a way. Maybe that road is between work and home, but the point is that they are learning online because they are on the move and need to take their courses with them.
Tag: working-offline
-
More Offline Toys
Today I’m trying out Blogjet. In contrast to ecto, it has a somewhat simpler interface more reminiscent of a browser than an email client. Like ecto, it offers WYSIWYG:
Both seem like they would work fine for faculty.
-
Working Offline with ecto
-
Web 2.0 for Tracking Web 2.0
Before I start on this post, I want to note that I am writing it in the Bleezer offline blogging client found via D’Arcy. This little freeware application is just a couple of months old and it already rivals much older for-pay blogging clients.
Anyway, Alan Levine is asking for a Web 2.0 tools list that is managed using a Web 2.0 tool.
His wish is my command (created using Lazybase):
-
Progress Toward an Offline e-Learning Client?
One of the most beloved aspects of the SUNY Learning Network’s current Lotus Notes-based homegrown LMS is its offline capabilities. Faculty members can download the current course data–including student discussion posts, tests, etc. They can respond to posts, grade papers and tests, add announcements, and so on, all while offline, and automatically synchronize the next time they have a connection. People who haven’t used this capability (especially those who always have a broadband connection handy) don’t understand the value of this affordance, but I do. It’s for the same reason that, much as I love my GMail, there are times when I really need an email client that can work offline. Or an offline RSS feed reader. Sometimes, it’s really handy to not have to be connected. And that’s doubly true for faculty members who are not gadget freaks, live in rural areas, and are unlikely to have ubiquitous broadband (or any broadband at all).
Anyway, like it or not, we’re on the hook to reproduce that capability in our next-generation system. This is a somewhat daunting challenge. Not that it’s rocket science; synchronization has been done many times in many different ways, and there are any number of existing code bases that we could draw from. Rather, it’s daunting because it’s a lot of work to do at all and a lot more work to do right. Developing and, even worse, QA testing a cross-platform fat client in an environment where you have no control whatsoever over the profile of the client machines is a pretty large task, even if you draw on an existing cross-platform technology base such as Eclipse RCP or Mozilla Firefox.
A while back, I wrote a bit about some relatively new possibilities for re-implementing the fat client experience with…er…less fat. At the time, though, I was focusing more on the user experience; I didn’t really get into the whole synchronization issue.
As of yesterday, it looks like there may be a nice, lightweight solution to offline synchronization on the horizon, courtesy of none other than Ray Ozzie–the original inventor of Lotus Notes and now Microsoft’s CTO. (more…)
-
Lean Clients, Plump Clients, and Chubby Clients for Learning Management Systems
As I mentioned in a previous post the SUNY Learning Network currently uses a home-grown learning management system built on top of Lotus Notes. And while there is a web interface to the system, many of the current users are quite attached to their fat client.
This may sound quaintly outdated at the moment. However, I strongly suspect that we’ll see fat(ter) LMS clients in the near future. There are some wonderful affordances that come with a more robust client-side component to the system. Up until now, those affordances have come with the relatively steep price of having to develop, install and maintain fairly heavy-duty (and often cross-platform) client-side software. But that’s changing. These days, the browser and the operating system themselves are increasingly able to function as client-side platforms for richer functionality. Add to this the blossoming of web services and the small, simple client-side tools that they enable, and we have the potential for what I would call “lean clients,” “plump clients” and “chubby clients.” (more…)