At 11:30 AM -0800 3/14/02, Rob Bloodgood wrote: >The problem is, concurrency. Dreamweaver has versioning built in... but >emacs has no way to recognize it. So when I make a fix to a file, if the >designers aren't explicitly instructed to refresh-from-the-website-via-ftp, >my changes get hosed.
Versioning, no. Locking, yes, optionally. (Well, I guess it can do versioning via SourceSafe, but not via anything else.) I'm seriously hoping they'll address that in the next release. >I've been trying, in various attempts over the past two years, to come up >with a compromise between the two. The closest I've come was somebody >mentioned a CVS emulation layer over a DAV repository... but that never came >to fruition. And even more frustrating, I haven't managed to pick up enough >eLisp to do it myself w/ vc.el <sigh>. > >Does anybody have any ideas for my next direction to turn? There are WebDAV extensions under development to provide versioning. I suspect that eventually we'll see those supported. But that's got to be a year or more down the road. Emacs over WebDAV should work fine if you run something that supports WebDAV as a filesystem (e.g. OSX), but that's not going to help you much. There are two options I can think of. 1. If your designers aren't making use of checkin/checkout in DreamWeaver, then simply make it clear to them that before they can save a file to the server, they have to do a sync first. Make the final repository sit on CVS, and do a checkin every night. So if something does go wrong you can at least pick up the previous day's work. 2. DreamWeaver's locking mechanism is handled by placing lock files on the server. Those files have the info about who has what. It ought to be possible to write an emacs extension that would use those files. -- Kee Hinckley - Somewhere.Com, LLC http://consulting.somewhere.com/ [EMAIL PROTECTED] I'm not sure which upsets me more: that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's.
