Re: Can I make global changes to the default file management options?

On Jun 3, 2010, at 4:06 AM, Geoff Barnes wrote:
> I don't know that it would solve the problem I'm experiencing to be =
able to always link vs. embed. It would be helpful in a way, but the =
ideal solution would be a true embed, where the placed image's encoding =
is placed directly into the plist.
[....]
> A true embed would do conflict incidence reduction just as well as =
flat files do, while preserving our ability to resolve conflicts =
item-by-item - at the plist level - when they arise.

I'm not sure what the difference is between what you describe as "true =
embed" and flat files. Right now there are three ways a Graffle document =
can have an image:
   - a file package. The graffle document is a directory containing a =
plist file and a bunch of image files (.png or whatever).
   - a flat file. The graffle document is a single file, and any images =
are contained in the file as big base64-encoded blobs.
   - "linking", where the document has a relative path to the image =
file, but doesn't actually contain the image. Less conflict-prone, but =
if the file or image moves, the link breaks.

The default behavior is to save a document as a package if it has any =
images, simply because images tend to be large, unchanging chunks of =
data and keeping them in their own files speeds up a number of things.

> Anyone else experience pain from this, or am I way off to the edge?

We try to make Graffle play well with version control (we use it with =
svn internally) but it's not a very often-requested feature. Bug reports =
describing how people are actually using OG with version control are =
useful.

What sequence of events is it that's causing the most conflict pain for =
you? Two different users adding images and ending up with images =
assigned the same image####.png filename?