Re: [Xournal-devel] on poppler dependencies

2011-05-08 Thread Matthew Chan
Hi Ryan, I'm not familiar with all the autotools magic you need to get it working, but I needed to modify the source files with the unresolved header dependencies to point to a local copy of CairoOutputDev.h Andreas and I have already discussed using PoDoFo as a replacement library for the curren

Re: [Xournal-devel] developer consensus on XMPP library

2011-04-27 Thread Matthew Chan
The documentation wasn't really great. It exists, but it's kind of patchwork, and not up to date as far as I could tell. Matt On Wed, Apr 27, 2011 at 5:57 PM, Bob McElrath wrote: > Why not libpurple? > > http://developer.pidgin.im/wiki/WhatIsLibpurple > > Matthew Chan

[Xournal-devel] developer consensus on XMPP library

2011-04-27 Thread 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

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-23 Thread Matthew Chan
On Sat, Apr 23, 2011 at 3:22 PM, Andreas Butti 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 popp

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-23 Thread Matthew Chan
On Sat, Apr 23, 2011 at 4:54 AM, Andreas Butti 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 interna

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-22 Thread Matthew Chan
lade-2.0 >= 2.6.4 gthread-2.0 >= 2.4.0" PKG_CHECK_MODULES(PACKAGE, [$pkg_modules]) +AC_CHECK_LIB([z], [gzopen]) AC_SUBST(PACKAGE_CFLAGS) AC_SUBST(PACKAGE_LIBS) On Fri, Apr 22, 2011 at 9:37 PM, Matthew Chan wrote: > Hi Andreas, > > Last email of

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-22 Thread Matthew Chan
f 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? Matt On Fri, Apr 22, 2011 at 8:53 PM, Matthew Chan wrote: > Hi Andreas, > > I talked to the f

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-22 Thread Matthew Chan
description of what it does please? Also, what is the difference between outputDev.h which is shipped in the poppler project and the cairoOutputDev.h header? Thanks, Matt On Fri, Apr 22, 2011 at 2:32 PM, Andreas Butti wrote: > > > Am 22.04.2011 20:28, schrieb Matthew Chan: > > Hi Andr

Re: [Xournal-devel] On collaboration in Xournal

2011-04-22 Thread Matthew Chan
hat. At the moment, I can't even compile Xournal++ on my > laptop, > so getting past this hurdle will be my first priority. > > Thanks, > > --- Alex. > > On Wed, Apr 20, 2011 at 02:48:28PM -0400, Matthew Chan wrote: > > Hi everyone, > > > > This sou

[Xournal-devel] Fwd: xournal++ cairoOutputDev.h build error

2011-04-22 Thread Matthew Chan
**forwarding to list** -- Forwarded message -- From: Matthew Chan Date: Fri, Apr 22, 2011 at 2:28 PM Subject: Re: xournal++ cairoOutputDev.h build error To: Andreas Butti Hi Andreas, I've managed to build in eclipse now. There was a weird eclipse bug causing build errors

Re: [Xournal-devel] xournal++ cairoOutputDev.h build error

2011-04-21 Thread Matthew Chan
at. It was extremely responsive, and I managed to load a PDF into it and annotate it successfully. Keep up the great work! Matt On Thu, Apr 21, 2011 at 10:33 PM, Matthew Chan wrote: > Hi Andreas, > > I manage to work around the autotools errors, but I'm getting a > cairoOutputDe

Re: [Xournal-devel] On collaboration in Xournal

2011-04-20 Thread Matthew Chan
Hi everyone, This sounds like a great idea. We could even implement a ownership transfer of layers. For example, if I wanted to edit a stroke on my collaborator's layer, I could select one of his strokes and we could both agree to temporarily transfer ownership of the layer to me so I could recolo