Peter, >>Composable2, ComponentManager2 ? >> > >ewww - runaway, runaway ;) > I knew we we going round in circles dude.... You're the one pushing for 'Component becomes Object' (by implication) then backing away ;-)
I don't like Stephens new ServiceXXXX stuff. I mean it is good. No it is perfect but for the absense of the word "Component". We are not without precident, all these from JDK1.4 : LayoutManager2 GlyphPainter2 Parser2 (Crimson) ElementNode2 NamespaceSupport2 <fx> ducks from Peter's bullets </fx> Packages Evolve. Lets understand that. We have no versioning built into Java in the sense that two versions of the same API could interoperate in the same classloader/classpath. In ten years time we will have loads of dead packages (java.io is example) or loads of suffixed classes/interfaces. We could migrate all functionality immediately to the "2" versions and for the original versions have a hand crafted proxy that routes all calls through to the new one. It is one strategy that will be taken with AWT in the end I guess. Sun/Netacape built Swing on top of the AWT primatives, but kept AWTs own heavyweight comps. Sun could obsolete AWT and or have a near enough pure Java "AWT2" that AWT routes through to. In fact AWT could route through to Swing, more or less completely hiding the experience. In that version of the graphic toolkit all Swing would need from the iunderlying OS would be mouse, kbd and "rectangle reservation" graphics support. Swing could sit small OSs that have no advanced graphics API. Sigh... Java's original Component model ;-) - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
