Difference between revisions of "Evince"

From Sugar Labs
Jump to navigation Jump to search
(The job finished record is already part of this page. It can be replaced by a new version by Evince developers, but holds relevant history until such time.)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
The Read activity and other components in Sugar that display PDFs use [http://live.gnome.org/Evince evince] for that.
 
The Read activity and other components in Sugar that display PDFs use [http://live.gnome.org/Evince evince] for that.
  
In order to be able to embed evince inside other components, we have had to do the following modifications:
+
These tickets track the effort to upstream the changes we had to do:
  
* build evince as a dynamic library
+
* None! This job is finished ;)
  
* add python bindings to that library
+
Done
  
* expose document info to embedders
+
* [http://bugzilla.gnome.org/show_bug.cgi?id=568287 Add python bindings for evince]
 
+
* [http://bugzilla.gnome.org/show_bug.cgi?id=567789 Make EvDocumentInfo and friends GTypes]
And now we need to upstream all that before distros can provide an evince that Sugar can use.
+
* [http://bugzilla.gnome.org/show_bug.cgi?id=567788 Make EvJobPriority a proper GType]
 +
* [http://bugzilla.gnome.org/show_bug.cgi?id=567751 move reusable code into a shared library so other apps can display documents using evince code]
 +
* [http://bugzilla.gnome.org/show_bug.cgi?id=567785 Expose ev_view_set_zoom_for_size for embedders to use]
 +
* [http://bugzilla.gnome.org/show_bug.cgi?id=567790 Expose stuff needed by the python bindings]
 +
* [http://bugzilla.gnome.org/show_bug.cgi?id=567787 Add evince_embed_init so embedders can init threads and evince internals]
 +
* Exception to the feature freeze requested: http://mail.gnome.org/archives/release-team/2009-January/thread.html#00109

Latest revision as of 20:57, 19 December 2016