UWECProgrammer/ConsolidatedMentionResolutionBenchmark

sentence stringlengths 1 1.38k	label stringclasses 3 values
I used to use MyEclipse quite a bit.	o
It had a decent IDE for making Swing forms and such.	o
I assume it has improved in the past year - they seem to add features in gobs and heaps, quite often.	o
URL_http://www.myeclipseide.com / .	o
That is the netbeans one which has been ported.	o
Use NetBeans, I have also successfully developed one application using NetBeans.	p
It is realy awesome, it helps you while writing the code.	p
Since Swing generates some code on its own so it is really helpful to use Netbeans.	p
Go through it and you can always ask question and problems.	o
It will be good if you go for latest version release.	p
I have always coded my UIs by hand.	o
The frustration of dealing with screen builders and filling out all those property sheets is too much for me.	o
After a couple of screens and a little research I am just as productive.	n
As others have mentioned, my best experience with Java SWING applications is with NetBeans.	p
NetBeans has a WYSIWYG editor, and the code is automatically generated for you, which is then protected, however you can add custom code to add listeners and other events that the end user may be interested in using, such as buttons, text forms and areas, and other nice GUI tools.	p
When I use swing, I usually use the NetBeans.	o
If you prefer the Eclipse IDE, there are the Visual Editor plugin.	p
URL_https://developers.google.com/java-dev-tools/download [window-builder-pro] is good option and it is free also.	p
Is Java Swing still in use?	o
I am planning on making a Java Swing application and was wondering if Swing is still used or if it has been replaced with something else.	o
Thanks in advance!	o
Related: URL_http://stackoverflow.com/questions/407343/where-are-swing - applications-used.	o
Related: URL_http://stackoverflow.com/questions/408820/what-is-the-difference - between-swing-and-awt.	o
Related: URL_http://stackoverflow.com/questions/2377467/if-swing-has-more - features-to-design-a-form-then-what-is-the-use-of-awt-in-java.	o
_**Swing is still in use.... but there is AWT!!	o
AWT: Speed: use of native peers speeds component performance.	o
Look and Feel: AWT components more closely reflect the look and feel of the OS they run on.	o
Portability: use of native peers creates platform specific limitations.	o
Some components may not function at all on some platforms.	o
Third Party Development: the majority of component makers, including Borland and Sun, base new component development on Swing components.	o
There is a much smaller set of AWT components available, thus placing the burden on the programmer to create his or her own AWT-based components.	n
Features: AWT components do not support features like icons and tool-tips.	o
Swing: Portability: Pure Java design provides for fewer platform specific limitations.	o
Behavior: Pure Java design allows for a greater range of behavior for Swing components since they are not limited by the native peers that AWT uses.	p
Features: Swing supports a wider range of features like icons and pop-up tool-tips for components.	o
Vendor Support: Swing development is more active.	o
Sun puts much more energy into making Swing robust.	p
Look and Feel: The pluggable look and feel lets you design a single set of GUI components that can automatically have the look and feel of any OS platform (Microsoft Windows, Solaris, Macintosh, etc.).	o
It also makes it easier to make global changes to your Java programs that provide greater accessibility (like picking a hi-contrast color scheme or changing all the fonts in all dialogs, etc.).	p
Performance: Swing components are generally slower and buggier than AWT, due to both the fact that they are pure Java and to video issues on various platforms.	n
Since Swing components handle their own painting (rather than using native API's like DirectX on Windows) you may run into graphical glitches.	o
Look and Feel: Even when Swing components are set to use the look and feel of the OS they are run on, they may not look like their native counterparts.	o
URL_http://edn.embarcadero.com/article/26970 [More-Reading.	o
] .	o
"Applet Portability: most Web browsers support AWT classes so AWT applets can run without the Java plugin.	o
"This is patently false.	n
ugh?	o
I guess this is 1990s and you are still using Netscape 4.0, right?	o
Edited it..........	o
I wouldn't recommend AWT, it gets very little love these days (other than the bits that are needed for Swing).	n
Better to use SWT if you want to go down the native path.	o
"Most Web browsers do not include the Swing classes, so the Java plugin must be used.	o
" What?	o
The Swing classes are part of the JRE, not the browser.	o
I don't recall this being a problem in 2003.	o
For all these negatives, I have edited the question.....	o
they not look like their native counterparts that one made me giggle.	o
At least on Windows I have yet to see a single control (apart from JLabel maybe) that looks and feels like its native counterpart with the native LAF :-).	o
"rather than using native API's like DirectX on Windows": false, Swing uses Java2D, which may use DirectX when supported.	n
"Swing components are generally buggier than AWT": this is false as well.	n
Swing is still there and well supported.	p
Most of the reasons why people hated swing when it first came out are no longer valid simply because of Moores Law, along with improved JVMs.	o
Swing apps no loger feel jerky and unrepsonsive and an accumulation of minor improvements result in a more professional looking GUI.	o
Its also worth looking at the "groovy/swing" combination for rapid development and prototyping.	p
Docs for Swing, on the other hand, are dire to nonexistent.	n
Aggree that the docs are lacking somewhat, but, IDE support is pretty good, and, googling usually gets you some decent usage examples.	n
Real programmers don't read documentation.	o
There is a lot of tuning in Swing that cannot be attributed to Moores law.	o
@JMcO For documentation -> URL_http://download - llnw.oracle.com/javase/tutorial/uiswing/.	o
Yes it is still in use.	o
short and to the point.	o
We still use it.	o
Not everything is a web app, so far there have been some tentative replacements (such as SWT, which eclipse is written in) SWT has a native layer that wraps the underlying calls to the native windowing layer.	o
It only works for a limited set of platforms and of course requires some third party shared libraries.	p
I would venture to say that there are far fewer SWT apps than Swing apps.	o
Although swing is still in use, I would rather chose URL_http://wiki.eclipse.org/index.php/Rich_Client_Platform [Eclipse-RCP] as a platform for desktop applications, since it also provides a huge amount of plugins.	o
Eclipse RCP uses Eclipse's own SWT, which means you need the native SWT libraries.	o
You can also build on the NetBeans Platform, which is built on Swing: URL_http://platform.netbeans.org/ .	o
Yes, it still is in use.	o
The library is still part of the JRE, and will probably be that way for the future.	o
There are other options though.	o
For instance, you may want to look at JavaFX if you need a rich UI; or using SWT in your application.	o
Maybe you want some kind of 3D effects, and you need to look into a 3D engine like jpct or the jmonkeyengine.	o
Java has progressed somewhat since the software Swing world.	o
jmonkeyengine is only for games.	o
Yes.	o
Roughly URL_http://hewgill.com/~greg/stackoverflow/stack_overflow/tags/#!	o
swing+javafx+wpf+qml [1-out-of-120-questions] on StackOverflow is about Swing!	o
[enter image description here]( URL_http://i.stack.imgur.com/OwRhP.png) .	o
Yes, it's still in use.	o
Takes while to get used to but once you have it, it's a pretty nice framework for writing applications.	o
Have a look at Webstart for deploying your application.	o
Also a bit of a clunker to start with but really handy when you're comfortable .	p
Swing is still the preferred way to build heavy-weight, e.g.	n
"Desktop" applications, in Java.	o
If your code is running in a web browser, you will likely use other things.	o
But for freestanding desktop apps, it is quite excellent and in wide use.	p
For desktop programs, yes, Swing is heavily in use.	n
However there are many alternatives because alot of people think that Swing is heavily verbose and hard to work with.	o
JavaFX is worth taking a look at .	p

I used to use MyEclipse quite a bit.

o

It had a decent IDE for making Swing forms and such.

o

I assume it has improved in the past year - they seem to add features in gobs and heaps, quite often.

o

URL_http://www.myeclipseide.com / .

o

That is the netbeans one which has been ported.

o

Use NetBeans, I have also successfully developed one application using NetBeans.

p

It is realy awesome, it helps you while writing the code.

p

Since Swing generates some code on its own so it is really helpful to use Netbeans.

p

Go through it and you can always ask question and problems.

o

It will be good if you go for latest version release.

p

I have always coded my UIs by hand.

o

The frustration of dealing with screen builders and filling out all those property sheets is too much for me.

o

After a couple of screens and a little research I am just as productive.

n

As others have mentioned, my best experience with Java SWING applications is with NetBeans.

p

NetBeans has a WYSIWYG editor, and the code is automatically generated for you, which is then protected, however you can add custom code to add listeners and other events that the end user may be interested in using, such as buttons, text forms and areas, and other nice GUI tools.

p

When I use swing, I usually use the NetBeans.

o

If you prefer the Eclipse IDE, there are the Visual Editor plugin.

p

URL_https://developers.google.com/java-dev-tools/download [window-builder-pro] is good option and it is free also.

p

Is Java Swing still in use?

o

I am planning on making a Java Swing application and was wondering if Swing is still used or if it has been replaced with something else.

o

Thanks in advance!

o

Related: URL_http://stackoverflow.com/questions/407343/where-are-swing - applications-used.

o

Related: URL_http://stackoverflow.com/questions/408820/what-is-the-difference - between-swing-and-awt.

o

Related: URL_http://stackoverflow.com/questions/2377467/if-swing-has-more - features-to-design-a-form-then-what-is-the-use-of-awt-in-java.

o

_**Swing is still in use.... but there is AWT!!

o

AWT: Speed: use of native peers speeds component performance.

o

Look and Feel: AWT components more closely reflect the look and feel of the OS they run on.

o

Portability: use of native peers creates platform specific limitations.

o

Some components may not function at all on some platforms.

o

Third Party Development: the majority of component makers, including Borland and Sun, base new component development on Swing components.

o

There is a much smaller set of AWT components available, thus placing the burden on the programmer to create his or her own AWT-based components.

n

Features: AWT components do not support features like icons and tool-tips.

o

Swing: Portability: Pure Java design provides for fewer platform specific limitations.

o

Behavior: Pure Java design allows for a greater range of behavior for Swing components since they are not limited by the native peers that AWT uses.

p

Features: Swing supports a wider range of features like icons and pop-up tool-tips for components.

o

Vendor Support: Swing development is more active.

o

Sun puts much more energy into making Swing robust.

p

Look and Feel: The pluggable look and feel lets you design a single set of GUI components that can automatically have the look and feel of any OS platform (Microsoft Windows, Solaris, Macintosh, etc.).

o

It also makes it easier to make global changes to your Java programs that provide greater accessibility (like picking a hi-contrast color scheme or changing all the fonts in all dialogs, etc.).

p

Performance: Swing components are generally slower and buggier than AWT, due to both the fact that they are pure Java and to video issues on various platforms.

n

Since Swing components handle their own painting (rather than using native API's like DirectX on Windows) you may run into graphical glitches.

o

Look and Feel: Even when Swing components are set to use the look and feel of the OS they are run on, they may not look like their native counterparts.

o

URL_http://edn.embarcadero.com/article/26970 [More-Reading.

o

] .

o

"Applet Portability: most Web browsers support AWT classes so AWT applets can run without the Java plugin.

o

"This is patently false.

n

ugh?

o

I guess this is 1990s and you are still using Netscape 4.0, right?

o

Edited it..........

o

I wouldn't recommend AWT, it gets very little love these days (other than the bits that are needed for Swing).

n

Better to use SWT if you want to go down the native path.

o

"Most Web browsers do not include the Swing classes, so the Java plugin must be used.

o

" What?

o

The Swing classes are part of the JRE, not the browser.

o

I don't recall this being a problem in 2003.

o

For all these negatives, I have edited the question.....

o

they not look like their native counterparts that one made me giggle.

o

At least on Windows I have yet to see a single control (apart from JLabel maybe) that looks and feels like its native counterpart with the native LAF :-).

o

"rather than using native API's like DirectX on Windows": false, Swing uses Java2D, which may use DirectX when supported.

n

"Swing components are generally buggier than AWT": this is false as well.

n

Swing is still there and well supported.

p

Most of the reasons why people hated swing when it first came out are no longer valid simply because of Moores Law, along with improved JVMs.

o

Swing apps no loger feel jerky and unrepsonsive and an accumulation of minor improvements result in a more professional looking GUI.

o

Its also worth looking at the "groovy/swing" combination for rapid development and prototyping.

p

Docs for Swing, on the other hand, are dire to nonexistent.

n

Aggree that the docs are lacking somewhat, but, IDE support is pretty good, and, googling usually gets you some decent usage examples.

n

Real programmers don't read documentation.

o

There is a lot of tuning in Swing that cannot be attributed to Moores law.

o

@JMcO For documentation -> URL_http://download - llnw.oracle.com/javase/tutorial/uiswing/.

o

Yes it is still in use.

o

short and to the point.

o

We still use it.

o

Not everything is a web app, so far there have been some tentative replacements (such as SWT, which eclipse is written in) SWT has a native layer that wraps the underlying calls to the native windowing layer.

o

It only works for a limited set of platforms and of course requires some third party shared libraries.

p

I would venture to say that there are far fewer SWT apps than Swing apps.

o

Although swing is still in use, I would rather chose URL_http://wiki.eclipse.org/index.php/Rich_Client_Platform [Eclipse-RCP] as a platform for desktop applications, since it also provides a huge amount of plugins.

o

Eclipse RCP uses Eclipse's own SWT, which means you need the native SWT libraries.

o

You can also build on the NetBeans Platform, which is built on Swing: URL_http://platform.netbeans.org/ .

o

Yes, it still is in use.

o

The library is still part of the JRE, and will probably be that way for the future.

o

There are other options though.

o

For instance, you may want to look at JavaFX if you need a rich UI; or using SWT in your application.

o

Maybe you want some kind of 3D effects, and you need to look into a 3D engine like jpct or the jmonkeyengine.

o

Java has progressed somewhat since the software Swing world.

o

jmonkeyengine is only for games.

o

Yes.

o

Roughly URL_http://hewgill.com/~greg/stackoverflow/stack_overflow/tags/#!

o

swing+javafx+wpf+qml [1-out-of-120-questions] on StackOverflow is about Swing!

o

[enter image description here]( URL_http://i.stack.imgur.com/OwRhP.png) .

o

Yes, it's still in use.

o

Takes while to get used to but once you have it, it's a pretty nice framework for writing applications.

o

Have a look at Webstart for deploying your application.

o

Also a bit of a clunker to start with but really handy when you're comfortable .

p

Swing is still the preferred way to build heavy-weight, e.g.

n

"Desktop" applications, in Java.

o

If your code is running in a web browser, you will likely use other things.

o

But for freestanding desktop apps, it is quite excellent and in wide use.

p

For desktop programs, yes, Swing is heavily in use.

n

However there are many alternatives because alot of people think that Swing is heavily verbose and hard to work with.

o

JavaFX is worth taking a look at .

p