Re: [Java-gnome-developer] Java-Gnome is cool but it's a Bad Thing.

[Joe P. <joe...@in...>]

I personally use Java for the following reasons (in no particular
order):

1- easy to use language
2- OO base
3- depth of class libraries
4- portability (I use UNIX/Linux, my clients can use whatever they want)
5- good error-handling via exceptions

Portability is important to me and my company.  We like the fact that we
can develop good systems using Linux and Solaris and still deploy to MS
Windows clients if they so desire.

The current state of the java-gnome bindings are not very useful to me
but I continue to watch development and consider pitching in due to the
potential.

I know that the java-gnome bindings are not being developed with the
intention of extending AWT but there is no denying that they could be
used to do so down the road.  If it is not done by the original
developers, it can be done by someone else.  I think this would be a
nice thing to see.

I'm a Java developer AND a GNOME user.  I'd like to be able to write a
GNOME panel applet using Java.  The Java-GNOME bindings will allow me to
do so.

While I'd really like to see a GNOME-enabled AWT with GTK look-and-feel
support, there is no reason it can't be built upon the work done by the
Java-GNOME team.

-joe

On 05 Sep 2001 13:00:52 -0400, Ed Symanzik wrote:
> The screenshots are cool but here's why this is a Bad Thing:
> 
> - I write Java so my applications will be portable.  Gnome is
>   not portable.
> 
> - Microsoft did the same thing, tying Java to Windows calls, 
>   and they got their hand slapped.  It was bad then and it's
>   bad now.
> 
> Perhaps I don't understand but it seems to me this should be
> done as UIManager.setLookAndFeel("org.gnome.GnomeLookAndFeel")
> or perhaps by rewriting awk/swing to use gnome.