OpenWetWare:Software/Image Editor

From OpenWetWare

(Difference between revisions)
Jump to: navigation, search
m
m (Current wiki limitations with regards to images)
Line 1: Line 1:
__NOTOC__
__NOTOC__
==Current wiki limitations with regards to images==
==Current wiki limitations with regards to images==
-
*In MediaWiki, images, are only handled as a bunch of pixels (through standards such as PNG, JPEG, GIF ...).
+
*In MediaWiki, images are only handled as a bunch of pixels (through standards such as PNG, JPEG, GIF ...).
*No easy way to update/edit an image from the wiki. It is a static piece of information if you don't have a suitable editor to modify the image.
*No easy way to update/edit an image from the wiki. It is a static piece of information if you don't have a suitable editor to modify the image.
*No way to have a look at differences between versions of a given image.
*No way to have a look at differences between versions of a given image.

Revision as of 21:59, 10 November 2006

Current wiki limitations with regards to images

  • In MediaWiki, images are only handled as a bunch of pixels (through standards such as PNG, JPEG, GIF ...).
  • No easy way to update/edit an image from the wiki. It is a static piece of information if you don't have a suitable editor to modify the image.
  • No way to have a look at differences between versions of a given image.
  • No way to link pages to graphical objects in an image.

A new way to handle images/drawings

  • Use a text-based drawing language to benefit from the wiki history mechanism.
  • provide within the wiki a way to view/edit the image/drawing.
  • Provide a way to link subregions of an image to wiki pages or URLs.
  • Make computer-generated images feasible.

Proposed architecture

  • Drawing description would be SVG based and stored on a standard Wiki page.
  • PNG, JPEG, GIF images can be handled within SVG.
  • A Java applet would implement an image viewer/editor.
  • The applet would be embedded into a standard Wiki page where the image has to be shown.
  • The applet can switch back and forth between two modes (Viewing/Editing). Once edited, the new SVG file can be saved on its Wiki page.

Benefits

  • Can be used to replace powerpoint-like graph.
  • Would enable collaborative annotations over real experimental data (gels, culture plates, random pictures).

Related projects

Comments

  • this xml-type/applet-based architecture could be easily extended to implement new features (graph, gene annotations, ...)

Road Map

Specifications for OWW Image Editor V1

features:

  • Applet based.
  • SVG handled by Batik library
  • Display PNG, JPEG, GIF, Tiff images.
  • Display SVG graphics.
  • No animation handled.
  • Read and display SVG files from a pre-existing OWW pages.
  • No editing capabilities.


Specifications for OWW Image Editor V2

features:

  • Based on Version 1.
  • Define an editing mode to update SVG source file.
  • Enable to add, delete, scale Ellipses.
  • Enable to add, delete, scale Rectangles.
  • Enable to add, delete, scale Text in a unique color.
  • Can save changes on the OWW page.

Specifications for OWW Image Editor V3

features:

  • Based on Version 2.
  • Enable multiple colors.
  • Can create OWW page if the SVG file doesn't exist yet
Personal tools