We can do it this way.  But on second thought, I think
it would be better for Renaud to move it in as
AWTRenderer, and slowly start factoring out more and
more while things are getting settled.  BTW, this will
take some time to do anyway--it isn't easy because the
renderers are so different between 0.20.5 and 1.0.

[A note for Renaud:  I would recommend cutting down on
the chatroom English and instead start writing
properly/respectfully to us, in the same manner that
all of us have been writing to you.  Capitalize "I",
the first word of each sentence, your name, our
names[1], greetings, etc.  Above all, when people
write to you in standard polite English, you shouldn't
be responding back with chatroom writing.  None of us
here do.  Thanks!]

Glen

[1]
http://marc.theaimsgroup.com/?l=fop-dev&m=110625230922690&w=2


--- Jeremias Maerki <[EMAIL PROTECTED]> wrote:

> Given the new layout I don't even need to prepare
> anything. It would
> only complicate things. Just rename the AWTRenderer
> to Java2DRenderer,
> move it to the new location, then create an empty
> subclass of
> Java2DRenderer called AWTRenderer and move any
> AWT-dependant code to
> that subclass.
> 
> On 22.02.2005 22:43:01 Renaud Richardet wrote:
> > Glen Mazza <[EMAIL PROTECTED]> wrote:
> > > Looks good!  Now whether you wish to do this
> before or
> > > after Renaud moves the logic over is up to you
> two.
> > > There's advantages/disadvantages to either
> method.
> > yes, that looks good! 
> > 
> > Jeremias, if it's ok for the team, i would
> apreciate if you would do
> > the changes asap.
> > 
> > thanks, Renaud
> 
> 
> 
> Jeremias Maerki
> 
> 

Reply via email to