Content deleted Content added
Hervegirod (talk | contribs) |
|||
Line 408:
:::::::: AWT is not "hard wired" into the language. And you can easily use Java without it altogether (for example, Java on mobile devices - same language, different runtime library). [[User:Spockwithabeard|Spockwithabeard]] ([[User talk:Spockwithabeard|talk]]) 19:18, 13 February 2011 (UTC)
::::::::: J2ME Personal Profile contains AWT packages too. [[User:Hervegirod|Hervegirod]] ([[User talk:Hervegirod|talk]]) 22:49, 13 February 2011 (UTC)
:::::::::: Java ME MID Profile does not. There is no feature of the Java language or VM (as specified) to support AWT, so it cannot be said to be "hard wired" into the language. The fact that you can't build a GUI without runtime-library support is irrelevant. The Java ''langauge'' contains no support for building a GUI. Many Java apps (as stated earlier) have no GUI, such as server and embedded apps. [[User:Spockwithabeard|Spockwithabeard]] ([[User talk:Spockwithabeard|talk]]) 12:46, 19 February 2011 (UTC)
:::Java does not have events as a first class feature, and not as a language feature. Period. If you consider java.util then yes, there is a conventional way to ''implement'' events. However, AWT has no place in this article. AWT is a framework built ''using'' the language, in no way can it be presented as part of the language or even the core library. Events are defined in java.util and if this article should allow "core" libraries then Java+core library can be said to feature events. [[User:Useerup|Useerup]] ([[User talk:Useerup|talk]]) 15:22, 6 December 2010 (UTC)
| |||