On Thu, 2009-10-22 at 22:50 -0700, Jon A. Cruz wrote:
On Oct 22, 2009, at 3:51 PM, Alvin Penner wrote:
Of course, that doesn't mean we should make image links easier to use,
just that we should not default to creating them.
What it comes down to is that you will confuse half the users, depending on which way you default. That is, if you default to only linking images you will confuse/annoy those who expect embedded. However, if on the other hand you default to always embedding images, you will confuse/annoy those who expect linked.
Indeed.
Having a switch in preferences would be bad, because the user has to be aware o what it is set to. Also means you have to first go there if you need to change it depending on project-specific needs.
An option in Import dialog would be better. Or even having 2 entirely separate actions.
Of course that wouldn't answer what to do in the drag-and-drop case :/
As this issue affects all kinds of graphic and sound applications, I have been thinking about a solution on another level. This would require linking to objects via IDs, so you can move stuff around without breaking links. Dependency tracking and automatic bundling once your stuff leaves your system.