Difference between revisions of "Improved Media Management"

From Inkscape Wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
=Issues=
 
=Issues=
  
* Pasting writes a PNG file with a bogus name into the directory of the document and creates a link; this prevents pasting into a document opened from a read-only folder and causes broken links when the file is sent to somebody else
+
* Pasting writes a PNG file with a bogus name into the directory of the document and creates a link. If the document wasn't saved yet, it saves it to some arbitrary directory (home dir on Linux, Inkscape installation dir on Windows).
 +
* Importing and DnDing a raster image creates links to the originals.
 +
 
 +
Here are the effects:
 +
* Pasting an image into an unsaved document on Windows requires administrator privileges. (WTF!!!)
 +
* Not possible to paste into a document opened from a read-only directory.
 +
* Completely unexpected location of images pasted into an unsaved document.
 +
* If the user forgets to send the linked images, SVGs sent to others via e-mail or other means are broken.
 +
* By using "Edit externally", a user unaware of links can overwrite valuable images.
 +
* Inconsistent with SVG behavior: SVGs are always embedded.
 +
* Copying the image to a web server results in a broken image; users unaware of links might blame the browser or the web server rather than Inkscape (see [https://bugs.launchpad.net/inkscape/+bug/415374 example])
 +
 
 +
The e-mail problem must be fixed on the sender's side, because only he has access to complete data. The solution must involve combining raster data with the SVG, so that they reside in the same file.
  
 
=Use Cases=
 
=Use Cases=

Revision as of 02:54, 28 December 2009

Overview

This set of issues generally is first seen due to problems managing linked vs. embedded images. However it quickly becomes clear that the underlying principals and problems extend across the board to many things including CSS files, ICC profile files, etc.

Issues

  • Pasting writes a PNG file with a bogus name into the directory of the document and creates a link. If the document wasn't saved yet, it saves it to some arbitrary directory (home dir on Linux, Inkscape installation dir on Windows).
  • Importing and DnDing a raster image creates links to the originals.

Here are the effects:

  • Pasting an image into an unsaved document on Windows requires administrator privileges. (WTF!!!)
  • Not possible to paste into a document opened from a read-only directory.
  • Completely unexpected location of images pasted into an unsaved document.
  • If the user forgets to send the linked images, SVGs sent to others via e-mail or other means are broken.
  • By using "Edit externally", a user unaware of links can overwrite valuable images.
  • Inconsistent with SVG behavior: SVGs are always embedded.
  • Copying the image to a web server results in a broken image; users unaware of links might blame the browser or the web server rather than Inkscape (see example)

The e-mail problem must be fixed on the sender's side, because only he has access to complete data. The solution must involve combining raster data with the SVG, so that they reside in the same file.

Use Cases

Cases

  • Arthur wants to create a collage using some bitmaps. He drags 2 images from Firefox into an SVG document, pastes a third one from GIMP and imports 4 other from his photo folder. He saves the document and sends the SVG using e-mail to a friend. He doesn't know much about links, so he does not include the original images in his e-mail.
  • Issa works on a multi-user system at an university. She opens a scientific poster template from a shared read-only folder. She pastes photos of samples into the document, then saves the poster in her home folder.
  • Charlie uses Inkscape to add vector frames to his photos. He wants to be able to post-process the images without updating the SVG document. He creates an image link.
  • Sara is a web designer and has SVG documents with lots of absolute image links. She moves all the images to another folder. The links break, which is not surprising to her. She wants to fix all the links at once.
  • Billy wants to edit an image embedded in the SVG document he received from Arthur.

Personas

Use cases are helpful, but in order to gain the most we need to know who are the users under discussion. This is a general Usability Design issue and we have some overall information being collected under our wiki section on User Personas. The specific user personas referenced in these cases on this page are:

  • Arthur - 40-year old department store owner and amateur photographer who uses Windows. He has no idea what SVG stands for, but is familiar with pasting images into MS Word documents.
  • Issa - 21-year old undergrad student of chemistry with some generic Unix experience, but no SVG or Web technologies experience.
  • Charlie - 35-year old US Navy nuclear propulsion engineer on an overseas deplyoment who misses his family and likes to learn time-saving tricks.
  • Sara - 30-year old Web designer with extensive knowledge of Web technologies and some experience with hand-tweaked SVG documents.
  • Billy - 16-year old son of Arthur, a high school student and Wikipedia contributor experimenting with free software. Uses Inkscape from time to time to update world maps and draw diagrams.

Proposals

  • Default to embedding images when pasting and DnDing pixel data
  • When DnDing a file, ask whether to embed or to link
  • Add a link option to the import dialog that defaults to off
  • Embedded images as hybrid links: embedded raster data with info about its original location. If the original file exists, it is watched for modifications and updated

HID