Every place I've worked has been in need of something like this. I don't think they've wanted to invest in a fancy/expensive/proprietary system, something open-source would fit great here.
CVS can be too complicated for the non-techies. mod_dav on apache already makes a nice way to publish documents from a windows box (just use the MS web-folders icon). Hopefully, the versioning extensions to DAV will be sufficient for managing the versions, but I don't think that part's ready for prime time yet.
By the way, subversion (CVS replacement) is closely related, its network protocol is DAV based I believe.
I'm impressed with the KDE developers ability to come up with new technology when the existing tools don't seem to fit, eg backing off from CORBA for embedding local components and coming up with something (hopefully) better.
But are you sure its wise to develop an entire new scripting language, kscript, which seems to be part of koffice. As you know, there's no shortage of scripting languages out there already.
I suggest you revisit your earlier decision to move away from an established language (I believe at one time you were going with python). Perhaps some the reasons to abandon python have changed, like no longer having to get it to play as nice/efficiently with mico.
At any rate, you need to present a good case for your scripting language, be it kscript or other. And don't restrict it just to koffice! Good scripting is a powerful feature.
Slashdot Mirror
Every place I've worked has been in need of something like this. I don't think they've wanted to invest in a fancy/expensive/proprietary system, something open-source would fit great here. CVS can be too complicated for the non-techies. mod_dav on apache already makes a nice way to publish documents from a windows box (just use the MS web-folders icon). Hopefully, the versioning extensions to DAV will be sufficient for managing the versions, but I don't think that part's ready for prime time yet. By the way, subversion (CVS replacement) is closely related, its network protocol is DAV based I believe.
But are you sure its wise to develop an entire new scripting language, kscript, which seems to be part of koffice. As you know, there's no shortage of scripting languages out there already.
I suggest you revisit your earlier decision to move away from an established language (I believe at one time you were going with python). Perhaps some the reasons to abandon python have changed, like no longer having to get it to play as nice/efficiently with mico.
At any rate, you need to present a good case for your scripting language, be it kscript or other. And don't restrict it just to koffice! Good scripting is a powerful feature.