Sun May Join Eclipse Project 44
ebresie writes "It seems with the possible movement by the Eclipse project towards a more independent entity, Sun may join the Eclipse Effort."
You mean you didn't *know* she was off making lots of little phone companies?
Very good news for Eclipse (Score:5, Interesting)
Perhaps this means Eclipse will get a GUI builder soon?
Re:Very good news for Eclipse (Score:3, Informative)
Re:Very good news for Eclipse (Score:3, Informative)
And about Eclipse being ported to mono, it's on the mono homepage [go-mono.com], it was ported on May 10th, there's even a screenshot [go-mono.com].
I'm not aware of the details, but they probably ported the whole SWT to Mono using their java compiler and then they could build the whole thing.
Re:Very good news for Eclipse (Score:3, Informative)
Eclipse is running inside IKVM.NET [ikvm.net], a JVM for .NET/Mono. The idea of IKVM is to allow Java bytecodes to run inside a .NET VM. It's pretty cool, check out the FAQ [ikvm.net].
Re:Very good news for Eclipse (Score:4, Interesting)
IKVM also helps bridge the two worlds: Java and CIL. Your Java code can then be loaded and used by CIL applications (C#, VB, etc) all running together.
personally i don't rate Eclipse much as a development environment compared to Visual Studio.NET. But i am a big fan of the Standard Widget Toolkit (SWT)
Re:Very good news for Eclipse (Score:2, Informative)
VS.NET may be the Holy Grail for GUI development, but for just plain old writing code, Eclipse is light-years ahead. I mean, VS.NET doesn't even add your import statements, and it won't code complete something if it's not in an import statement.
Re:Very good news for Eclipse (Score:2, Interesting)
Re:Very good news for Eclipse (Score:1)
Sun already integral part of eclipse (Score:5, Funny)
The aim of the Eclipse project (Score:2, Funny)
Re:The aim of the Eclipse project (Score:2, Funny)
All that you touch. All that you see
All that you taste. All you feel
All that you love. All that you hate
All you distruct. All you save
All that you give. All that you deal
All that you buy. Beg, borrow or steal
All you create. All you destroy
All that you do. All that you say
All that you eat. Everyone you meet
All that you slight. Everyone you fight
All that is now. All that is gone
All that's to come. And everything
Re:Sun already integral part of eclipse (Score:2)
GUI Builder (Score:3, Informative)
Re:GUI Builder (Score:2, Interesting)
Swing RIP (Score:4, Interesting)
Soon it will be down to VisualStudio.NET, Eclipse and Emacs for developing things. Borland's only man left on the island marriage with BEA ain't gonna save it.
JBuilder.. (Score:1, Flamebait)
Anyway, JBuilder rocks. It rolls. It totally owns. Everything else in the Java world sucks by comparison.
Is that clear enough for you?
Oh, and I wouldn't consider
Re:Swing RIP (Score:5, Informative)
Admittedly it took until version 1.4.2 of the jdk for swing to catch up. I'd say swt is close to irrelevant in eclipse since it does not even include a GUI builder. Eclipse is mostly used for server side development. I think most eclipse users couldn't care less what particular toolkit is used. They just need a responsive UI and swt/eclipse happens to offer it for them.
So far the only major application to use SWT that I am aware of (no doubt there are some prototypes somewhere) is eclipse itself. I am aware of a substantial amount of mature swing apps. So to call swing a failure because swt supposedly blows swing out of the water based on a sample of one (1) application seems a bit premature. IMHO IBM wasted time and resources by developing swt. I'm sure it's a decent toolkit but I can't seem to find out what problem with swing it is trying to address or what the added value of swt is for serverside development.
Re:Swing RIP (Score:2, Interesting)
How sluggishness Swing IDEs are is the reason I switched to developing Java with Emacs... that was until I tried Eclipse. Why should I keep convincing people to spend tens of
Re:Swing RIP (Score:2)
IBM may have had the vision, but the result does not exactly speak for itself. I like the eclipse GUI (well designed) but to say it is significantly better in any way than a swing gui goes to far for me. Of course there are many poorly written swing applications (one of the reasons for this is that swing is actually easy to use once you get th
Re:Swing RIP (Score:2)
JBuilder uses Borlands own widget library.
angel'o'sphere
Re:Swing RIP (Score:1)
Oh, and SWT is open source whereas swing isn't.
Re:Swing RIP (Score:1)
Re:Swing RIP (Score:1)
The market with Java is moving away from tools and twords servers in the mid term and services (people) in the long term. Of all the companies trying to make $$$ off of Java, IBM's is the soundest.
Re:Swing RIP (Score:2)
The key to Eclipse eclipsing other tools is it being built with the Standard Widget Toolkit. Swing is a failure like the AWT before it. Any IDE that is built with Swing will be blown out of the water by Eclipse.
Modded as interesting but wrong.
Swing is a very well designed GUI class library, I would go so far to say its a frame work.
As soon as you app is running for a while the SWING gui is native jit compiled. Just like SWT.
There are a lot of nice Swing gui apps out there, which are pretty fast. And furt
what about netbeans (Score:1, Interesting)
Re:what about netbeans (Score:3, Interesting)
Re:what about netbeans (Score:3, Informative)
Have you even looked at Netbeans in the last releases? Especially Netbeans 3.5 with J2SDK1.4.2 got much faster.
And I totally fail to see why Netbeans should be inflexible. It's one the most flexible applications I ever had the joy to work with.
It's not only highly modular
Re:what about netbeans (Score:2)
Re:what about netbeans (Score:1)
I never said Netbeans is fast. It just changed from painfully slow to slightly slow =).
I use Netbeans on a daily basis at my job. We evaluated Eclipse when we abandoned Visual J++. My Impression was that the UI is faster, of course, but the rest of the code seemed just as slow and even more memory-hungry. It lacked some features we needed and so we chose Netbeans which got them all (after adding RefactorIt [refactorit.com]).
Over the time we extended Netbeans with our own modules, which play a great role in our daily work
Sun Needs an IDE (Score:4, Insightful)
Meanwhile, IBM has quietly pushed Eclipse. I keep getting the impression that IBM understands both the two relevent cultures (Java developers and open-source people) a lot better than Sun.
Sun's IDE (Parent not insightfull) (Score:4, Informative)
NetBeans started as a student project in the Czech Republic (originally called Xelfi), in 1996. The goal was to write a Delphi-like Java IDE in Java. A company was formed around this project, called NetBeans. There were two commercial versions of NetBeans, called Developer 2.0 and 2.1. Around May of 1999, NetBeans released a beta of what was to be Developer 3.0 - some months later, in October '99, NetBeans was acquired by Sun Microsystems. After some additional development time, Sun released the Forte for Java Community Edition IDE - the same IDE that had been in beta as NetBeans Developer 3.0.
There had always been interest in going Open Source at NetBeans. In June 2000, Sun open-sourced the NetBeans IDE [...]
(from http://www.netbeans.org/about/history.html)
Yeah.. Forte didn't work out. It fell in the hands of evil open source communists =)
Political reason not to ... (Score:2)
Re:Political reason not to ... (Score:4, Insightful)
Daniel
SWT in JFC (Score:3, Insightful)
Re:SWT in JFC (Score:2, Interesting)
Re:SWT in JFC (Score:2)
No way. SWT is not just this cool, fast piece of code. It's a collection of native bindings. You download a platform specific SWT package in order to run your SWT based code.
Sun has been fussing about IBM resorting to this non-cross-platform strategy, if you see a properly implemented Swing GUI (eg. IntelliJ), you'll realize that SWT is not really that much snappier.
IDE? Who needs an IDE? (Score:1)
SWT vs Swing vs AWT and Sun (Score:2, Interesting)
Then came Swing, which was more abstract, higher level, and less hardware specific, with more functionality in some areas and less in others.
Then came SWT, which came about to increase speed by moving closer to the lower level APIs, to avoid lots of bloat, to be closer to host OS look and feel, and once again more hardware/OS specific and this was good..
There are always differences [developer.com], and more differences [blog-city.com]
---
Sun doesn't plan on a
Swing, NetBeans and the anti-hype (Score:2, Interesting)
My personal experience in the building of a huge client, Swing based applications suite for near-real-time railway traffic monitoring, control, planning and simulation, currently being deployed the Spain's second high speed railway (Madrid-Lleida, and Barcelona a