Am 27.04.2011 23:47, schrieb Ryan Lewis:
> I think that poppler includes two frontends, for glib and qt, this
> provides the interface to evince and okular respectively.
And it also contains also a C++ frontent.

I cannot use the QT frontend, because we're using GTK instead of QT.

I first used the GLib API, but there are still bugs... e.g. 
https://bugs.freedesktop.org/show_bug.cgi?id=2951

So I used poppler direct, this also means I don't have to write our own 
PDF parser, than Xournal does, I use Poppler for parsing PDFs (for the 
PDF export), everything else makes anyway no sense.



Andreas

> -rhl
>
>
>
>
> On Wed, Apr 27, 2011 at 4:09 PM,
> <xournal-devel-requ...@lists.sourceforge.net>  wrote:
>> Send Xournal-devel mailing list submissions to
>>         xournal-devel@lists.sourceforge.net
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://lists.sourceforge.net/lists/listinfo/xournal-devel
>> or, via email, send a message with subject or body 'help' to
>>         xournal-devel-requ...@lists.sourceforge.net
>>
>> You can reach the person managing the list at
>>         xournal-devel-ow...@lists.sourceforge.net
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Xournal-devel digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: xournal++ cairoOutputDev.h build error (Matthew Chan)
>>    2. Re: xournal++ cairoOutputDev.h build error (Matthew Chan)
>>    3. developer consensus on XMPP library (Matthew Chan)
>>    4. Re: developer consensus on XMPP library (Andreas Butti)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sat, 23 Apr 2011 14:15:30 -0400
>> From: Matthew Chan<talc...@gmail.com>
>> Subject: Re: [Xournal-devel] xournal++ cairoOutputDev.h build error
>> To: Andreas Butti<andreasbu...@gmail.com>,     xournal-devel
>>         <xournal-devel@lists.sourceforge.net>
>> Message-ID:<BANLkTi=8dnmvhtgragzfw6buh5g9nh8...@mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On Sat, Apr 23, 2011 at 4:54 AM, Andreas Butti<andreasbu...@gmail.com>wrote:
>>
>>>   Am 23.04.2011 03:37, schrieb Matthew Chan:
>>>
>>> Hi Andreas,
>>>
>>> Last email of the night, promise =P
>>>
>>> http://thread.gmane.org/gmane.comp.freedesktop.poppler/1130/focus=1143
>>>
>>> It looks like it's an internal poppler header. We're going to need to find
>>> a way around it, or the distributions won't include xournal in their repos.
>>> Also, if it's internal, I'm not sure how long the header will stay
>>> unchanged. I'm not too clear what we can do to get around it since I'm not
>>> familiar with it.
>>>
>>> What do you think?
>>>
>>>   c) do it themselves and send us the patch
>>> OBVIOUSLY c) is the preferred way [image: ;-)]
>>>
>>>
>>> I'ts not only cairoOutputDev.h
>>>
>>> I use a lot more poppler classes.
>>>
>>>
>>> e.g. Poppler GLIB share only 2 parameter for searching, and had internal
>>> 10, so it was not working for my purpose, for PDF export I use poppler
>>> objects which are already parsed.
>>>
>>> If there is really a problem with these things, it will might be better to
>>> include Poppler in the xournal sources, because they never share all
>>> internal sources, and we need them for PDF export, else we have to write our
>>> own PDF parser library, which makes absolutely no sense and is to much work.
>>>
>> I think we might have a problem if we try and include all the poppler
>> sources. Fedora (and ubuntu/suse too I think) have a policy against bundling
>> entire libraries into a project. They need to be packaged separately. Also,
>> if poppler releases bug or security fixes later on, we'll need to merge them
>> in ourselves if we bundle the sources. It could get messy really fast.
>>
>> Maybe we can write a patch to poppler that exposes those functions you need?
>>
>>
>>
>>
>>> An example: void PdfObjectWriter::writeObject(Object * obj,
>>> XojPopplerDocument doc)
>>>
>>> Object is an internal poppler class...
>>>
>>> The problem: Poppler don't support change PDFs, this is all written by me!
>>>
>>>
>>> Andreas
>>>
>>>
>>> Matt
>>>
>>>
>>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 23 Apr 2011 16:08:31 -0400
>> From: Matthew Chan<talc...@gmail.com>
>> Subject: Re: [Xournal-devel] xournal++ cairoOutputDev.h build error
>> To: Andreas Butti<andreasbu...@gmail.com>,     xournal-devel
>>         <xournal-devel@lists.sourceforge.net>
>> Message-ID:<banlktin8cxvu_xqwdm+8bzjqajwkp89...@mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On Sat, Apr 23, 2011 at 3:22 PM, Andreas Butti<andreasbu...@gmail.com>wrote:
>>
>>> May we can add all function which is needed to poppler, but then poppler is
>>> a PDF editing library and not only a PDF parser and renderer.
>>>
>>> But I thought we can ask the poppler team, what they think.
>>>
>>> What I do now:
>>>
>>> Take two poppler documents.
>>>
>>> Create a new PDF document, add pages from both poppler documents, and I'm
>>> able to take one page on top of the othet (Xournal contents on top of the
>>> background) then I add Author etc. information and bookmarks.
>>>
>>> If poppler support this we don't need it as library.
>>>
>> If poppler's goal is to act as a PDF parser/renderer, and not a PDF editor,
>> they might not want to expose the functionality you mentioned. Also, it
>> would probably take them a while to implement the changes that we suggested.
>>
>> Another option might be to use a dedicated PDF writing library. I'm not sure
>> how closely integrated poppler is to Xournal++ PDF printing (it seems pretty
>> tight), but PoDoFo may be an option. It's included in ubuntu, suse, fedora,
>> gentoo repos, and builds on Windows/OSX. It also has all(?) the
>> functionality you mentioned and is extremely well documented.
>>
>> > From the podofo project page:
>>
>> **snip**
>> *podofoimpose* - A powerful PDF imposition tool. It places pages from one or
>> more source PDFs onto pages of a new PDF, applying scaling and positioning.
>> *podofomerge* - Merges two PDF files into onw.
>> *podofopdfinfo* - Provides some basic info about a PDF - metadata, page
>> details, etc.**snip**
>>
>> We'd be more interested in the actual library, but if the tools can do it,
>> so can the library.
>>
>> I think this covers all the stuff you mentioned though, with exception of
>> bookmarks. I wasn't able to find any information on them directly, but
>> Podofo supports creating/editing PDF outlines. Is that the same thing?
>>
>> Would it be possible to use poppler as the PDF parser/renderer and then
>> podofo for the editing/writing?
>>
>>
>>>
>>> *BUT*
>>>
>>> For now I don't want to change everything, because all is working, and 
>>> *Ubuntu
>>> contains all necessary header files*.
>>>
>>>
>> I completely understand. It would be nice to get a stable implementation out
>> the door, even if it can't get included in other distros for now.
>>
>>
>>> Fresh installed Ubuntu 11.04. I had to install the poppler header package,
>>> but this package contains all necessary files.
>>>
>>> Andreas
>>>
>> On a completely separate note, do you have time to create the files you
>> mentioned for me to start working on the collaboration functions? I'd like
>> to start coding if possible. Also, if you could include an SVN branch with
>> that, I would greatly appreciate that.
>>
>> I've been using the head revision to annotate a PDF I've been reading. I'll
>> report back any bugs that I encounter.
>>
>> Thanks!
>> Matt
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Wed, 27 Apr 2011 15:47:19 -0400
>> From: Matthew Chan<talc...@gmail.com>
>> Subject: [Xournal-devel] developer consensus on XMPP library
>> To: xournal-devel<xournal-devel@lists.sourceforge.net>
>> Message-ID:<BANLkTikk3snehfqXkJAgwEujCfpRMKBe=a...@mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi all,
>>
>> I'm making good progress into implementing the collab features (the
>> messaging class is finished). I'd like to implement the XMPP backend, but I
>> need some community consensus first.
>>
>> I've put about a day and a half into using Gloox, but the documentation is
>> poor (examples out of date), and community support is worse. Also, it
>> appears the code has not been developed since 2009. It does appear stable
>> though.
>>
>> I've looked into other options, and one promising candidate seems to be the
>> Swiften library. It's multiplatform and actively developed. It's only been
>> public for a short while (May2010), but it was developed for awhile
>> privately and released when the author felt it was ready. The documentation
>> is pristine as well. It has ample implementation examples and also is
>> doxygen documented.
>>
>> The only (significant?) downside I am aware of with the Swiften library is
>> that it's not packaged in any distribution yet. If we were to depend on this
>> lib for collab features, someone would also need to package the Swiften
>> library in the repos of every distro we would want it to be included in.
>> This isn't a trivial effort, but the Swiften lib is definitely better
>> developed than a lot of other projects I have seen, which facilitates
>> packaging. Also, given the popularity of the xournal project, I'm sure that
>> someone would be willing to package the lib into the repos. This would
>> probably increase the amount of time it takes to have our code included in
>> the repos.
>>
>> Is everyone ok with this trade-off? I'm really at my limits with the gloox
>> library. I can't even get it to connect to a public XMPP server since it's
>> so poorly documented.
>>
>> Matt
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 27 Apr 2011 22:09:01 +0200
>> From: Andreas Butti<andreasbu...@gmail.com>
>> Subject: Re: [Xournal-devel] developer consensus on XMPP library
>> To: xournal-devel@lists.sourceforge.net
>> Message-ID:<4db877dd.8000...@gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Am 27.04.2011 21:47, schrieb Matthew Chan:
>>> Hi all,
>>>
>>> I'm making good progress into implementing the collab features (the
>>> messaging class is finished). I'd like to implement the XMPP backend,
>>> but I need some community consensus first.
>>>
>>> I've put about a day and a half into using Gloox, but the
>>> documentation is poor (examples out of date), and community support is
>>> worse. Also, it appears the code has not been developed since 2009. It
>>> does appear stable though.
>> Not document is for me not so a problem, Xournal++ is also nearly not
>> document;-) (To less time;-))
>>
>> But no active development and not stable is really bad, you shouldn't
>> use this library.
>>
>>> I've looked into other options, and one promising candidate seems to
>>> be the Swiften library. It's multiplatform and actively developed.
>>> It's only been public for a short while (May2010), but it was
>>> developed for awhile privately and released when the author felt it
>>> was ready. The documentation is pristine as well. It has ample
>>> implementation examples and also is doxygen documented.
>>>
>>> The only (significant?) downside I am aware of with the Swiften
>>> library is that it's not packaged in any distribution yet. If we were
>>> to depend on this lib for collab features, someone would also need to
>>> package the Swiften library in the repos of every distro we would want
>>> it to be included in. This isn't a trivial effort, but the Swiften lib
>>> is definitely better developed than a lot of other projects I have
>>> seen, which facilitates packaging. Also, given the popularity of the
>>> xournal project, I'm sure that someone would be willing to package the
>>> lib into the repos. This would probably increase the amount of time it
>>> takes to have our code included in the repos.
>> This should not be a problem I think.
>>
>> And I'm not sure if we publish Xournal++ and collaboration support at
>> the same time, we will see how fast your progress is, but there is a lot
>> of work to do, so may the first Xournal++ release don't contain
>> collaboration, so this are may two steps...
>>
>> (Ok, may Collaboration is ealier finished than Xournal++, this is the
>> other option, I planed to finish Xournal++ until February... No it's
>> April...;-))
>>
>>> Is everyone ok with this trade-off? I'm really at my limits with the
>>> gloox library. I can't even get it to connect to a public XMPP server
>>> since it's so poorly documented.
>> Try it out, often the fist impression is right, but if not throw it away
>> and start again;-)
>>
>>
>> I first thought I'll simple extend Xournal. I was working about a month
>> on this, then I found out this is the wrong solution, so I throw the
>> most of my work away I already did, and started new;-)
>>
>>
>> Andreas
>>
>>
>>> Matt
>>>
>>
>>
>>
>> ------------------------------
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>>
>> ------------------------------
>>
>> _______________________________________________
>> Xournal-devel mailing list
>> Xournal-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>>
>>
>> End of Xournal-devel Digest, Vol 17, Issue 12
>> *********************************************
>>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Xournal-devel mailing list
> Xournal-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xournal-devel

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Xournal-devel mailing list
Xournal-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xournal-devel

Reply via email to