After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351348 - Have a renderer plugin API
Have a renderer plugin API
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: backends
unspecified
Other Linux
: Low enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-14 19:14 UTC by Bastien Nocera
Modified: 2007-12-28 18:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2006-08-14 19:14:53 UTC 
So new formats can be added without needing to recompile and/or modify evince.
This could be useful for non-free, reverse-engineered, proprietary, and legally-sensitive plugins.
Comment 1 Nickolay V. Shmyrev 2006-08-20 23:40:07 UTC 
Actually I am a bit agains plugins as they are usually considered, but it would be  nice to automatically load some binary files in some dir.
Comment 2 Bastien Nocera 2006-10-16 15:05:31 UTC 
Well, that's just what plugins are really ;)
Comment 3 Wouter Bolsterlee (uws) 2006-11-04 21:55:22 UTC 
Perhaps we should call it "pluggable backends" instead of "plugins". I guess you mean something along the lines of gtk+'s pixbuf backends and gstreamer codecs?
Comment 4 Wouter Bolsterlee (uws) 2006-11-05 11:10:22 UTC 
Changing component. Filter on "uws doing evince component triaging" to get rid ofthe spam.
Comment 5 Carlos Garcia Campos 2007-12-28 18:18:21 UTC 
Fixed in svn trunk.