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.
Right now, the WikiPedia (or more accurately, MediaWiki) model seems to
be really effective - what with support for multiple authors, change
tracking, discussions, etc. Starts to fall down if you want to manage
a structured document or generate printed versions as an output.
Miles
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
