At 07:14 PM 6/29/01 -0500, Weiqi Gao wrote:
>On 29 Jun 2001 18:26:30 -0300, Arved Sandstrom wrote:
>> I'm open to suggestions from anyone as to a convenient label for the
>> redesign that Karen & I have described (and that others have also
contributed
>> to, I might add).
>
>Why not stick with t
On 29 Jun 2001 18:26:30 -0300, Arved Sandstrom wrote:
> At 06:40 AM 6/29/01 -0500, Weiqi Gao wrote:
> >On 29 Jun 2001 06:37:00 -0300, Arved Sandstrom wrote:
> >>
> >> FOP2 is the term for a completely new layout engine, and so maybe
> >> we don't really want to call the thing "FOP2". Suggestions?
At 06:40 AM 6/29/01 -0500, Weiqi Gao wrote:
>On 29 Jun 2001 06:37:00 -0300, Arved Sandstrom wrote:
>>
>> FOP2 is the term for a completely new layout engine, and so maybe
>> we don't really want to call the thing "FOP2". Suggestions? I'll
>> call it FOP1+ for now.
>
>Please spare us of the confus
On 29 Jun 2001 06:37:00 -0300, Arved Sandstrom wrote:
>
> FOP2 is the term for a completely new layout engine, and so maybe
> we don't really want to call the thing "FOP2". Suggestions? I'll
> call it FOP1+ for now.
Please spare us of the confusion and stick with simple numbers like 1 or
2.
--
At 08:52 AM 6/29/01 +0200, Jeremias Maerki wrote:
>Just an idea, but I don't have enough overview over FOP right now to know
>if it's feasible:
>Why not take a little time to encapsulate the parts to be redesigned, so
>the FOP 2 people can work on a separate repository (or just another
>package su
> Also if possible it might be good to create the branch for FOP II (2) after
> the next release so that there is a place to start working in.
> One question, how should we handle updates to FOP that are not specific to
> the new layout.
> For example: images, svg, logging, configuration etc.
> A
On Wed, 27 Jun 2001 12:32:24 Arved Sandstrom wrote:
> 2. We require a release plan for FOP 1. I propose a very simple one - a
> regular planned release the first week of every month, with a secondary
> bugfix release 1-2 weeks later (second or third week). That means that
> another will appear
Hi, all
Here are some assorted things.
1. Unless someone beat me to it, I'll go about getting a fop-users mailing
list set up. That appears to be the will of the majority (well, everyone
actually);
2. We require a release plan for FOP 1. I propose a very simple one - a
regular planned releas
