TODO 2.12 KB
Newer Older
Dom Lachowicz's avatar
Dom Lachowicz committed
Higher priority:

Dom Lachowicz's avatar
Dom Lachowicz committed
3 4 5 6
 * Make our GdkPixbuf dependency optional, for broader adoption in other communities (eg. OpenGL games). We'll want to use 
   ARGB internally. We'll keep the GdkPixbuf-based public interface around, but split up the libraries somewhat. We may want
   to use it to load PNGs/JPEGs/etc., but that piece of code's implementation will be flexible so that it isn't exclusively
   dependant on GdkPixbuf.
7 8 9 10 11 12 13 14 15

 * Improvements to the Mozilla plugin
	* Possibly use a Cairo backend to draw directly onto Mozilla's Drawable, rather than using our XEmbed hack.
		* Should enable proper translucency, but could be SLOW
	* Enable printing support, integrated with Mozilla's (
		* Ideally would use Cairo->PS for this
			* In a pinch, embedding a PNG inside of a PS snippet would also work

 * Areas in need of improvement:
Dom Lachowicz's avatar
Dom Lachowicz committed
	* multiImage
17 18 19 20
	* Text
		* Whitespace issues
		* "International" issues - bi-directional, top->bottom, etc.
		* Text along paths
21 22
		* Remove pango compeletly since it isn't thread safe nor does it support SVG text very well.
		* Create interface to allow text to be drawn by cairo directly if available
23 24 25 26
	* Fonts
		* CSS-defined fonts (do we want to support this?)
		* SVG fonts (do we want to support this?)

Dom Lachowicz's avatar
Dom Lachowicz committed
27 28
 * Improved GError support in the loader and error propegation, rather then the g_warnings that we currently use.
	 * Make error messages translatable (requires adding gettext).

30 31
Lower Priority:

Dom Lachowicz's avatar
Dom Lachowicz committed
32 33 34 35 36 37
 * Improvements to the rsvg-view application
	* Add panning
	* Add menus
	* Set a better size hint
	* Use cairo

38 39 40 41 42 43
 * Any SVG 1.2 features that we want to sneak in. SVG 1.2 conformance is not a priority. Top candidates include:
	* <pageSet>

 * Improved Gimp plugin (choose 1 of "A" or "B". "A" would be easier, but perhaps less compelling. Jimmac and Tigert would be estatic if we could do either.)
	* A) Store layer names, composite layers onto the Gimp itself
	* B) Implement a Gimp-based RsvgRender that drew SVGs in terms of Gimp's path, gradient, pattern, etc. APIs
44 45 46 47

* DOM interface, possibly javascript bindings.

* Animation, should be easier if DOM is done right.