OpenWetWare talk:Software/Image Editor: Difference between revisions
No edit summary |
m (SVG image support) |
||
| Line 7: | Line 7: | ||
Other things like graphs and chemical diagrams (see [[Amino acids]]) are already doable. What's missing may be a WYSIWYG editor also. | Other things like graphs and chemical diagrams (see [[Amino acids]]) are already doable. What's missing may be a WYSIWYG editor also. | ||
== SVG image support == | |||
--[[User:Vincent|Vincent]] 14:51, 11 November 2006 (EST): That's right, SVG is already handled within MediaWiki (see [http://meta.wikimedia.org/wiki/SVG_image_support documentation]). However, it is quite a limited use of SVG as SVG files are PNG rasterized. It prevents to benefit from the all world of SVG interactivity (animations, links). | |||
But at the end I agree that for some '''static''' vector graphics, it could be better to rely on SVG rasterization instead of having to use an applet as a viewer (which might be slow to launch). | |||
As you mentionned, the editing of SVG still lacks some sort of ergonomy. It should be handled by a graphical interface(e.g.applet). It would be too constraining to ask users to update raw SVG files. | |||
Revision as of 12:51, 11 November 2006
Austin Che 22:55, 10 November 2006 (EST): Some of the comments on the limits aren't really true. For example, you can embed SVG already using wikitex. For example:
<svg> <rect fill="red" stroke="black" x="15" y="15" width="100" height="50"/> <circle fill="yellow" stroke="black" cx="62" cy="135" r="20"/> </svg>
Other things like graphs and chemical diagrams (see Amino acids) are already doable. What's missing may be a WYSIWYG editor also.
SVG image support
--Vincent 14:51, 11 November 2006 (EST): That's right, SVG is already handled within MediaWiki (see documentation). However, it is quite a limited use of SVG as SVG files are PNG rasterized. It prevents to benefit from the all world of SVG interactivity (animations, links). But at the end I agree that for some static vector graphics, it could be better to rely on SVG rasterization instead of having to use an applet as a viewer (which might be slow to launch).
As you mentionned, the editing of SVG still lacks some sort of ergonomy. It should be handled by a graphical interface(e.g.applet). It would be too constraining to ask users to update raw SVG files.
