glynn at sensei.co.uk
Fri Oct 2 11:02:33 PDT 1998
Peter C. Mehlitz wrote:
> To make Toolkit abstract would be just a matter of minutes, but - since it
> doesn't have a public constructor - I don't see any reason why we should add
> another class, just to end up with the same behavior (a good way to bloat the
Ah, well, the point is that the existing mechanism doesn't quite give
you the specified behaviour (at least not according to the versions of
the spec. which I've seen; I don't know if this is changed in 1.2).
Gets the toolkit of this component. Note that the frame that contains
a component controls which toolkit is used by that component.
Therefore if the component is moved from one frame to another,
the toolkit it uses may change.
IOW, a Java application can force the use of a particular toolkit by
creating a subclass of java.awt.Window, which overrides the
getToolkit() method. But a Kaffe application can't.
Glynn Clements <glynn at sensei.co.uk>
More information about the kaffe