i’ve been using groove for as long as you’ve been able to download the builds. i’ve found it adequately useful out-of-the-box for fostering lightweight collaboration and file sharing between work and home, but it desperately needs customized applications before any real uptake is going to occur. beyond what’s at the groove devzone, it’s disconcerting that i haven’t seen more “hello world” style articles that introduce the groove programming model to independent developers.

maybe using xml to configure groove is the start of more exposure:

“This article examines the use of XML to configure custom applications for Groove, a peer-to-peer groupware platform.”

“Programmers with a solid understanding of XML will have less trouble than others making the transition to building Groove tools. XML plays is a significant part of the Groove architecture. Though most of the work required to develop Groove tools involves writing code in JavaScript, VB, or C++ to control the tool application logic, there are four XML files that developers have to configure to allow users access to their custom tools. The rest of this article will examine these files and their roles.”

Leave a Reply