|
|
|
| Authored by: Wol on Sunday, May 20 2012 @ 04:29 PM EDT |
As has been widely pointed out, you have just used a Java api...
public static void main(String[] args) {
Please note, aiui, if you don't do that your program won't even compile ...
Cheers,
Wol[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Sunday, May 20 2012 @ 06:29 PM EDT |
If you wrote your own API completely then all you end up with is a new language
that is in now way Java but happens to share the same syntax. Your not then
programing in Java and if you say you are Oracle will probably try to Sue you ;)
(this last bit is a trademark joke by the way)
Michael[ Reply to This | Parent | # ]
|
| |
| Authored by: Anonymous on Sunday, May 20 2012 @ 07:52 PM EDT |
Java has several APIs to do so: e.g.
Swing (in Java SE), AWT (in SE
as well), SWT (an API by
IBM), lcdui (in Java ME), LWUIT (an independent API for
Java
ME) or an API different from all of the above used by
Android! Why does
Google think that you must copy the
specific API for console output
(System.ou.println) but not
the API for displaying a
button?
Why did Sun think that it needed several different UI's
?
For example the LWUIT:
Writing appealing cross platform mobile
applications is challenging. Due to implementation differences in fonts, layout,
menus, etc. the same application may look and behave very differently on
different devices. In addition much of the advanced UI functionality is not
accessible in LCDUI and requires the developer to write very low level "paint"
type code. The Lightweight UI Toolkit was developed to address these
issues
Lwuit is a subproject of Mobileandembedded,
was started in January 2011 ...
So Oracle decided that existing
UIs were unsuitable for mobile devices a few years after Google had already
decided that. Why didn't Oracle use the UI that Android already had ?
[ Reply to This | Parent | # ]
|
|
|
|
|
