>Can you post a version online that doesn't contain so many pages?
>The object layer chapter alone contains over 20 pages, which makes
>it very annoying to read -- a single downloadable file would be
>nice.
>
> I though that the info format is quite convenient. Y
On Wed, Feb 18, 2009 at 07:18:01 -0800, ge...@gnu.org wrote:
> > Date: Wed, 18 Feb 2009 01:38:57 -0500
> > From: Michael Gold
> >
> > So the object layer needs to know the file type anyway (not just the
> > header string); and given this, it can choose an appropriate header when
> > saving,
> Date: Wed, 18 Feb 2009 01:38:57 -0500
> From: Michael Gold
>
>
> > > For the standard headers, the client could check using the
> > > pdf_obj_doc_get_header you proposed, but that still seems like a
> > > low-level detail they shouldn't have to deal with.
> > >=20
> > > We could
On Tue, Feb 17, 2009 at 19:56:40 -0800, ge...@gnu.org wrote:
> > Date: Tue, 17 Feb 2009 16:32:39 -0500
> > From: Michael Gold
> >
> >
> > > - What's the point of header_string?
> > >- The client probably doesn't care about the header -- they just
> > > want the librar
> Date: Tue, 17 Feb 2009 16:32:39 -0500
> From: Michael Gold
>
>
> > - What's the point of header_string?
> >- The client probably doesn't care about the header -- they just
> > want the library to open a valid PDF.
> >=20
> > The user may want to open non-pdf file
On Tue, Feb 17, 2009 at 00:43:48 +0100, jema...@gnu.org wrote:
>Can you post a version online that doesn't contain so many pages?
>The object layer chapter alone contains over 20 pages, which makes
>it very annoying to read -- a single downloadable file would be
>nice.
>
> I though
Hey Michael.
Many thanks for your comments! Quite useful.
Here I address most of the questions: I should think about the rest of
them.
> I just committed in the trunk the first draft of the object layer
> public API. It is documented in the "Object Layer" chapter of the
> reference man
On Fri, Feb 06, 2009 at 00:49:36 +0100, jema...@gnu.org wrote:
>
> Hi.
>
> I just committed in the trunk the first draft of the object layer
> public API. It is documented in the "Object Layer" chapter of the
> reference manual.
Can you post a version online that doesn't contain so many pages?
T
Leonard Rosenthol wrote:
> You want a garbage collection model for PDF object handling - it's how it is
> done by EVERY SINGLE PDF library out there...
>
> Objects belong to a document - they can't be shared across documents. They
> need to be "rooted" to the document in question. Some librari
l-bounces+lrosenth=adobe@gnu.org] On Behalf Of Juan Pedro
Bolivar Puente
Sent: Tuesday, February 10, 2009 10:11 PM
To: jema...@gnu.org
Cc: pdf-devel@gnu.org
Subject: Re: [pdf-devel] Object layer API
> When we save an object document (using pdf_obj_doc_save) a garbage
> collector is inv
> When we save an object document (using pdf_obj_doc_save) a garbage
> collector is invoked on the objects of the saved document. The garbage
> collector implements a sweep-mark process that, using the document
> root dictionary as the root, marks any reachable object. Then, in the
> sweep phase,
Hi Gerel.
> Please take a look and send your comments to discuss: it is capital to
> come with a useful and complete API for the object layer.
Of course, some comments follow.
Thanks :)
> Note that:
>
> [...]
>
> 3) It is not clear to me where to put the pdf cre
> Date: Fri, 06 Feb 2009 00:49:36 +0100
> From: jema...@gnu.org
>
> Please take a look and send your comments to discuss: it is capital to
> come with a useful and complete API for the object layer.
Of course, some comments follow.
> Note that:
>
> [...]
>
> 3) It is not clear to me
Hi.
I just committed in the trunk the first draft of the object layer
public API. It is documented in the "Object Layer" chapter of the
reference manual.
Briefly, the API is built around two main concepts:
- Object Documents.
Hierarchy of objects that may compound a PDF document (not every
14 matches
Mail list logo
