Talk:Swing (Java)

message: The following phrase seems to be a leftover and does not make sense in the current context.
"The disadvantage of lightweight components is slower execution. The advantage is uniform behavior on all platforms."
71.112.18.252 (talk) 02:15, 28 November 2007 (UTC)
thread_title:  More lightweight/heaviweigth discussion 

message: I had a recent assignment to find the origin of the name of Swing (Java) and one student submitted this link stating that the name was based off the 1930's dance craze. Can anyone else confirm or deny this claim with sources? I already googled and looked through the Sun website.
: Closest reference I can find is from an 1998 version of the Swing website: "Swing was the project name chosen by the developers of the new high-level components. Although these components are now part of the JFC software, the Swing name persists." I would not be surprised if the Swing team chose the name based on the dance (as opposed to the several other meanings of that word). I seem to recall hearing something to that effect at the time, but can't track down a reference. -- BrianDuff
I wondered about this, and found this article which seems kosher. 
https://blogs.oracle.com/thejavatutorials/entry/why_is_swing_called_swing 
Ety uncertain (talk) 07:24, 30 June 2009 (UTC)
thread_title:  Swing Origins 

message: Suggest we get a section on (and screenshots of) Swing in Vista - apparently it's rather more than just a port from XP.
Some links : http://weblogs.java.net/blog/chet/archive/2006/10/java_on_vista_y.html
http://weblogs.java.net/blog/chet/archive/2005/08/mustang_swing_a.html
--Wootery 23:09, 12 December 2006 (UTC)
thread_title:  Swing on Vista 

message: Was just skimming through the article for some general information on Swing and found the comparison with AWT unclear:
"...every Swing lightweight interface ultimately exists within an AWT heavyweight component because all of the top-level components in Swing ... extend an AWT top-level container."
A little more explanation of the relationship between the two would be helpful: if the AWT components are tied to native OS controls, and the Swing components are extensions of AWT components, how then do the Swing components manage to be "lightweight"? Are these AWT top-level containers so abstract as to not involve any of the "heavyweight" code? Do the Swing components extend them just to retain a consistent interface?
:Only the top level components like windows are heavyweight, the components inside them (buttons, scrollbars, text fields, etc) are not - for the most part they're drawn using Java graphics routines. So it means that a JButton exists within a JWindow and therefore within a Window. --Jamoche 18:49, 8 October 2006 (UTC)
thread_title:  Lightweight/heavyweight distinction 

message: Swing is a set of classes that provides more powerful and flexible functionality that is possible with standard and advanced AWT(Abstract Window Toolkit) components.These are not implemented by platform specific code. Instead they are written entirely in Java, therefore, they are platform independent. 
Fundamentals of swing is the JApplet class that extends the Applet class. Applets that use Swing must be subclasses of the JApplet class  —The preceding unsigned comment was added by AbhishekDutta1987 (talk • contribs) 02:22, 1 May 2007 (UTC)
thread_title:  JAVA SWING 

message: The Hello world example used on this article is not really a Hello world IMHO:
* the use of Runnable and threading stuff is not necessary in such a basic program as this one, making the example more complex that it should. Threading stuff vs Swing should be in a new paragraph.
* There's too much comments in the code, which should be outside the code, in the paragraph.
* Centering the frame in the middle of the screen is also not necessary in this example.
I have no problem to modify the example myself, but I'm asking for comments on this proposal before ;-)
Hervegirod (talk) 10:23, 23 February 2008 (UTC)
replies: text: since I have received no comment since February (more than one month), I assumed people agree with my proposal. Hervegirod (talk) 12:29, 28 March 2009 (UTC)
thread_title:  Hello world 

message: Could someone please have a look at the external links section? The ones that are left after the so-called cleanup from Aug 27th are mostly useless. (A blog with less than 2 dozen entries that was started in May this year remained, but the links to java.sun.com were deleted...) 195.212.29.163 (talk) 14:39, 26 September 2008 (UTC)
replies: text: I agree. The cleanup of the external links was idiotic. The Swing tutorial link is one I consider invaluable.  —Preceding unsigned comment added by 66.245.20.81 (talk) 22:28, 16 August 2009 (UTC)
thread_title:  External links 

message: Swing has some disadvantages. Most important one seems to be single threaded model, this is very limiting. Also Swing component takes more time to render. Im pretty sure that regular users of Swing can find others.  —Preceding unsigned comment added by 82.145.248.24 (talk) 05:02, 6 June 2009 (UTC)
thread_title:  Disadvantages 

message: does anyone know if the seperate release of swing for use on older versions of java is still available for download and if so from where? Plugwash (talk) 15:33, 19 November 2009 (UTC)
thread_title:  download 

message: That code at the end is a mess. I've written cleaner code and I'm 13. --75.166.224.107 (talk) 21:41, 22 November 2009 (UTC)
thread_title:  Messy Code 

message: Added section about possibility to use Swing on web with third party product (similar section to for example http://en.wikipedia.org/wiki/Standard_Widget_Toolkit#Use_on_the_web).
Change reveted by Salix_alba (reason: advert for AjaxSwing). Don't want to advert anything, want to show web possibility of Swing as compared to SWT, currently shows SWT as having that advantage over Swing. Would be glad to hear any comments or suggestions on that revision.  —Preceding unsigned comment added by 79.135.222.215 (talk) 18:18, 20 October 2010 (UTC)
thread_title:  Use on the web 

message: Hello fellow Wikipedians,
I have just modified  on Swing (Java). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Corrected formatting/usage for http://www.sun.com/smi/Press/sunflash/1998-12/sunflash.981208.9.xml
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—cyberbot IITalk to my owner:Online 22:44, 4 April 2016 (UTC)
thread_title:  External links modified 

message: I do not understand why the following example "Game" is needed in this article. This article is meant as a clear and concise description of the Swing widget toolkit not as a tutorial. Wikipedia articles provide information not serve as tutorials, there are other resources for that. If we take a look at the articles of other widget-toolkits I'm sure we won't find a "game-example".
Moreover the code in this example isn't very good Java code. It uses deprecated features and is certainly not well-written. The wording of the given explanation is also not clear and for some reason the text "File:C:\Users\Travor\Pictures\GameSample.png|thumb|class MoveObj run in Windows NT 6.2" has been inserted below it.--Furquanahmad (talk) 17:02, 13 May 2016 (UTC)
thread_title:  Why this example is needed? 

message: There are currently three mentions in the article text to JavaFX as Swing's 'successor', which seems strange to me, as they have different goals. Also, as time has shown, Swing is still in the base JDK/JRE, while JavaFX was jettisoned into an independent library.
The successor claims seem to be uncited, and blame suggests the mentions were introduced arbitrarily by proponents of JavaFX. I propose removing them. Chabala (talk) 05:36, 20 March 2024 (UTC)
thread_title:  JavaFX successor POV issue