Eric Meyer (and a few others in his comments area) has suggested that the table top in the Tiger iChatAV app might be useful for more than just pretty reflections. What if it also served as a place to share documents? Either as icons (which, when clicked, would open said document), or as thumbnail icons that enlarge when selected.

I would absolutely LOVE this feature. Ideally, it would support sharing of static documents (PDF, images), "live" collaborative documents (SubEthaEdit workspaces), and, perhaps even group web browsing (select a web page document, and follow along with whoever is leading that document browse session...).

I just posted some pics from our trip to Vancouver and Victoria for the NMC 2004 Summer Conference.

View the photos

Bluestream just released the next version of their XStreamDB XML database server.

Perhaps the biggest part of the release isn't even in the software - it's in the licensing. It's now about half the cost of what we paid, and it's free for teaching. If you're teaching XML, you can download it and just go. Student projects, etc... It's all good.

There are also a bunch of great changes under the hood - scored search results, performance improvements, and other goodness.

Or, in this case, from the UK. Last night 190 spam crap comments were added to this weblog (in a span of about 20 minutes).

Despite using the MT-Blacklist plugin, ported to Blosxom. I've gone through and deleted the 190 spam crap comments. I've also turned off addition of new comments to existing comment threads. It's easy to remove comment posts when they're just spam. It's harder when it's added into existing content...

Just came across this: According the the preview page, Tiger is coming with Blosjom bundled. Blosjom is a java port of the Blosxom software the currently powers this weblog...

Looks like there may not be a satellite feed for the Stevenote this year. Failing that, there's the O'Reilly coverage, as noted on their MacDevCenter...

Before leaving for the NMC 2004 Summer Conference, I handed King the code I'd hacked together to implement XML KeyValueCoding and the XStreamDB EOAdaptor. He needed the XML KVC part to implement an ECL client in APOLLO, so it should have worked just fine.

In usual King form, he went through my code, and when he was done, it looked like part of the EOF stack itself - all of the niggly loose ends I was struggling with were properly cauterized - no, that's too rough - they were reworked with Best Practices and EOF methodology so they worked properly, rather than just working (yes, there is a distinction ;-) ).

I'm sure this is going to be linked all over the place, but it's a very interesting read. It's a reposting by David Gristwood, of an original article by Jim McCarthy (a manager on the MS Visual C++ team).

Particularly interesting and useful, it delves into the topic of "slippage", but treats it as a necessary and good part of the process. Slippage becomes a transition from the unknown to the less unknown - as you know more, the timeline and estimates become more refined and realistic, often leading to slippage.

We're working on a whole bunch of related (and sometimes dependent) projects here at the Learning Commons, and it's sometimes difficult to communicate how they all fit together.

Although we are coming at several related problems from several directions simultaneously, we see them all as One Big Project, with each component making up part of a larger puzzle. Here's the extremely simplified model of how the projects fit together:

Perhaps the easiest way of thinking about these projects is with APOLLO acting as a kind of malleable glue that can hold distinct and separate technologies together. We see things like ties to Blackboard LMS happening somehow via APOLLO, which can serve as a bridge between any of the other project puzzle pieces.

Scott Leslie is heading up a rather large initiative in BC to deploy some cool whiz-bang learning object technology across the province for a couple of very large organizations. His group recently made a decision on which technologies they were going to use, and they picked APOLLO.

Scott has written up an excellent description of his rationale, plan, and hopes for the BC/APOLLO collaboration. I really like his pragmatic stance - use what's best for the job, and for the users. He likes Open Source, but isn't married to it. He likes commercial software, but will use something else if it's a better fit.

• Even a decentralist wants a system to work
• Provide the wires and power and let it go
• Provide the interfaces
• Decentralists are not de-connected
• not isolationsists
• not vandals
• community based on a shared platform
• rapid group forming, ridiculously easy group forming and problem solving, group comes together and disappears when the need is gone
• ad hoc!
• kind of like affinity groups from Henry Jenkins keynote
• don't have to stay together forever
• don't define ourselves in terms of communities, define ourselves in terms of ourselves
• we can use the best available tools whenever we want
• need to post our manifesto on the wiki
• centralists are like IT
  • centralists keep power flowing, WiFi working
• what are great successes that we can cite
  • scientific discovery is decentralized
  • great art is decentralized
  • web is decentralized
• The centre will not hold
• University of Calgary still only supports Netscape 4.7
• decentralism is Darwinian, 1000 will be culled out, some will survive
• the more centralized, the more standards get lower
• the Dodge Caravan ads hammer the message join the team
• decentralists think!
• D'Arcy: "could have gone down hill but it didn't"
• Brian, D'arcy, Alan met after doing a presentation on RSS, blogs and Wikis
  • decentralized collaboration works
  • decentralized, virtual collaboration requires a different skill set than real world face to face collaboration but the skillsets are complementary

The NMC 2004 Small Pieces session yesterday went extremely well (I think ;-) ) - it was very chaotic, noisy, confusing, loud, and messy, but I think it was interesting or at least entertaining for all.

There was activity on the wiki, some on the weblogs, and some iChatAV video conferences. The Decentralists group wound up too deep in a very compelling discussion to break away for iChatAV. Our discussion turned into one of the most vibrant and engaging experiences I've had in quite a while (thank you Decentralists!)