On Thu, 19 Jul 2001, Mark Lillywhite wrote:
> >Sure. Monday the 23rd evening (GMT) is codeformatting day unless somebody
> >protests.
> >
> Would it be possible to wait for a day or two before setting a firm
> date? I hope to have my pipelining stuff completed today and I would
> like to at lea
>
>
>Sure. Monday the 23rd evening (GMT) is codeformatting day unless somebody
>protests.
>
Would it be possible to wait for a day or two before setting a firm
date? I hope to have my pipelining stuff completed today and I would
like to at least get an opinion on their suitability for inclusion
On Tue, 17 Jul 2001, Arved Sandstrom wrote:
> Hi, Tore
>
> Well, how about _you_ set the day, since you're the volunteer? :-)
Sure. Monday the 23rd evening (GMT) is codeformatting day unless somebody
protests.
Everyone who have some uncomitted code should commit it by then as the
diffs in you
May I suggest to put up a code convention section in involved.xml? I
think a short notice with the most important rules (tabs to spaces, 4
spaces for tab etc.) will suffice. That will make it easier to encourage
people to follow the conventions.
Jeremias Märki
mailto:[EMAIL PROTECTED]
OUTLINE A
At 11:25 PM 7/17/01 +0200, Tore Engvig wrote:
[ SNIP ]
>I guess we have to use codeformatters (eg astyle) before we check in our
>code.
>
>I happend to grab a copy of jIndent while it still was free. jIndent does
>more than just codeformatting, it parses the code and is able to change a
>lot of th
On Tue, 17 Jul 2001, Arved Sandstrom wrote:
> We should, in theory, be able to use the cvswrappers mechanism (or module
> options) to run a style tool on a file when it is committed (or in a number
> of other cases). I can investigate this. I'd suggest that we divvy up the
> existing code, and
My apologies,
I said:
> Yes, I found -bug to have a significant impact on performace after
> about 100 pages. Before 100 pages there did
Of course, I meant "-buf"! Who put those two letters so close together anyway?
Cheers
Mark
At 08:29 AM 7/17/01 +0200, Keiron Liddle wrote:
>>From what I have seen so far we are never going to get a common code style.
>I usually format the code but that doesn't mean it will stay that way and
>there are a lot of files. eg. Arved committed in some of the Marker code
>with tabs to replace t
Hi,
On 16 Jul 2001 14:24:06 -0400, Art Welch wrote:
FWIW the PCL renderer should not be keeping much in memory.
It seems to keep the whole PDF document in RAM until it's closed. But I have worked out a sneaky way to pipeline the PDF without major changes, thanks mostly to the thinking
> FWIW the PCL renderer should not be keeping much in memory.
The same applies to the PostScript renderer and (I think) to the MIF
renderer, which was my starting point for the PostScript renderer.
Jeremias Märki
mailto:[EMAIL PROTECTED]
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luz
Mark,
I think the first step would be to change the PDF generation code so that
it can write out as it goes to a stream (and also do what it does now).
This would most likely be done by writing out each page after completion.
It may also (I'm not sure) require different tracking of objects such a
On Tue, 17 Jul 2001 01:22:38 Arved Sandstrom wrote:
> At 09:26 PM 7/16/01 +1000, Mark wrote:
> > As an aside: is there a style guide for FOP code? I must say I find the
> >style and layout very confusing and I'm happy to clean things up as I
> go.
> >At the moment I can't even work out what tab s
Arved Sandstrom wrote:
> At 09:26 PM 7/16/01 +1000, Mark wrote:
>
>>As an aside: is there a style guide for FOP code? I must say I find the
>>style and layout very confusing and I'm happy to clean things up as I go.
>>At the moment I can't even work out what tab stop size people are using.
>>(
At 09:26 PM 7/16/01 +1000, Mark wrote:
> As an aside: is there a style guide for FOP code? I must say I find the
>style and layout very confusing and I'm happy to clean things up as I go.
>At the moment I can't even work out what tab stop size people are using.
>(In my own work I use 8 character t
FWIW
the PCL renderer should not be keeping much in memory.
BTW
earlier you had mentioned that the buf option slowed things down. I would expect
that pipelining things would improve performance, has this been the case? If so,
how much?
It
seems to me that with the exception of a few det
Hi ho fops and fopettes,
I have had a look at the memory use of my modified-for-streaming FOP executable and determined that the primary memory constraint is now in the PDF renderer. Basically, because the PDF renderer keeps all objects in memory until the end, this obviously limits the size of
16 matches
Mail list logo
