Re: Is it really this retro?
I think there are IDEs that do some of that.
Re: Is it really this retro?
Netbeans IDE has a good Swing toolbox to do what you require.
Welcome to NetBeans
Though it is probably best to start off writing GUIs programmatically as it eases your development of learning GUIs.
Re: Is it really this retro?
The new Eclipse Indigo release packages the Window Designer package which allows you to easily design Swing and SWT apps.
Re: Is it really this retro?
<<The new Eclipse Indigo release packages the Window Designer package which allows you to easily design Swing and SWT apps.>>
That's what I downloaded, and looking through the menu items, it doesn't seem obvious where this Window Designer is (maybe I'm suffering temporary selective blindness...?)
Re: Is it really this retro?
The swing designer stuff isn't under the Java folder when you're trying to create a new file. If you scroll down (after you select "new->other"), there's a folder called "WindowBuilder". Inside there is are a few different options, including the Swing Designer and SWT Designer.
Alternatively, if you have your own JComponent (say, a custom JFrame) you should be able to just right click the source file and say "Open With->Window Builder Editor"
Re: Is it really this retro?
GUI designers are fine for one-off fire-and-forget GUI developments, but if you're likely to have to maintain or enhance a GUI, they can be a horrible trap because the code they generate and/or the components they use are generally not easily maintainable by hand, so you are reliant on having that particular GUI designer, tools and even jars, available. I know from bitter experience that you can't rely on this.
For serious work, it's far better to write the GUI yourself using simple and easy-to-understand layouts like BorderLayout, BoxLayout, CardLayout, etc. This is more likely to give you maintainable code.
Re: Is it really this retro?
Quote:
Originally Posted by
dlorde
GUI designers are fine for one-off fire-and-forget GUI developments, but if you're likely to have to maintain or enhance a GUI, they can be a horrible trap because the code they generate and/or the components they use are generally not easily maintainable by hand, so you are reliant on having that particular GUI designer, tools and even jars, available. I know from bitter experience that you can't rely on this.
For serious work, it's far better to write the GUI yourself using simple and easy-to-understand layouts like BorderLayout, BoxLayout, CardLayout, etc. This is more likely to give you maintainable code.
I use both. The GUI designer is great for creating a base to work off of, but the part I like the most about Eclipse's GUI builder is the ability to basically modify the source file any way you want, letting you clean up and refine the way the GUI works, or even dramatically change its behavior or look via the code.
Re: Is it really this retro?
Quote:
Originally Posted by
helloworld922
I use both. The GUI designer is great for creating a base to work off of, but the part I like the most about Eclipse's GUI builder is the ability to basically modify the source file any way you want, letting you clean up and refine the way the GUI works, or even dramatically change its behavior or look via the code.
Naturally, once you have some experience and knowledge, it's a judgement call - how easy is the generated code to work with, can you (or will you want to) use the GUI designer on it once you've hacked it manually, how much is there to do, etc., etc. My point is that you shouldn't become dependent on a particular GUI designer, and you do need to know how to do the job manually :cool: