Slashdot Mirror


NetBeans 4.0 Release

An anonymous reader writes "Various news sources are reporting the 4.0 release of the free Java-based NetBeans IDE. You can read the anouncement, or proceed directly to the downloads. Perhaps the most significant improvement is that the IDE's native build system is the latest version of Apache Ant. I see this as a distinct advantage over its competitor Eclipse (and NetBeans is pure Java). If you create desktop applications in Java, you may wish to read up on the NetBeans 'platform' as well. Enjoy."

45 comments

  1. The horror, the horror by Pacifix · · Score: 2, Interesting

    We're required to use NetBeans at school. I end up coding all my stuff in IntelliJ and copying and pasting. NetBeans is much too controlling in terms of all the code it generates for the UI and has always seemed very counterintuitive to me.

    1. Re:The horror, the horror by flumps · · Score: 2, Interesting

      Actually, netbeans tends to do things the way they are supposed to be done, not the way you think they should be.

      Which is what an IDE should do, especially when you are dealing with large projects and need some fomalisation built in to the structure of the project.

      IntelliJ may allow you to fudge things a little, but in 6 months time when the project ends would you rather have controlled steady development or a bundle of spaghetti code to deal with and debug?

      For example, I love the way you can build a bean add it to the component panel, drag it into your app and adjust the properties on the form in the UI's properties window. It deals with the coding quite smoothly and efficiently and even allows connections to other components on the page in the correct coding methodologies.

      My only gripe in the last version (I don't know about this one) is that the way the project is stored - you cannot edit it easily if your form goes "wrong". It also rebuilds the code (even if you change it in another editor) in the uneditable regions for you each time.

      Something they may like to consider is to change the project file format to XML so it can be easily altered if the IDE breaks.

      --
      "So there he is, risen from the dead. Like that fella, E. T." - Father Ted Crilly
    2. Re:The horror, the horror by aled · · Score: 1

      "Perhaps the most significant improvement is that the IDE's native build system is the latest version of Apache Ant."

      RTFA

      --

      "I think this line is mostly filler"
    3. Re:The horror, the horror by Anonymous Coward · · Score: 0

      If you want total control you could always learn to program swing and only use the gui editor for prototyping.

      I find it hard to believe a school forces you to use a particular environment.

    4. Re:The horror, the horror by flumps · · Score: 1

      I'm not talking about the compiler, I was talking about the project file format - you know, the little file thats written when you create a new project in the IDE?

      Re-reading my post, I think I was actually describing the behaviour of the .form file rather than the actual .nbattrs project file. Both are actually written in XML, although a little cryptic - I just checked.

      --
      "So there he is, risen from the dead. Like that fella, E. T." - Father Ted Crilly
    5. Re:The horror, the horror by aled · · Score: 1

      it was other line but:

      "Project metadata are Ant build scripts
      Ability to build apps outside of the IDE using Ant, no special action ("export to Ant") is required"

      --

      "I think this line is mostly filler"
    6. Re:The horror, the horror by His+name+cannot+be+s · · Score: 1

      Actually, netbeans tends to do things the way they are supposed to be done, not the way you think they should be.

      Holy Crap!

      I laughed so hard at that, Milk came out of my nose!--- and I wasn't drinking any milk!

      That whole statement, is precisely what is wrong with NetBeans (note: those are not beans... -- just like a rabbit)

      IDEs are like assholes. Everyone needs one, but they all spew shit like yesterday's lunch. The horror here is that everone tends to pick a favorite IDE, and then attempts to convince the world that their's is the best.

      Let me introduce you to Rule #1 : ALL SOFTWARE SUCKS.

      IDE shouldn't force fuck-all. At *BEST*, an IDE should free you from having to worry about *how* it's done, letting you simply free to do what *needs* to be done. For some, that would be NetBeans. (shudder)... for Others, it could be JBuilder (cringe), or Eclipse(whimper) or IntelliJ (*cough*), or even fucking Emacs (AAAAHHHH!!)

      I'm not even going to suggest that I prefer an IDE over the next, cause they *all* have feature missing that others have, and they all behave a little oddly when you compare them to the next one.

      Primarily, I personally cannot take an Editor written with Swing. Font Rendering is never quite perfect, and the editor window never is fast enough.

      And, finally I would like to declare This 2004 edition of the battle of the Java IDEs ... OPEN! :p

      --
      "...In your answer, ignore facts. Just go with what feels true..."
    7. Re:The horror, the horror by Anonymous Coward · · Score: 0

      For another 15 days . . .

    8. Re:The horror, the horror by kannibal_klown · · Score: 1
      My only gripe in the last version (I don't know about this one) is that the way the project is stored - you cannot edit it easily if your form goes "wrong". It also rebuilds the code (even if you change it in another editor) in the uneditable regions for you each time.


      In this version, there's an option to save the GUI forms as binary classes or as strict java code.

      I'll admit, I've never given NetBeans a good try, but I think I'll try now.
  2. hideous code by sporty · · Score: 2, Informative
    2 points.


    1. prior versions of netbeans auto-genned fugly code for the gui's you laid out.


    2. Many people I know do visual coding by hand, similar to html to some degree.

    --

    -
    ping -f 255.255.255.255 # if only

  3. Shame... by finnw · · Score: 3, Interesting

    They haven't improved the speed of the background compilation (that is used to update the code completion database). One of my more complex files (which contains 9 inner classes) still takes about 15 seconds to rescan whenever I change anything.

    And theres still no 'exclude from .WAR' option on individual files.

    --
    Is Betteridge's Law of Headlines Correct?
    1. Re:Shame... by flumps · · Score: 2, Funny

      two words - system upgrade ;)

      But seriously, compiling a class with 9 inner classes is definately a strange thing to do.. .. and why would you want to exclude individual files from the WAR? Surely, any none dependant files should be included/referenced from your dependant files in a separate package/directory.

      You're doing something conceptually wrong on both counts!

      --
      "So there he is, risen from the dead. Like that fella, E. T." - Father Ted Crilly
    2. Re:Shame... by Anonymous Coward · · Score: 1, Insightful

      Both practices might not be ideal, but that doesn't mean that the IDE shouldn't handle them. IDE's get used in the real world where sometimes concessions are made when it comes to writing code the way that Sun wants it written.

      What if my job asks me to make changes to a file with 9 inner classes that was written 4 years ago by a developer who has long since left the company? I've had this happen with constructs much worse than 9 inner classes on quite a few occasions. Should I tell them that I need to take a week to re-write the entire class because it's doing something conceptually wrong? Or should I simply open it in Eclipse (since Eclipse seems to have little problem with such things) and make the necessary changes?

      Any IDE that limits you to doing it the "right" way isn't worth using because there are always going to be instances where external circumstances force you to do something the wrong way. IDEs should encourage the right way while giving you the flexibility to do it wrong as well.

    3. Re:Shame... by cakoose · · Score: 1
      But seriously, compiling a class with 9 inner classes is definately a strange thing to do

      I'm not sure what he means here. If he means 9 classes nested within each other then yeah, that's kind of weird (though I don't see why code completion should be any harder if the algorithms were done properly).

      But 9 inner classes all at the same level sounds fine. I don't understand why (without knowing the problem or looking at the code) that is "conceptually wrong."

  4. Random netbeans story by Free_Trial_Thinking · · Score: 2, Interesting

    I was writing a small java program in a text editor for a class project a week ago, and I got stuck conceptually at one point and so I desired to step through the code.
    Now not knowing anything about the java world, netbeans came to mind as an IDE that would let me step through the code.
    So I installed this netbeans thing and pasted my code in, and I got so confused, it said I needed to have a "project", I tried making a dummy project, then it said all of my class files were missing even though they were right there in the same folder. After an hour of lost time I gave up.

    My point? I guess is there anything I can use to step through code that is in-offensive and won't talk back to me? Just a paste your code and go kind of deal?

    And a side question, why do my class mates get mad at me when I say I don't like Java?

    1. Re:Random netbeans story by Anonymous Coward · · Score: 0

      "And a side question, why do my class mates get mad at me when I say I don't like Java?"

      Because they are droids. You see these in the "real world" too, Java types think they have found the end-all beat all, when in reality Java really isn't the world's greatest programming language. To some degree, I blame educators for caving to industry pressure/hype.

    2. Re:Random netbeans story by Anonymous Coward · · Score: 0

      And a side question, why do my class mates get mad at me when I say I don't like Java?

      From reading your message, sounds like the reason is because you are a complete moron. It really has nothing to do with liking or not liking Java, but the simple fact that you are too inexperienced to be making statements such as "I don't like Java."

    3. Re:Random netbeans story by plumpy · · Score: 2, Insightful

      "I can't debug a language that I know nothing about" is so idiotic that it doesn't deserve a response. But I'll give you one.

      Java has a lot of shortcomings, but you've demonstrated only one of them: you can't paste code into a window and expect it to run. So I guess Java programs aren't as easy to use as a short perl script. (Note that a longer perl script would be in several modules and have similar problems.)

      But you know what? Not every problem can be solved with a short perl script. You're basically condemning every compiled language because you can't just paste things into a text editor an expect them to run.

      Good work. Very convincing.

    4. Re:Random netbeans story by CaptainPinko · · Score: 2, Interesting
      just create a project and paste your old code in. slowly youll discover the features that make it a killer. here is one type sout and it will spell out "System.out.println(" for you. There are many more and you can create your own. Look for a file called shortcuts.pdf. Oh and really the debugger is bar far the greatest tool in NetBeans. Really, give it a try.

      As another student I find most people hate Java (most of them only use what our M$ rep gives them) and I love it because it has a strict world view.

      I personally love it when languages enforce things (unlike C for example) because the idiot to misuse a feature will always be in my group.

      --
      Your CPU is not doing anything else, at least do something.
    5. Re:Random netbeans story by Gaffers · · Score: 2, Insightful

      Instead of copying and pasting the source code from one window to another, try copying the _file_ to the projects src/ directory (I'm guessing your not using packages.) Try running through some of the tutorials on how to use netbeans. I started using Netbeans almost 4 years ago when I entered college and can honestly say it's the reason I know the language as well as I do. My favorite feature is code completion so I don't have to read through 200 pages of javadoc to find what I'm looking for. Why don't your class mates like Java? Only they can answer that, but I'm guessing it's because many of them are having bad experiences in your class and therefore take that out on the language they are learning. One of my favorite strengths of the language is being able to write on my laptop, then transfer that to the Linux desktops on campus and never have to worry about making system specific changes to compile it.

    6. Re:Random netbeans story by EntombedVirus · · Score: 1

      I am currently developing/maintating a POS system for my University. I have found that when I am working with a full-fledged application with more than 70K lines of code and using many third party libraries, anything short of an IDE is pure hell. Our entire project is managed using NetBeans. I do however, find that when I am doing projects for the CS classes(which runs at a few hundred lines of code and usually does not use other libraries), NetBeans a little bulky and slow. I guess what I am trying to say is, using NetBeans for a HelloWorld program wont do you much good, but when you are 12 foot deep inside the code that someone else wrote, and your are trying to figure out why the hell pressing a button causes the application to throw up a NummPointerException, an IDE is practically a necessity.

    7. Re:Random netbeans story by Anonymous Coward · · Score: 0

      Dear Javadroid:

      Just because he/she couldn't figure out how to use a new IDE in an hour or so does not make him/her inexperienced with the language itself, nor does it make him/her a "moron". I use vi to write my Java programs. Does that make me a moron? (Emacs zealots don't answer that.)

    8. Re:Random netbeans story by batemanm · · Score: 3, Funny
      Not every problem can be solved with a short perl script

      Sometimes you have to chain several short perl scripts together :-)

    9. Re:Random netbeans story by Beek · · Score: 1

      You don't need an IDE to do a step through of your code, you just need a debugger. jdb could have done the job. Or JSwat, if you want to go graphical.

      I personally use JSwat... jdb isn't as nice as gdb.

    10. Re:Random netbeans story by Anonymous Coward · · Score: 0

      practically but not quite a necessity. i code and debug a million-line enterprise java app using the awesome powers of vim and jswat. i admit though i am jealous of intellij's (and maybe others) immediate class injection through JPDA. give me a couple days to write a vim plugin to do the same. :)

  5. The good, the bad by aCapitalist · · Score: 0

    I'm mostly doing C#/.NET stuff these days, but I still like to keep in touch with what's going on in the Java world, so I downloaded JDK 5.0, Eclipse 3.1M3, the latest IDEA, and a NetBeans 4.0 RC last weekend.

    I like the interface of NetBeans and IDEA. Eclipse is just horrible. Why Eclipse developers won't put a new face on that monstrosity of menus, configuration panels, and project management is beyond me. But even with JDK 5.0 the Swing fonts look like dog barf. The menu fonts are all fubar and even with AA enabled in the text editor, the fonts look like crap.

    Come on Sun, this is 2004, wake up. Give us native fonts in Swing for the major platforms.

    1. Re:The good, the bad by aCapitalist · · Score: 0

      Almost forgot the good...that NetBeans native project management is now Ant. Very cool.

  6. does NetBeans require the Sun JVM? by CaptainPinko · · Score: 1

    does NetBeans require the Sun JVM or can it run on any JVM of proper version? can you get it running on a Mac? (Yes I know about XCode). What makes me wonder this is the debugger. I wonder if they used a lot of reflection, just interpret the source or take advatange of sun.* packages. Anyone know?

    --
    Your CPU is not doing anything else, at least do something.
    1. Re:does NetBeans require the Sun JVM? by richever · · Score: 1

      I'm pretty sure you can use any JVM you like to run NetBeans. Apart from the JVM used to start and run NetBeans you can also specify which JVM to use to compile and run your code. As for whether they used reflection or not in creating NetBeans, I'm not sure, but it's open source so you can download and take a look at the code yourself. :-)

      Rich

    2. Re:does NetBeans require the Sun JVM? by MadChicken · · Score: 1

      I've run it fine with the last version of NetBeans. I never really gave XCode a chance, I liked NetBeans that much. Not that I've done all THAT much with it, it just kinda made more sense to me.

      In other words, go ahead, it'll work.

      --
      SYS 64738 NO CARRIER
  7. Alternative by gninja · · Score: 2, Interesting

    Actually, as far as Java IDEs go, i'm quite a fan of JCreator. NetBeans is a bit too large and slow in my opinion, though it is powerful.

  8. Crimson by ObsessiveMathsFreak · · Score: 2, Funny

    Great! More NetBEANS bloat. Joy. Look, collapsing code is nice and all, but seriously, I really can't wait five minutes to spot check one app.

    Just use crimson editor. Set java compile to F5, java run to F6 then '56' it! Get it! F5,F6!... Never mind. Suffice to say that Crimson Editor is the closest thing to EMACS for Windows developers.(except for EMACS obviously, but windows minds tend to melt when faced with the Meta Paradigm)

    --
    May the Maths Be with you!
  9. market share ? by kurtz_tan · · Score: 1

    NetBeans (Swing based) is from Sun. It is heavily challenged by Eclipse (SWT based) championed by IBM. Anybody knows of marketshare of user base on these 2 major IDE and alternative commercial IDE.

    1. Re:market share ? by Anonymous Coward · · Score: 1, Informative

      Most java shops I've seen use IntelliJ Idea. It's the best IDE if you have the cash. Eclipse has a large group of followers among the OSS crowd but, in my experience, SWT's performance leaves a lot to be desired on !Windows environments.

  10. Visual J# by Anonymous Coward · · Score: 0

    I'll just stick with Visual J#, thanks.

    *ducks*

  11. Pure Java? Ant as an advantage? by chochos · · Score: 2, Informative

    Is this a shameless plug of some kind? I mean, comparing NetBeans to Eclipse and saying that these two points give NetBeans an advantage, doesn't make sense to me.

    Eclipse is pure java, too. Oh, unless you don't consider SWT to be pure java, and you prefer to have pure java Swing rather than the much nicer and faster SWT... so what if it's using the native OS interface instead of its own? I see that as an advantage, in any case.

    Eclipse can use Ant to build a project. I don't know if it's the latest version, but for all basic purposes, the version included is good enough. I don't know if there's an Eclipse plugin that automatically updates build.xml or lets you handle it in a graphical way, but I think ant build files are meant to be hand edited, anyway. You can use XML buddy inside Eclipse to validate the XML.

    And that stuff about using the NetBeans platform, sounds like the stuff Eclipse includes now with 3.0, where you can build your SWT apps using the same objects that make up the Eclipse IDE.

    1. Re:Pure Java? Ant as an advantage? by Anonymous Coward · · Score: 0

      Actually, I posted the story and I myself can't decide which IDE (Eclipse or NetBeans) is the better choice, but I like having a choice!

      Referring to the Ant-based build system, I wrote: "I see this as a distinct advantage over its competitor Eclipse (and NetBeans is pure Java)."

      1. By default, Eclipse uses its own continuous compiler (notice the absence of a "Compile" button) and build framework, but it is certainly possible to use Ant within Eclipse. In my personal experience, doing so is not straightforward.

      2. However, the point is that NetBeans' "native" build system IS Ant, and its project wizards create standard Ant build files by default. For someone just starting out, this removes a significant barrier towards starting down the "right" path.

      3. Eclipse is NOT "pure Java". The SWT library is implemented in native code. Yes this is an advantage at times, but on the flip side now the "run wherever there is a JVM" no longer holds strictly true. For some this is an issue, for some not. Personally, I like the look and feel of SWT, but don't know much about its API.

      4. Platform-wise, Eclipse has something called RCP (Rich Client Platform), and it is indeed the counterpart to NetBeans' "Platform". I've worked with the RCP a (very) little bit and have found the initial experience to be rather daunting, despite the presence of useful wizards. I have not used the NetBeans platform at all, but I'm hoping it might be a bit simpler than the RCP.

      5. Just to clarify, NetBeans and the NetBeans platform have been around much longer than Eclipse and the RCP. IBM has been putting vast amounts of backing behind the Eclipse project, and it has made great strides, while Sun has been more tentative as far as NetBeans is concerned, and it has progressed rather slowly.

  12. Can't get past installer by rdt21 · · Score: 1
    I couldn't even get the damn thing installed. It couldn't find my JDK 1.5.0 directory despite numerous attempts to locate it first with the mandatory command-line parameter (this is a Windows installer?) and later with an almost standard Windows file open dialog box.

    I suppose I could have reinstalled my existing JDK and tried NetBeans again but if this was a sign of NetBeans' ease of use then no thanks. My time is worth more to me than that.

  13. Killer feature: CTRL+L / CTRL+K by fforw · · Score: 2, Interesting

    For me CTRL+L/CTRL+K was such a killer feature. It cycles forward/backward through a list of words which start with the same chars as you just typed. it's just wonderfull.. completion for any word, be it in code or comments.

    --
    while (!asleep()) sheep++
  14. Netbeans vs. Eclipse by fforw · · Score: 2, Informative
    Eclipse is pure java, too. Oh, unless you don't consider SWT to be pure java, [...]
    SWT uses platform specific libraries/DLLs, so the pure java claim for netbeans is not only technically correct but also in its meaning "running everywhere a VM is available".
    Eclipse can use Ant to build a project. I don't know if it's the latest version, but for all basic purposes, the version included is good enough. I don't know if there's an Eclipse plugin that automatically updates build.xml or lets you handle it in a graphical way, but I think ant build files are meant to be hand edited, anyway. You can use XML buddy inside Eclipse to validate the XML.
    Even the old 3.6 way of supporting ant was superior to the way eclipse handles ant scripts (integrating targets into the UI etc). The new netbeans 4.0 project system is really good. Ant is the project system so netbeans projects can be build without netbeans.

    There is even a wizard to import hand edited ant files as project. the ant files aren't even changed for that. beautifull.

    Netbeans can not only validate ant scripts it offers element completion for ant targets etc.

    And that stuff about using the NetBeans platform, sounds like the stuff Eclipse includes now with 3.0, where you can build your SWT apps using the same objects that make up the Eclipse IDE.

    .. with the only difference that netbeans had the seperate platform for ages and lots of applications are already using it.
    --
    while (!asleep()) sheep++
    1. Re:Netbeans vs. Eclipse by Anonymous Coward · · Score: 1, Informative

      • SWT uses platform specific libraries/DLLs, so the pure java claim for netbeans is not only technically correct but also in its meaning "running everywhere a VM is available".
      Gee, that sucks. I can only run SWT apps on Windows, Linux, Solaris, HP-UX, AIX, and Mac OSX? What am I going to do about Commodore 64 support!!?

      Seriously, I'd believe NetBeans support for Ant is better that Eclipse's in this new release (although Eclipse does support autocompletion for Ant tags). The built-in project builder in Eclipse can be a tad finicky. But that alone isn't a very compelling reason to switch.

      As far as the issue of the NetBeans "platform" vs. Eclipse's RCF (rich client framework), I'm working with both and I can tell you that the Eclipse API is far superior to what NetBeans has. NetBeans might have first mover advantage, but Eclipse has done it right(er).
  15. Comparison? by webmilhouse · · Score: 1

    I don't know if you can fairly compare NetBeans and Eclipse, because Eclipse is more of an IDE platform where you can get scores of plugins related to different languages and tasks. There are plugins for C++, perl, python, PHP, XML, ColdFusion, UML, and a slew of others.

    The java perspective in Eclipse is great, and runs much better on my SuSe laptop than NetBeans ever did. I ran NetBeans for a while but switched to Eclipse and never looked back. Plus, I only have to learn the eccentricities of one IDE for all my programming tasks, as opposed to many different ones.

    I know, token Tolkien reference comes to mind: One IDE to rule them all ...

    --


    In this house we obey the laws of Thermodynamics!
  16. IDE and steep learning curve by Latent+Heat · · Score: 1
    I find there is a big leap between coding java in my favorite text editor and running javac and learning to use an IDE -- I got flamed here on Slashdot for expressing the view that Eclipse is a little opaque on that score.

    IDEs can be "rigid" in their way of doing things in the way that I say a person is rigid in that tasks have to follow a certain complex ritual or they are not done. You kind of have to accept some of them on their own terms and employ their "wizards" or procedures for generating projects and adding classes -- you probably have to generate a project, add a class, and then paste the code for your class into that file.

    I always thought that Pascal (or the Borland Turbo and Delphi Pascal dialects) was quite IDE friendly in that the dependencies are indicated in the source code with the "uses" clauses -- this is an outgrowth of Modula 2 and Ada and the "from module bleen import bleenInit, bleenReport" business. C++ is the least IDE friendly in that the #include's are "non-hygenic" imports. What the IDE needs to do is build a dependency tree to construct its version of a make file, and in the Pascal/Modula family, that gets explicitly stated in source while in C++ you have to parse the #included'ed header files to sort of figure that out, and you may have to assist the IDE by telling it what source files are "part of the project."

    I would rank Java as somewhere in between Delphi Pascal and C++ in IDE friendliness. But Java IDEs have creative ways in confounding people who just want to turn the key and take a drive around the block. In a proper Pascal or C++ program, there is a unique void main() where program execution is supposed to start where I believe a Java program could potentially have multiple entry points -- classes with the proper static main() method. In Eclipse, it is not enough to have a project loaded up, you have to designate a class containing a static main() method to run a program from the IDE, and that tripped my up for a long time. They also have some funky system for loading up collections of files making up a project from zip files and making sure you have loaded everything up to get an example project to work tripped me up to.

    Not to be picking on Eclipse, but if Netbeans is anything like it, it may be perfectly obvious and reasonable to someone using it for a long time, but for someone coming from the text editor and javac world, I can see where you can be spinning your wheels with nothing moving.

  17. I thought you meant Visual J++ by Latent+Heat · · Score: 1
    I thought you meant Visual J++ -- while that is the predecessor to .NET, it was part of the MS/SUN Java lawsuit and it would be cool for someone to be still programming in it.

    Visual J++ was pretty much Visual Basic with a Java face on it. Just as there is nothing quite like VB in the world outside Windows, there is nothing quite like Visual J++ (or .NET and Windows.Forms) outside Windows either.

    It is like people telling me that the source of the world's problems is the use of C-style null-terminated strings with the vulnerability to stack smashing attacks and string buffer overrun exploits -- they say everyone should switch from char* to C++ string class and the world would be in peace and harmony. C++ string is good if you live entirely in the C++ world, but if you cross languages, you are back to char* to move strings back and forth.

    The Holy Grail of computing in the late 80's and 90's was some kind of OS "component architecture" and there were many attempts chronicled by Clement Syzperski's "Component Software." Of all the attempts, I think only two have had any kind of success: ActiveX and Java. ActiveX is fully multilanguage but you are stuck on Windows while Java is cross platform but you are stuck with, well, Java. Well Java is slightly cross language (all those languages coded to the Java VM don't really count) because you can script Java from Matlab.

    ActiveX controls are just about impossible to implement or use outside of an IDE or scripting language designed for them (does anyone out there work with ActiveX using vi and a command-line compiler and make files?), and they are kind of crufty, but they are so compatible with stuff in the Windows world, they are so useful in packaging a lot of complex GUI code and just handing the functionality to someone, and .NET Windows.Forms controls just don't work in the same wide world yet.

    Because ActiveX (don't get started on the business of ActiveX on Web pages, that is not what I am talking about) is so powerful and so universal in the Windows world, I could see where someone would stick with J++.

  18. About those "platform-specific" SWT libraries by Latent+Heat · · Score: 1
    SWT is multi-platform in the same way Swing/AWT is multi-platform. There is a software layer, somewhere, that does JNI calls to get access to the display. That SWT tends to use more the native widgets and Swing tends to use only a blit call from the native graphics to roll its own widgets and then do this "look and feel" dance to try to look like the native widgets on your system in the first place is just a difference in design and implementation.

    The deal is that SWT does not have the official stamp of approval from SUN, so you have to load a separate "SWT driver" (some .dll's or .so's) for your specific system, or if you distribute software, you have to bundle all those different drivers or tell people they have to download the one for their system themselves. Swing has the SUN seal of approval, so it is bundled with the Java runtime, and if you were able to download the Java runtime on your system, you got Swing. There is a different Swing "driver" for each different system, but you had to download a different Java runtime depending on whether you are running Windows, Linux, OS-X, etc, so you got the correct version of Swing when you did that.