Slashdot Mirror
Sun May Join Eclipse Project
ebresie writes "It seems with the possible movement by the Eclipse project towards a more independent entity, Sun may join the Eclipse Effort."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
If I remember correctly, #develop is the "official" Mono IDE, although you're right; /. did report some time back (with choice quotes from Miguel) that Eclipse has been successfully ported to Mono (or vice versa).
More than mere navel gazing.
There are plugins available right now that allow you to create forms via drag-n-drop. I don't know if any are open source. You can check out eclipse-plugins.2y.net/eclipse/plugins.jsp for more info.
I wouldn't be so sure about #develop being the official Mono IDE because it was only fairly recently that it became Mono-compatible (and I'm not even sure if it's already mono-compatible).
And about Eclipse being ported to mono, it's on the mono homepage, it was ported on May 10th, there's even a screenshot.
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.
Go hug some trees.
Eclipse is running inside 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.
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 it's also branding-enabled.
And if you think it's bloated - well it's modular - just deactivate the modules you don't need.
while (!asleep()) sheep++
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 =)
while (!asleep()) sheep++
I've yet to see any swing problems that are inherent to the technology. Swing looks and feels great on my machine. I use both eclipse and swing applications and I can't notice a difference in responsiveness, look & feel, etc. I have yet to see a single swt UI for which no swing equivalent can be made. Also eclipse is not noticably faster than e.g. JEdit. It could be that your judgement is affected by the lack of hardware acceleration of swing (or 2d graphics in general) under linux. Under windows and mac os x, this is not an issue.
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.
Jilles
I don't know, I've been doing some VB.NET work in VS.NET lately, and I am feeling exceedingly unproductive without features like built-in refactoring, smart renaming, smarter code completion, and similar things that exist in Eclipse (and IntelliJ).
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.