Eclipse Window Builder VS Netbeans GUI Builder

Question

I would start J2SE projects for abuntu OS. I am trying to create a Netbeans graphical editor and an Eclipse constructor.

Both of them are good, drag and click, double-click to create an event handler, such as VisualStudio.

However, I did a Netbeans study, someone said:

The second main drawback of Matisse is that it is simply not good enough, you place the components in a grid, Matisse then creates XML with the attributes of the component, then generates Java code for the components on the grid. It seems cool, but then you decided that you want to add a button somewhere in the form or resize the component - this procedure can lead to the mixing of all gui, throwing adjacent components in different places - fixing can be a pain in the neck. Even if you managed to place all the components where they should only be manually changed, some of the generated netbeans code is a BIG problem, a problem that you cannot get out of if you do not start all over again.

Does this error exist on the latest netbeans? What is the Pros. and cons. between the NetBeans GUI collector and the Eclipse Windowbuilder?

Answer 1

I have been using NetBeans since 6.x and have never had such problems. Resizing components, adding some new ones, even working on generated code, etc., is really easy and without problems. In addition, NB has a visual debugger and an improved GridBagLayout configuration (as with 7.1).

I have not used Eclipse Windowbuilder yet, but I think he is capable too. Each has its own criteria for the gui builder. Btw. the author of this article seems very eclipse-oriented ("the eclipse is the best IDE there")

I'm sorry that I cannot give you an answer like "pro / cons of A, pro / cons of B" - as I said, I have never used Eclipse Windowbuilder before. And for me there is no need to do this, I can create gui with netbeans without problems / very simple / fast (even better than with Visual Studio). For my point of view, everything works the way I want :-)

If you have used both options, there are probably some things that you prefer or dislike in one IDE, but others can do better.

Answer 2

Personally, although WindowBuilder is a pretty powerful tool to use in Eclipse, I find it more awkward (and, frankly, I prefer to write the Swing GUI manually if this is the only option)

Matisse is a much better option due to Grid editors like the ones mentioned earlier, and I also prefer Matisse to handle event handlers on WindowBuilder. Another thing is that Matisse succeeds in adding more properties to GUI element settings, where WindowBuilder translates a very small list of mutable functions (leaving you to dive through a mess of autogenerated code to change a simple property).

Eclipse has a version of matisse, although the plugin is not free (see myeclipse).

Answer 3

I used both Eclipse and Netbeans,

Eclipse -WindowBuilder is a powerful tool that easily modifies it. But it causes more code problems. A long time after you receive Spagetti codes to solve the problem. When you encounter a problem, you cannot open the Desing layer.

Netbeans generates codes very easily, and you can change them, but more complicatedly, sometimes you cannot. But I do not get (only a few, my errors) any problems with the code ... or etc., if you have a problem with the component; You can get the default settings too easily anytime.

Note: ONLY MY IDEA!