I wonder. Isn't possible to create a smart factory (see SmartAPIPages) for
AWT components, AWT peers, and Swing components. Why do we want to use a
toolkit without a smart factory? The "toolkit" does not use separate
controllers for each component, so your stuck with a factory, not a smart
factory.
Imagine that the toolkit _uses_ a smart factory. The smart factory is
configured with controllers for _all_ of the AWT and Swing components on
your computer. Not just components that come with standard Java. I mean
_all_ of your components.
If we had a smart factory for components--all components--we would be able
to mix and match the peers behind AWT and Swing. I'm thinking that a smart
factory for components would use the JOS Registry API (see RegistryAPI) to
configure the list of component controllers.
This extends the idea of look and feel, I think. When you combine a
powerful smart factory to the GUI, you can get a button without knowing the
name of a specific button class. A smart factory should be able to create a
button with a caption, an image, a caption and image, in both AWT _and_
Swing. A smart factory should be able to creaet a sticky button in both AWT
_and_ Swing.
What else? A smart factory can support Java 1.0, 1.1 and 2.0 (1.2) and the
next version of Java, too. We can look forward to being the first operating
system to support Java 3.
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
