CodeGuru Staff

Bruce Eckel’s Thinking in Java Contents | Prev | Next The priority of a thread tells the scheduler how important this thread is. If there are a number of threads blocked and waiting to be run, the scheduler will run the one with the highest priority first. However, this doesn’t mean that threads with lower […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next A thread can be in any one of four states: New: the thread object has been created but it hasn’t been started yet so it cannot run. Runnable: This means that a thread can be run when the time-slicing mechanism has CPU cycles available for […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next You can think of a single-threaded program as one lonely entity moving around through your problem space and doing one thing at a time. Because there’s only one entity, you never have to think about the problem of two entities trying to use the same […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next As a starting point, consider a program that performs some CPU-intensive operation and thus ends up ignoring user input and being unresponsive. This one, a combined applet/application, will simply display the result of a running counter: //: Counter1.java // A non-responsive user interface package c14; […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next Objects provide a way to divide a program up into independent sections. Often, you also need to turn a program into separate, independently-running subtasks. Each of these independent subtasks is called a thread, and you program as if each thread runs by itself and has […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next I suggest placing the superscript after Swing in “Introduction to Swing.”After working your way through this chapter and seeing the huge changes that have occurred within the AWT (although, if you can remember back that far, Sun claimed Java was a “stable” language when it […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next and Beans So far in this book you’ve seen how valuable Java is for creating reusable pieces of code. The “most reusable” unit of code has been the class, since it comprises a cohesive unit of characteristics (fields) and behaviors (methods) that can be reused […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next Java 1.1 has also added some important new functionality, including focus traversal, desktop color access, printing “inside the sandbox,” and the beginnings of clipboard support. Focus traversal is quite easy, since it’s transparently present in the AWT library components and you don’t have to do […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next In Java 1.1 a dramatic change has been accomplished in the creation of the new AWT. Most of this change revolves around the new event model used in Java 1.1: as bad, awkward, and non-object-oriented as the old event model was, the new event model […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next It’s possible to see that for safety’s sake you can have only limited behavior within an applet. In a real sense, the applet is a temporary extension to the Web browser so its functionality must be limited along with its knowledge and control. There are […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next As noted previously, action( ) isn’t the only method that’s automatically called by handleEvent( ) once it sorts everything out for you. There are three other sets of methods that are called, and if you want to capture certain types of events (keyboard, mouse, and focus events) […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next The way that you place components on a form in Java is probably different from any other GUI system you’ve used. First, it’s all code; there are no “resources” that control placement of components. Second, the way components are placed on a form is controlled […]