The original design goal of the graphical user interface (GUI) library in Java l.o was to allow the programmer to build a GUI that looks good on all platforms.
让程序员建立一个在所有平台上看起来都不错的GUI是在java1.0时GUI库设计的初衷。
That goal was not achieved.
这个目标没有达成。
Instead, the Java l.o Abstract Windowing Toolkit (AWT) produced a GUI that looked equally mediocre on all systems.
相反,awt生产出一个在所有平台上看起来都很平庸的GUI。
In addition, it was restrictive;
并且,它是限制的。
you could use only four fonts and you couldn’t access any of the more sophisticated GUI elements that exist in your operating system.
只能用4种字体,不可以用任何系统支持的复杂GUI控件。
The Java 1.0 AWT programming model was also awkward and non-object-oriented.
awt开发模型是非对象且笨拙的。
A student in one of my seminars (who had been at Sun during the creation of Java) explained why:
我的研究院里的一个学生(参于java研制)解释说:
The original AWT had been conceived, designed, and implemented in a month.
awt是一个月内完成的。
Certainly a marvel of productivity, and also an object lesson in why design is important.
这是一个生立力的奇迹,并且也是一个说明“为什么设计是很重要的”的一个实例。
让程序员建立一个在所有平台上看起来都不错的GUI是在java1.0时GUI库设计的初衷。
That goal was not achieved.
这个目标没有达成。
Instead, the Java l.o Abstract Windowing Toolkit (AWT) produced a GUI that looked equally mediocre on all systems.
相反,awt生产出一个在所有平台上看起来都很平庸的GUI。
In addition, it was restrictive;
并且,它是限制的。
you could use only four fonts and you couldn’t access any of the more sophisticated GUI elements that exist in your operating system.
只能用4种字体,不可以用任何系统支持的复杂GUI控件。
The Java 1.0 AWT programming model was also awkward and non-object-oriented.
awt开发模型是非对象且笨拙的。
A student in one of my seminars (who had been at Sun during the creation of Java) explained why:
我的研究院里的一个学生(参于java研制)解释说:
The original AWT had been conceived, designed, and implemented in a month.
awt是一个月内完成的。
Certainly a marvel of productivity, and also an object lesson in why design is important.
这是一个生立力的奇迹,并且也是一个说明“为什么设计是很重要的”的一个实例。