Evince: Difference between revisions

← Older edit Newer edit →

@@ Line 3: / Line 3: @@
 In order to be able to embed evince inside other components, we have had to do the following modifications:
-* build evince as a dynamic library: http://bugzilla.gnome.org/show_bug.cgi?id=567751
+* [http://bugzilla.gnome.org/show_bug.cgi?id=567790 Add python bindings for libevince]
+* [http://bugzilla.gnome.org/show_bug.cgi?id=567789 Make EvDocumentInfo and friends GTypes]
-* add python bindings to that library
+* [http://bugzilla.gnome.org/show_bug.cgi?id=567788 Make EvJobPriority a proper GType]
+* [http://bugzilla.gnome.org/show_bug.cgi?id=567787 Add evince_embed_init so embedders can init threads and evince internals]
-* expose document info to embedders
+* [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=567751 move reusable code into a shared library so other apps can display documents using evince code]
-And now we need to upstream all that before distros can provide an evince that Sugar can use.