> That's because OpenGroupware doesn't *need* to provide a client. They > support standards, so all the existing clients Just Work. Although the Kolab > format is open (IMAP+ftp access to vcards, etc.), it's not a protocol > combination any existing clients support, or are ever likely to support, so > unlike OGo Kolab has to make their own client.... For example, look at > Evolution or Mozilla. Both work with OGo. Neither work with Kolab. It's > again getting back to openness. OGo lets you choose your clients. Kolab > doesn't. OGo lets you choose your servers. Kolab doesn't. a plugin for Evolution would be just as logical, or maybe even more logical to build for Kolab, since kolab's specs are open, whereas the plugin for OGo is the Exchange plugin, which is, at best, a screenscraper-like solution to get data from Exchange-webaccess server-like servers. Mozilla's calendar is pretty cool, but also pretty unfinished, and so, no real OGo client exists in the totally free world. If OOo's project takes off, and Evolution or Mozilla gets open/complete OGo implementations, then, and only then, can OGo be considered a full product. Maarten
