OpenWetWare:Software/Image Editor - Revision history

Vincent Rouilly at 17:15, 24 November 2006

Vincent Rouilly — Fri, 24 Nov 2006 17:15:12 GMT

←Older revision		Revision as of 17:15, 24 November 2006
Line 2:		Line 2:
	==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 ...).
		+	**MediaWiki is already providing a limited support for SVG; however it is based on a SVG->PNG rasterization (ImageMagic library). Also, as any other XML languages, SVG is really wordy and not so friendly to directly edit as an xml document. Graphical editors are needed.
	*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.
	*No way to link pages to graphical objects in an image.		*No way to link pages to graphical objects in an image.
		+
		+	==Practicals==
		+	Examples based on the current level of SVG support provided by mediaWiki (ImageMagik SVG-->PNG rasterization):
		+	*[[OpenWetWare:Software/Image Editor/Gel annotation \| Gel annotations]]
		+	*[[OpenWetWare:Software/Image Editor/Petri dish annotation \| Petri dish annotations]]
		+	*[[OpenWetWare:Software/Image Editor/Graph \| Graph]]

	==A new way to handle images/drawings==		==A new way to handle images/drawings==
Line 24:		Line 31:

	==Related projects==		==Related projects==
		+	*[http://www.inkscape.org inkscape]: OpenSource SVG Editor
	*[http://xml.apache.org/batik Batik]: SVG library		*[http://xml.apache.org/batik Batik]: SVG library
	*[http://www.iath.virginia.edu/inote/ iNote] (not SVG compliant)		*[http://www.iath.virginia.edu/inote/ iNote] (not SVG compliant)

Vincent Rouilly: /* Current wiki limitations with regards to images */

Vincent Rouilly — Sat, 11 Nov 2006 01:59:58 GMT

Current wiki limitations with regards to images

←Older revision		Revision as of 01:59, 11 November 2006
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.

Vincent Rouilly at 01:59, 11 November 2006

Vincent Rouilly — Sat, 11 Nov 2006 01:59:12 GMT

←Older revision		Revision as of 01:59, 11 November 2006
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	==Current wiki limitations with regards to images==		==Current wiki limitations with regards to images==
-	*~~Images~~ are handled as a bunch of pixels ~~in mediaWiki~~ (through ~~standard~~ 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. ~~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.
-	*No way to link pages to graphical objects in an image	+	*No way to link pages to graphical objects in an image.

	==A new way to handle images/drawings==		==A new way to handle images/drawings==
	*Use a text-based drawing language to benefit from the wiki history mechanism.		*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 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==		==Proposed architecture==
-	*Drawing description would be SVG based and stored on a standard ~~wiki~~ page.	+	*Drawing description would be SVG based and stored on a standard Wiki page.
	*PNG, JPEG, GIF images can be handled within SVG.		*PNG, JPEG, GIF images can be handled within SVG.
-	*Java ~~Applet~~ embedded into ~~the wiki~~ page where the image has to be shown.	+	*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.		*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.
-	*Provide a way to link subregions of an image to wiki pages or URLs
-	*Make computer-generated images feasible

	==Benefits==		==Benefits==
	*Can be used to replace powerpoint-like graph.		*Can be used to replace powerpoint-like graph.
-	*~~allow~~ collaborative annotations over real experimental data (gels, culture plates, random pictures).	+	*Would enable collaborative annotations over real experimental data (gels, culture plates, random pictures).

	==Related projects==		==Related projects==
Line 29:		Line 30:

	==Comments==		==Comments==
-	*this xml-type/applet-based architecture could be easily extended to ~~other~~ features (graph, gene annotations, ...)	+	*this xml-type/applet-based architecture could be easily extended to implement new features (graph, gene annotations, ...)

	=Road Map=		=Road Map=

Tk: /* Proposed architecture */

Tk — Sat, 11 Nov 2006 00:54:18 GMT

Proposed architecture

←Older revision		Revision as of 00:54, 11 November 2006
Line 16:		Line 16:
	*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.		*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.
	*Provide a way to link subregions of an image to wiki pages or URLs		*Provide a way to link subregions of an image to wiki pages or URLs
		+	*Make computer-generated images feasible

	==Benefits==		==Benefits==

Tk: /* Proposed architecture */

Tk — Sat, 11 Nov 2006 00:53:11 GMT

Proposed architecture

←Older revision		Revision as of 00:53, 11 November 2006
Line 15:		Line 15:
	*Java Applet embedded into the wiki page where the image has to be shown.		*Java Applet embedded into the 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.		*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.
		+	*Provide a way to link subregions of an image to wiki pages or URLs

	==Benefits==		==Benefits==

Tk: /* Current wiki limitations with regards to images */

Tk — Sat, 11 Nov 2006 00:51:52 GMT

Current wiki limitations with regards to images

←Older revision		Revision as of 00:51, 11 November 2006
Line 4:		Line 4:
	*No easy way to update/edit an image from the wiki. 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. 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.
		+	*No way to link pages to graphical objects in an image

	==A new way to handle images/drawings==		==A new way to handle images/drawings==

Vincent Rouilly at 00:23, 11 November 2006

Vincent Rouilly — Sat, 11 Nov 2006 00:23:55 GMT

←Older revision		Revision as of 00:23, 11 November 2006
Line 27:		Line 27:
	==Comments==		==Comments==
	*this xml-type/applet-based architecture could be easily extended to other features (graph, gene annotations, ...)		*this xml-type/applet-based architecture could be easily extended to other 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

Barry Canton: OWW Image Editor moved to OpenWetWare:Software/Image Editor: adding it to the main software discussion section

Barry Canton — Fri, 10 Nov 2006 19:27:47 GMT

OWW Image Editor moved to OpenWetWare:Software/Image Editor: adding it to the main software discussion section

←Older revision

Revision as of 19:27, 10 November 2006

Vincent Rouilly at 18:23, 10 November 2006

Vincent Rouilly — Fri, 10 Nov 2006 18:23:15 GMT

New page

__NOTOC__
==Current wiki limitations with regards to images==
*Images are handled as a bunch of pixels in mediaWiki (through standard such as PNG, JPEG, GIF ...).
*No easy way to update/edit an image from the wiki. 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.

==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.

==Proposed architecture==
*Drawing description would be SVG based and stored on a standard wiki page.
*PNG, JPEG, GIF images can be handled within SVG.
*Java Applet embedded into the 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.
*allow collaborative annotations over real experimental data (gels, culture plates, random pictures).

==Related projects==
*[http://xml.apache.org/batik Batik]: SVG library
*[http://www.iath.virginia.edu/inote/ iNote] (not SVG compliant)
*[http://freshmeat.net/projects/glipsgraffiti/ glipsgraffiti]: SVG editor
*[http://www.kiyut.com/products/sketsa/index.html Sketsa]

==Comments==
*this xml-type/applet-based architecture could be easily extended to other features (graph, gene annotations, ...)