Swing Packages

javax.swing.*

• All the new Swing components and classes need a home. Where?

• A subject of great debate!

• For JDK 1.1, Sun used “com.sun.java.swing”

• Problem: developers complained this was not appropriate for “core” class

Solution:

Denotes ‘extension’ package that

has migrated to core status

Why “javax”?

* logical grouping

* minimizes transition

costs

* most developers

happy with it

* helps maintain

existing JDK 1.1 code

(cf. MFC lib breaks)

Previous slide

Next slide

Back to first slide

View graphic version