verdy_p

True, what is needed is the integration with development platforms for server-side applications. Good opensource environments exist for various languages, including Java, Javascript, CSS, HTML, C, C++, notably the excellent Eclipse.
During this develomement you may use some WYSIWIG editor to help generating a template page or create some fragments, or to modelize a general visual layout.
However, most of the time you'll work only on fragments of the pages.
A WYSIWIG ediotor however ''may'' be helpful for creating various static sections such as documentation pages, but even for them it is now simpler to use a dedicated software such as a wiki, or to templatize also the documentation (which can be also partly generated automatically from the application design.
For interactive pages, such as support forums (like this one) or blogs, there are also dedicated applications that you can deploy on a subdomain or in a HTTP subdirectory of your website. All those apps have convenient ways to customize the layout and integrate them them to the rest of your website.
You'll need a real development only for complex interactive pages that are linked to a background process, such as online catalogs and shops, or pages showing the state of a process or organizing some collaborative work and measuring the advancement. For bug tracking there are also convenient applications that are easy to deploy and you'll use your WYSIWIG editor only to create a template from which you'll extract some fragments to integrate in the layout of these apps.

The problem is not the copyrightability of the API but the fact that Google advertized programmers trying to convince them that the Google-made implementation was fully compatible with the JDK/JRE specs.

Google has created a compatibility nghtmare that costs a lot to application developers and defames the name of the Java platforms. We MUST say that the Android SDK is definitely NOT compatible with the Java JDK.

The abuse made by Google is in saying that the development would be the same. Google broke the contract offered in Java "Develop once, deploy anywhere".

As long as Google will not satisfy the compatibility test, or will reject bug reports related to its own implementation in the Adroid DSK, Google should not abuse the names and should instead use its own package names.

The Android platform is definitely not compatible. Applications have to be redeveloped and retested specifically for Android, the test on other mobile platforms certified (e.g. Nokia) are not enough.

Google lies to developers and to customers of devices running Android. It even created its own compatibility test, just as a commercial tactic to create another non-open marketplace for mobile applications.

So the copyright abuse is really in the abusive use of the Java reference name for too long. We know that Google lied to everyone (even to the court) and decided to abuse the name, just to refuse to open its own new proprietary platform.

Remember this : Android is definitely NOT open, much less than Java.

Google did not even want to get a licence in order to be able to integrate its specification in the Open platform to ensure the compatibility contract "develop once, deploy anywhere".

So Android applications now can no longer be deployed on Java platforms (mobiles, set tob boxes, TVs, media center appliances), and Java applications can no longer be deployed on Android devices. Google has created its own **closed** platform when insisting that it would be compatible with Java.

Do you really defend Google's closed platform here ? And the breach not really in terms of copyright but in trademarks and on Google's Android developer sites ?