Hello guys. This is just an opinion. Which Java IDE should I use. Eclipse or NetBeans. I usually like to develop applications and create GUI windows. So which one should I use?
Eclipse vs. NetBeans
Collapse
X
-
Tags: None
-
For GUI with Eclipse you need a plugin for that. Netbeans doesn't need a plugin for GUIs.Originally posted by Kid ProgrammerHello guys. This is just an opinion. Which Java IDE should I use. Eclipse or NetBeans. I usually like to develop applications and create GUI windows. So which one should I use?
Which one should you use? I prefer Eclipse.
Matter of preference I guess. -
Using such a drag-and-drop thing for gui building is AVBT (A Very Bad Thing (tm)).
Those things create code for you that you don't understand, the code is very
screen size dependent and it smells funny. Guis are best built using proper
LayourManagers and a proper nesting of gui Components.
Find a consistent way to build up your guis, separate the controller functionality
from the view functionality (many separate small methods!) and knit them together
in a sort of generic way and you're almost there. Let those LayoutManagers do
the rest of the boring work. You don't need Netbeans for that; better have an IDE
that gives you full control over (the structure of) your code.
kind regards,
JosComment
-
I swithched from eclipse to netbeans 6.0 a fortnight ago, and had many problems with it. I found netbeans "doing the stuff for you kind" which i dont like personally, i like to put my jar file(for web projects) for struts,jsf etc manually, netbeans does this for me. I find eclipse very fast and doesnt make you feel the "lazy kind" like "let me put the jars for you".Originally posted by JosAHUsing such a drag-and-drop thing for gui building is AVBT (A Very Bad Thing (tm)).
Those things create code for you that you don't understand, the code is very
screen size dependent and it smells funny. Guis are best built using proper
LayourManagers and a proper nesting of gui Components.
Find a consistent way to build up your guis, separate the controller functionality
from the view functionality (many separate small methods!) and knit them together
in a sort of generic way and you're almost there. Let those LayoutManagers do
the rest of the boring work. You don't need Netbeans for that; better have an IDE
that gives you full control over (the structure of) your code.
kind regards,
Jos
This is in context to web projects like struts,jsf etc in netbeans, i dont know about the GUI stuff. Jos said it well.
regards.Comment
-
Originally posted by r035198x... and can't edit.
True, I once played with a thing that generated code for me and it put some
magic incantations in the comment lines as well as a warning "do not delete".
Guess what I do when I see a warning sign "wet, do not touch" so I deleted
those magic spells. There was no way I could alter that gui with that tool
anymore; they are so cute. not.
kind regards,
JosComment
-
I had a thing like that too. It was called Netbeans.Originally posted by JosAHTrue, I once played with a thing that generated code for me and it put some
magic incantations in the comment lines as well as a warning "do not delete".
Guess what I do when I see a warning sign "wet, do not touch" so I deleted
those magic spells. There was no way I could alter that gui with that tool
anymore; they are so cute. not.
kind regards,
JosComment
-
I never really trusted Sun's code quality; Java is the first different thing: they haveOriginally posted by r035198xI had a thing like that too. It was called Netbeans.
JSRs and expert groups and other companies define and implement most of the
reference implementations .
kind regards,
JosComment
-
Testify, brother! Another problem with the automatically generated code is that it stinks. Or rather, if you want to use a design like Model-View-Presenter:Originally posted by JosAHUsing such a drag-and-drop thing for gui building is AVBT (A Very Bad Thing (tm)).
Those things create code for you that you don't understand, the code is very
screen size dependent and it smells funny. Guis are best built using proper
LayourManagers and a proper nesting of gui Components.
Find a consistent way to build up your guis, separate the controller functionality
from the view functionality (many separate small methods!) and knit them together
in a sort of generic way and you're almost there. Let those LayoutManagers do
the rest of the boring work. You don't need Netbeans for that; better have an IDE
that gives you full control over (the structure of) your code.
kind regards,
Jos
http://martinfowler.co m/eaaDev/uiArchs.html
You will be going in and redoing the code.Comment
-
Most of the people don't think of components like that (nice article btw); all theyOriginally posted by BigDaddyLHTestify, brother! Another problem with the automatically generated code is that it stinks. Or rather, if you want to use a design like Model-View-Presenter:
http://martinfowler.co m/eaaDev/uiArchs.html
You will be going in and redoing the code.
want is that their buttons and what have you look nice without having to deal
with LayoutManagers; the behaviour of these components is just an afterthought.
kind regards,
JosComment
-
I guess I've been on the pokey end of that stick for too long. And I'm thinking of web apps, where the stick is both longer and pokier. So you end up with a web page that needs to be tested, and the only way to do that is to step through 10 previous web pages, over and over again. <nightmare-ish screaming/>Originally posted by JosAHMost of the people don't think of components like that (nice article btw); all they
want is that their buttons and what have you look nice without having to deal
with LayoutManagers; the behaviour of these components is just an afterthought.
kind regards,
JosComment
-
It sounds like I should go with Eclipse. I usually find auto generated code easy but I'm not learning anything. I'll stick with Eclipse.Comment
-
The greatest day on earth in my java career was when I learned that I *COULD* in fact place widgets at pure x,y locations and not use some layoutmanager.
But that might be due to hating having to specify widget placements like an HTML table. Span this way, shrink this way. Bah.Comment
-
I had a different epiphany:Originally posted by PlaterThe greatest day on earth in my java career was when I learned that I *COULD* in fact place widgets at pure x,y locations and not use some layoutmanager.
But that might be due to hating having to specify widget placements like an HTML table. Span this way, shrink this way. Bah.
But it was all right, everything was all right, the struggle was finished. He had won the victory over himself. He loved GridBagLayout.Comment
-
Try JDeveloper....I usually find auto generated code easy but I'm not learning anything.
You will amazed about the generated code.....
It is readable enough by a java programmer....
And most of all? the generated code is editable, you can have an experiment on it...
That's what i've care for....
and also IDX Java IDE.... Not a gui builder but it interprets all of your classes in diagram.... You'll see the diagram about your codes.... with code completion, syntax checker debugger and a window to browse the Java Core API Documentation.. .(Only for Windows)
That is what im using now in my project and im always guided by that diagram.(Useful if you forgot the specific blocks of your code.)
You'll never regret....
regards,
sukatoaComment
Comment