> [Drifting (even further) off topic here...] > > On Fri, 20 Apr 2012 14:25:59 -0400 > Miles Fidelman <mfidel...@meetinghouse.net> wrote: > > Mike Meyer wrote: > > > On Fri, 20 Apr 2012 10:26:26 -0700 > > > Andreas Kupries<andre...@activestate.com> wrote: > > > > > >> On 4/20/2012 7:34 AM, Mike Meyer wrote: > > >>> ... Things like architectural diagrams wind up there, and ... > > >> I like to program my diagrams, instead of drawing them. Easier to > change, and > > >> the code (aka text) is nicer to version than some binary blob. > > > If I don't need to work on such collaboratively, I'll use graphviz for > > > the same reasons. But google docs is easier to get other people to > > > contribute to. > > > > Don't know about google docs - no real version control. Unusable for > > anything serious, like a multi-author paper or proposal. I always end > > up sharing Word Documents, with change tracking, via email. Gets ugly > > with more than a few people. > > I'm still exploring how google docs fits into a small team. So far, > I've just used it for one-page diagrams, and it's worked well there. > > Word, on the other hand - never again. The differences between > implementations - different programs, different versions of the same > program, the same version on different platforms - is just to > painful. In one case, I saw word documents that would cause some > *machines* to crash when opened. Other machines (presumably using the > same version of word) would open them just fine. Saving the doc > unaltered on those machines created a doc that didn't cause other > machines to crash. >
have you tried MSFT's answer to google docs (SkyDrive + Office Apps)? I've used it myself (I live in the win ecosystem) for on-the-go Word, PowerPoint, and OneNote editing and it works great as a replacement. Tomek
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
