
W dniu 28 grudnia 2009 19:53 użytkownik Jon Cruz <jon@...18...> napisał:
The limitation is for *in-band* data transfer. There standard ways that Jabber does *out-of-band* file transfers. This is common for most any instant messaging protocol.
Oops, sorry. I didn't read it to the end :/
Solution: never link external media assets, only embed them. This results in 100% consistent behavior.
Now you are using a straw man, because that was not my solution. It was: embed by default on paste and DnD and provide embed/link radio button in the import dialog, which is initially set to embed. "By default" means the behavior could be changed to always link on paste/DnD, by going to the prefs dialog. Further improvements could include making embed/extract actions better discoverable, and several other improvements that you mentioned, but even this small change could fix the missing data problem, which is the most severe. I stated at least twice that I have completely no issue with comprehensive link support, as long as it is kept out of sight of the clueless.
Embedding doesn't break anything for user B, only introduces a minor inconvenience (he has to extract the images, turning them into links). It doesn't preclude B from using links, or A learning about them some time in the future, but it avoids the broken document that discourages them to learn more about Inkscape.
Regards, Krzysztof