On Thu, 2006-05-11 at 14:35 -0400, Jody Goldberg wrote:
> On Wed, May 10, 2006 at 04:51:48PM -0500, Federico Mena Quintero wrote:
> > On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
> > > I'm implementing the preview code in gtkprint. I have decided to use an
> > > external helper (de
On Wed, May 10, 2006 at 04:51:48PM -0500, Federico Mena Quintero wrote:
> On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
> > I'm implementing the preview code in gtkprint. I have decided to use an
> > external helper (default is evince) to do print preview. The idea was
> > to write
John (J5) Palmieri wrote:
On Thu, 2006-05-11 at 11:48 -0500, Yevgen Muntyan wrote:
Alexander Larsson wrote:
I think the best way to do this is to rely on an external helper. For a
couple of reasons:
* Running something as complicated as a document viewer in the same
process as the app
On Thu, 2006-05-11 at 12:29 -0500, Travis Watkins wrote:
> On 5/11/06, Alexander Larsson <[EMAIL PROTECTED]> wrote:
> > On unix we could use evince (or another pdf viewer of your choice), on
> > OSX we could use preview.app, and on Windows we could generate a .emf
> > file (easy with cairo) and use
On Thu, 2006-05-11 at 11:48 -0500, Yevgen Muntyan wrote:
> Alexander Larsson wrote:
>
> >I think the best way to do this is to rely on an external helper. For a
> >couple of reasons:
> >* Running something as complicated as a document viewer in the same
> >process as the application scares me for
On Thu, 2006-05-11 at 12:29 -0500, Travis Watkins wrote:
> On 5/11/06, Alexander Larsson <[EMAIL PROTECTED]> wrote:
> > On unix we could use evince (or another pdf viewer of your choice), on
> > OSX we could use preview.app, and on Windows we could generate a .emf
> > file (easy with cairo) and use
On 5/11/06, Alexander Larsson <[EMAIL PROTECTED]> wrote:
On unix we could use evince (or another pdf viewer of your choice), on
OSX we could use preview.app, and on Windows we could generate a .emf
file (easy with cairo) and use the emf viewer that ships with windows.
So what happens if you try
Alexander Larsson wrote:
I think the best way to do this is to rely on an external helper. For a
couple of reasons:
* Running something as complicated as a document viewer in the same
process as the application scares me for stability reasons. Its easy for
a bug in the viewer to bring the whole
On Wed, 2006-05-10 at 16:51 -0500, Federico Mena Quintero wrote:
> On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
> > I'm implementing the preview code in gtkprint. I have decided to use an
> > external helper (default is evince) to do print preview. The idea was
> > to write out to
On Wed, 10 May 2006, John (J5) Palmieri wrote:
> I'm implementing the preview code in gtkprint. I have decided to use an
> external helper (default is evince) to do print preview. The idea was
> to write out to a pdf in /tmp and launch the external helper when the
> user hits the preview button.
On Wed, 2006-05-10 at 19:37 -0400, Dominic Lachowicz wrote:
> > This was my original thought but Matthias and others suggested this.
> > One of the issues with cairo is that we would have to either run through
> > the drawing commands on every expose event or save out to a bitmaps
> > surface which
This was my original thought but Matthias and others suggested this.
One of the issues with cairo is that we would have to either run through
the drawing commands on every expose event or save out to a bitmaps
surface which would remove the ability to zoom. The other option is to
recreate evince
On Wed, 2006-05-10 at 17:52 -0500, Federico Mena Quintero wrote:
> On Wed, 2006-05-10 at 18:26 -0400, John (J5) Palmieri wrote:
> > One of the issues with cairo is that we would have to either run through
> > the drawing commands on every expose event or save out to a bitmaps
> > surface which woul
On Wed, 2006-05-10 at 18:56 -0400, John Ehresman wrote:
> John (J5) Palmieri wrote:
> > This was my original thought but Matthias and others suggested this.
> > One of the issues with cairo is that we would have to either run through
> > the drawing commands on every expose event or save out to a b
John (J5) Palmieri wrote:
This was my original thought but Matthias and others suggested this.
One of the issues with cairo is that we would have to either run through
the drawing commands on every expose event or save out to a bitmaps
surface which would remove the ability to zoom. The other op
On Wed, 2006-05-10 at 18:26 -0400, John (J5) Palmieri wrote:
> One of the issues with cairo is that we would have to either run through
> the drawing commands on every expose event or save out to a bitmaps
> surface which would remove the ability to zoom.
The canvas runs through the drawing comman
On Wed, 2006-05-10 at 16:51 -0500, Federico Mena Quintero wrote:
> On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
> > I'm implementing the preview code in gtkprint. I have decided to use an
> > external helper (default is evince) to do print preview. The idea was
> > to write out to
On Wed, 2006-05-10 at 17:42 -0400, John (J5) Palmieri wrote:
> I'm implementing the preview code in gtkprint. I have decided to use an
> external helper (default is evince) to do print preview. The idea was
> to write out to a pdf in /tmp and launch the external helper when the
> user hits the pr
I'm implementing the preview code in gtkprint. I have decided to use an
external helper (default is evince) to do print preview. The idea was
to write out to a pdf in /tmp and launch the external helper when the
user hits the preview button. The print dialog would stick around even
after the pre
19 matches
Mail list logo
