Finn Bock wrote:
[Glen]
Does anyone have a problem if I worked towards
removing the initialize() method from our
LayoutManager interface?
There is two way of looking at it. The code in initProperties() which
can be moved to the ctor should be. That is no loss at all and will
reduce complexity
Finn Bock wrote:
But removing the initialize() method will reduce the flexibility that
LMs currently has to retrieve information from the parent LM. Perhaps
that flexibility is not used at the moment but I suspect that it will
be needed to implement the irregular inheritence of properties like
Team,
Does anyone have a problem if I worked towards
removing the initialize() method from our
LayoutManager interface? The relatively few cases in
our LM subclasses where we are using it each appear to
show that they can initialize themselves -- the method
is currently only being used to query
-Original Message-
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Hi Glen,
Does anyone have a problem if I worked towards
removing the initialize() method from our
LayoutManager interface?
No objections here at first glance, however ... (see below)
The relatively few cases in
our
On Wed, Nov 10, 2004 at 06:37:28AM -0800, Glen Mazza wrote:
Team,
Does anyone have a problem if I worked towards
removing the initialize() method from our
LayoutManager interface? The relatively few cases in
our LM subclasses where we are using it each appear to
show that they can
--- Simon Pepping [EMAIL PROTECTED] wrote:
I think it is a hook for doing those initialization
actions which for
some reason cannot be done in the constructor. I
have no idea which
actions that could be.
Even if a few such actions exist--I don't know any
yet--I'm thinking those can still
Oops, the link [1] below was the code that originally
added initialize() (as init()) into the interface.
[1]
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/org/apache/fop/layoutmgr/Attic/LayoutManager.java?r1=1.7r2=1.8diff_format=h
[Glen]
Does anyone have a problem if I worked towards
removing the initialize() method from our
LayoutManager interface?
There is two way of looking at it. The code in initProperties() which
can be moved to the ctor should be. That is no loss at all and will
reduce complexity of the LMs a tiny
