Interested to Buy Any Domain ? << Click Here >> for more details...
heavy components means what?
- 4 Answers
- 7162 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / ranganathkini
Heavy components are GUI components which depend on a native
peer for displaying themselves. AWT uses heavy weight
components. This means that when u try to create a heavy
component, AWT realizes a native peer or creates a native
object and requests that native object to draw the component
using native APIs.
Heavy components are bad performes as they consume a lot of
system resources and have platform specific look and feel.
Also they are not fast as updates and notifications have to
pass thru several layers of method calls and callbacks to
get executed.
An alternative is the SWING GUI library which does not
depend on native objects for display, they use the Java 2D
API for drawing and display. These objects are much more
light weight and are very fast.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / devarathnam c,kotagudibanda(po
Hi...
Heavy components means , the components that are fully
dependent on underlaying OS.
Example:Applet
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / arjun sanapathi
lightweight component have transparent pixels which
heavyweight have opaque and also light weight is not dependent
on other objects.
| Is This Answer Correct ? | 0 Yes | 0 No |
What are the uses of synchronized keyword?
What is a string what operation can be performed out with the help of a string?
Hi buddy, well i got that there is always a default constructor with abstract class. OK. But why not with interface? Thanks in advance.
How to pass arraylist to stored procedure in java?
What is the purpose of an interface?
What is the difference between I ++ and ++ I in java?
What is the difference between int and integer in java?
IS method overriding is Duplication of Methods?
What value is a variable of the string type automatically initialized?
Why does java have two ways to create child threads? Which way is better?
If you are reviewing the code of your team members, what points will you look at, assuming the performance of the application is not so great
Explain the available thread states in a high-level?
Core Java 
