Difference between revisions of "Evince"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
In order to be able to embed evince inside other components, we have had to do the following modifications: | 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 | + | * build evince as a dynamic library: http://bugzilla.gnome.org/show_bug.cgi?id=567751 |
* add python bindings to that library | * add python bindings to that library | ||
Revision as of 10:40, 14 January 2009
The Read activity and other components in Sugar that display PDFs use evince for that.
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
- add python bindings to that library
- expose document info to embedders
And now we need to upstream all that before distros can provide an evince that Sugar can use.