Win a copy of Spring Boot in Practice this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

AWT vs. Jbuilder

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was messing around with some visual layout stuff in JBuilder, and I noticed that there are some controls that have duplicate functionality. Some of the them are of the format JControlName. In the descriptions they usually say they are an alternative to the AWT version of the control. Can anyone just give me a little explanation here and maybe some thoughts as to whether it matters which I use and why?
 
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ben,
The controls that are in the form JControlName are alternatives to the AWT version, but they are not provided by JBuilder. They are part of JFC (Java Foundation Classes) and are collectively known as Swing components.
Swing is newer than AWT, and many of the components are improved. Some are exclusive to Swing. But we still use AWT for layouts, events, and other things. I like Swing better, but I know that a lot of companies haven't moved to it yet. Also, current browsers don't support Swing, so to use Swing in an Applet, you need to supply your users with the Plug-in. According to recent news, you will be needing this Plug-in to run applets in all future versions of IE anyway because it will no longer have a Virtual Machine of any type built in!!! But that's a subject for another thread...
 
reply
    Bookmark Topic Watch Topic
  • New Topic