| Server IP : 79.136.114.73 / Your IP : 13.58.37.107 Web Server : Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.29 OpenSSL/1.0.1f System : Linux b8009 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/librsvg2-2/ |
Upload File : |
Higher priority: * 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. * Areas in need of improvement: * multiImage * Text * Whitespace issues * "International" issues - bi-directional, top->bottom, etc. * Text along paths * 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 * Fonts * CSS-defined fonts (do we want to support this?) * SVG fonts (do we want to support this?) * 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). Lower Priority: * Improvements to the rsvg-view application * Add panning * Add menus * Set a better size hint * Use cairo * 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 * DOM interface, possibly javascript bindings. * Animation, should be easier if DOM is done right.