You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by gs...@apache.org on 2008/01/31 18:47:27 UTC
svn commit: r617171 - in /harmony/standard/site: docs/
docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ xdocs/
xdocs/subcomponents/classlibrary/ xdocs/subcomponents/drlvm/
Author: gshimansky
Date: Thu Jan 31 09:47:23 2008
New Revision: 617171
URL: http://svn.apache.org/viewvc?rev=617171&view=rev
Log:
Removed undisplayable non-unicode character 0xa0 that comes from editing files in Word,
should be replaced with a space everywhere.
Modified:
harmony/standard/site/docs/contributors.html
harmony/standard/site/docs/roadmap.html
harmony/standard/site/docs/subcomponents/classlibrary/awt.html
harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html
harmony/standard/site/docs/subcomponents/drlvm/EM.html
harmony/standard/site/docs/subcomponents/drlvm/JIT.html
harmony/standard/site/xdocs/roadmap.xml
harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html
harmony/standard/site/xdocs/subcomponents/classlibrary/DNSsupport.html
harmony/standard/site/xdocs/subcomponents/drlvm/EM.html
harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html
Modified: harmony/standard/site/docs/contributors.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/contributors.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/contributors.html (original)
+++ harmony/standard/site/docs/contributors.html Thu Jan 31 09:47:23 2008
@@ -304,7 +304,7 @@
<td>A</td>
</tr>
<tr>
- <td class="TableCell">(Jimmy)Jiny Lv</td>
+ <td class="TableCell">(Jimmy)Jing Lv</td>
<td class="TableCell">IBM CN</td>
<td class="TableCell">A</td>
</tr>
Modified: harmony/standard/site/docs/roadmap.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/roadmap.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/roadmap.html (original)
+++ harmony/standard/site/docs/roadmap.html Thu Jan 31 09:47:23 2008
@@ -677,7 +677,7 @@
<tr>
<th class="TableHeading" colspan="" rowspan="" width="">
- IA32 <br>(Pentuim III or better)</br>
+ IA32 <br>(Pentium III or better)</br>
</th>
<td class="" colspan="" rowspan="">
Modified: harmony/standard/site/docs/subcomponents/classlibrary/awt.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/awt.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/awt.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/awt.html Thu Jan 31 09:47:23 2008
@@ -433,7 +433,7 @@
<i>AWT events</i> generated and handled by the AWT framework. All
AWT events are subclasses of the <code>AWTEvent</code> class and
are stored in the AWT event queue represented by
- the�<code>EventQueue</code> class.
+ the <code>EventQueue</code> class.
</li>
</ul>
<h3>
@@ -441,7 +441,7 @@
</h3>
<p>
AWT has the <i>event dispatch thread</i> (EDT) at its basis,
- represented by the class�<code>java.awt.EventDispatchThread</code>.
+ represented by the class <code>java.awt.EventDispatchThread</code>.
This thread handles all generated types of events by going over the
loop. EDT starts on AWT Toolkit creation and stops
on application termination.
@@ -459,22 +459,22 @@
<li>
Dispatch the AWT event: find the target AWT component for this
event and pass it to this component through
- the�<code>java.awt.Dispatcher</code> class.
+ the <code>java.awt.Dispatcher</code> class.
</li>
<li>
Push the AWT event to the event queue represented by
- the�<code>java.awt.EventQueue</code> class.
+ the <code>java.awt.EventQueue</code> class.
</li>
<li>
Pop all AWT events from the event queue.
</li>
<li>
Pass the given AWT events to the appropriate AWT component by using
- the�<code>java.awt.Component.processXYZEvent()</code> methods.
+ the <code>java.awt.Component.processXYZEvent()</code> methods.
</li>
<li>
Call the appropriate AWT component’s event listeners of
- the�<code>EventListener</code> interface. Applications should
+ the <code>EventListener</code> interface. Applications should
implement appropriate listeners' interfaces to react to specific
events.
</li>
@@ -496,8 +496,8 @@
If a non-EDT thread generates an AWT event when EDT is waiting for
a native event, a new native event is required to wake EDT and make
it handle the AWT event. Every time a non-EDT thread adds an event
- to the queue, the method�<code>awake()</code> of
- the�<code>NativeEventQueue</code> interface is called. This method
+ to the queue, the method <code>awake()</code> of
+ the <code>NativeEventQueue</code> interface is called. This method
produces a native auxiliary event so that EDT becomes ready to
handle AWT events. EDT treats this auxiliary event as <a
href="#Native_Event_classification">invisible</a>.
@@ -616,7 +616,7 @@
<ul>
<li>
Interacting with the underlying native window system, such
- as�<code>Win32</code> or�<code>X11</code>, by way of handling
+ as <code>Win32</code> or <code>X11</code>, by way of handling
native focus events and making native focus requests
</li>
<li>
@@ -663,11 +663,11 @@
</p>
<ul>
<li>
- The�<code>java.awt.FocusDispatcher</code> class handles focus
+ The <code>java.awt.FocusDispatcher</code> class handles focus
events received from the window toolkit level.
</li>
<li>
- Package-private methods of the�<code>KeyboardFocusManager</code>
+ Package-private methods of the <code>KeyboardFocusManager</code>
class manage focus on the higher AWT level.
</li>
</ul>
@@ -760,7 +760,7 @@
<p>
The AWT level of the focus subsystem handles focus requests
synchronously on every successful focus change request. When the
- method�<code>requestFocus()</code> is called, the keyboard focus
+ method <code>requestFocus()</code> is called, the keyboard focus
manager posts all necessary AWT events in the required order
irrespective of the success or failure of the native focus request. In
other words, the AWT subsystem does not wait until the native focus
@@ -783,12 +783,12 @@
<ul>
<li class="notetext">
When a top-level native window gains focus, the focus goes to a
- child of this window or the�<code>Window</code> component itself,
+ child of this window or the <code>Window</code> component itself,
in case no child elements are available.
</li>
<li class="notetext">
When a window in another application gains focus, the focus
- dispatcher calls the�<code>setFocus(false)</code> method on the
+ dispatcher calls the <code>setFocus(false)</code> method on the
focus owner to clear the focus owner value.
</li>
</ul>
@@ -815,7 +815,7 @@
focus manager ignores events sent to the window that has failed to
become the focused window because the corresponding AWT event was
dispatched and vetoed.<br />
- When handling the�<code>WINDOW_GAINED_FOCUS</code> event, private
+ When handling the <code>WINDOW_GAINED_FOCUS</code> event, private
methods in the keyboard focus manager set focus on the appropriate
child component of the window.
</dd>
@@ -846,29 +846,29 @@
<p>
You can paint standard components in many ways, including drawing the
component parts (text, background, shadows and all other elements) by
- the means of class�<code>java.awt.Graphics</code>. Note that the
+ the means of class <code>java.awt.Graphics</code>. Note that the
framework must not paint standard components by the
- method�<code>java.awt.Component.paint()</code> because it could be
+ method <code>java.awt.Component.paint()</code> because it could be
overridden. Instead, when processing a painting event, the framework
calls the package-private
- method�<code>java.awt.Component.prepaint()</code> just before calling
- the method�<code>paint()</code>. The�<code>prepaint()</code> method
+ method <code>java.awt.Component.prepaint()</code> just before calling
+ the method <code>paint()</code>. The <code>prepaint()</code> method
does the actual painting for all standard components by delegating the
painting task to the theme. This approach might not seem optimal, but
it works on all supported platforms without any changes.
</p>
<p>
- The�<code>org.apache.harmony.awt.Theme</code> class implements the
+ The <code>org.apache.harmony.awt.Theme</code> class implements the
default theme. Methods of this class do the following:
</p>
<ul>
<li>
Paint standard components, for example, the
- method�<code>drawButton()</code>.
+ method <code>drawButton()</code>.
</li>
<li>
Calculate the optimal component size for each type of component,
- for example, by using the method�<code>calculateButton()</code>.
+ for example, by using the method <code>calculateButton()</code>.
</li>
</ul>
<p>
@@ -883,19 +883,19 @@
<p>
You can create a custom theme that inherits from the default theme and
contains specific features. The current implementation contains
- the�<code>WinTheme</code> class that extends the default theme as
+ the <code>WinTheme</code> class that extends the default theme as
shown in Figure 5.
</p>
<p>
To use the native API in your theme, extend the default theme
overriding its painting methods. In the derived theme, you can use the
additional features of specific implementation of
- the�<code>Graphics</code> class, and explicitly call native API
- functions via wrappers, see�<code>org.apache.harmony.misc</code>
+ the <code>Graphics</code> class, and explicitly call native API
+ functions via wrappers, see <code>org.apache.harmony.misc</code>
package for details. Figure 5 below demonstrates theme-related classes
- hierarchy with methods related to the�<code>Button</code> component as
+ hierarchy with methods related to the <code>Button</code> component as
an example. A block of code for extending
- the�<code>drawButton()</code> method is shown in <a
+ the <code>drawButton()</code> method is shown in <a
href="#ExampleButton">Example 1</a> below.
</p>
<p style="text-align: center">
@@ -907,7 +907,7 @@
</p>
<p>
After creating a derived theme, turn it on by using the
- property�<code>awt.theme</code>. This property contains the name of a
+ property <code>awt.theme</code>. This property contains the name of a
subclass of default theme class used as the theme by all components.
If the property points to a non-existent class or if the required
native library is missing, or any other error occurs, the default
@@ -917,7 +917,7 @@
</p>
<p>
To force the default theme, set the command-line
- option�<code>-Dawt.theme=0</code>. As long as zero is an invalid class
+ option <code>-Dawt.theme=0</code>. As long as zero is an invalid class
name, this does the job.
</p>
<p class="backtotop">
@@ -933,17 +933,17 @@
and the contained text. Because not all these attributes are visible
through the public API, the DRL AWT module provides a set of
interfaces to allow the theme to access private and public data. The
- package�<code>org.apache.harmony.awt.state</code> contains these
+ package <code>org.apache.harmony.awt.state</code> contains these
interfaces, such
- as,�<code>TextState</code>,�<code>CheckboxState</code>,
- and�<code>ButtonState</code>. Each standard component class has an
+ as, <code>TextState</code>, <code>CheckboxState</code>,
+ and <code>ButtonState</code>. Each standard component class has an
inner class that implements the appropriate interface and has the
state field of that class declared.
- The�<code>java.awt.Component</code> class stores all functionality
+ The <code>java.awt.Component</code> class stores all functionality
common for all types of standard components. Specifically,
- the�<code>java.awt.Component</code> class has an inner
- class�<code>ComponentState</code> that implements
- the�<code>org.apache.harmony.awt.state.State</code> interface. This
+ the <code>java.awt.Component</code> class has an inner
+ class <code>ComponentState</code> that implements
+ the <code>org.apache.harmony.awt.state.State</code> interface. This
inner class enables implementing the state of a specific component by
overriding only a few methods.
</p>
@@ -954,8 +954,8 @@
</p>
<p>
Platform-specific and component-specific code is concentrated in
- separate helper classes, such as�<code>DefaultButton</code>, the
- helper to the default theme, and�<code>WinCheckbox</code>, the helper
+ separate helper classes, such as <code>DefaultButton</code>, the
+ helper to the default theme, and <code>WinCheckbox</code>, the helper
to the Windows<a href="#*">*</a> theme. The theme class contains only
simple methods.
</p>
@@ -963,7 +963,7 @@
<a id="ExampleButton" name="ExampleButton"></a>Example 1
</p>
<p class="exampletext">
- This is an example with the�<code>Button</code> component.
+ This is an example with the <code>Button</code> component.
</p>
<pre class="exampletext">
public void drawButton(Graphics g, ButtonState s) {
@@ -985,8 +985,8 @@
Figure 6 shows an example of component classes relation, inner states
and the inheritance hierarchy of component state interfaces. The
figure contains short names for convenience, for example,
- �<code>Component</code> actually means
- �<code>java.awt.Component</code>.
+ <code>Component</code> actually means
+ <code>java.awt.Component</code>.
</p>
<p style="text-align: center">
<img alt="Methods and classes related to state change operations"
@@ -1005,11 +1005,11 @@
</h3>
<p>
This section illustrates how the state interfaces are used in
- the�<code>Button</code> component. In DRL AWT, all standard components
+ the <code>Button</code> component. In DRL AWT, all standard components
follow the same model.
</p>
<p>
- This is a part of the�<code>java.awt.Button</code> code that
+ This is a part of the <code>java.awt.Button</code> code that
illustrates how to use visual themes in standard components.
</p>
<pre>
@@ -1021,7 +1021,7 @@
}
</pre>
<p>
- The framework calls the�<code>prepaint()</code> method, which paints
+ The framework calls the <code>prepaint()</code> method, which paints
standard components. The painting itself is done by the theme class,
and all the information it requires is contained in the state
variable.
@@ -1032,14 +1032,14 @@
</h3>
<p>
In DRL, the Windows<a href="#*">*</a> theme is implemented by the
- class�<code>org.apache.harmony.awt.theme.windows.WinTheme</code>,
+ class <code>org.apache.harmony.awt.theme.windows.WinTheme</code>,
which inherits from the
- class�<code>org.apache.harmony.awt.Theme</code>.
+ class <code>org.apache.harmony.awt.Theme</code>.
</p>
<p>
- The�<code>WinTheme</code> class paints components using the Windows<a
- href="#*">*</a> API function�<code>DrawFrameControl()</code> in the
- classic mode and�<code>DrawThemeBackground()</code> in the XP mode,
+ The <code>WinTheme</code> class paints components using the Windows<a
+ href="#*">*</a> API function <code>DrawFrameControl()</code> in the
+ classic mode and <code>DrawThemeBackground()</code> in the XP mode,
and basic Windows<a href="#*">*</a> API painting functions.
</p>
<p>
@@ -1047,26 +1047,26 @@
</p>
<ul>
<li>
- The class�<code>org.apache.harmony.awt.gl.WinThemeGraphics</code>
+ The class <code>org.apache.harmony.awt.gl.WinThemeGraphics</code>
has a set of native methods that call the Windows<a href="#*">*</a>
API. This class is tightly coupled
- with�<code>org.apache.harmony.awt.gl.WinGDIPGraphics2D</code>,
- which is an implementation of�<code>java.awt.Graphics</code>.
- The�<code>WinThemeGraphics</code> class
- queries�<code>WinGDIPGraphics2D</code> for the current clip,
+ with <code>org.apache.harmony.awt.gl.WinGDIPGraphics2D</code>,
+ which is an implementation of <code>java.awt.Graphics</code>.
+ The <code>WinThemeGraphics</code> class
+ queries <code>WinGDIPGraphics2D</code> for the current clip,
translation and device context.
</li>
<li>
The
- class�<code>org.apache.harmony.awt.wtk.windows.WinEventQueue.ThemeMap</code>
+ class <code>org.apache.harmony.awt.wtk.windows.WinEventQueue.ThemeMap</code>
that handles theme-related native events and opens and closes
handles of native theme data when needed.
</li>
<li>
The set of helper
- classes�<code>org.apache.harmony.awt.wtk.theme.windows</code>
+ classes <code>org.apache.harmony.awt.wtk.theme.windows</code>
responsible for specific types of components, for
- example,�<code>org.apache.harmony.awt.wtk.theme.windows.WinButton</code>.
+ example, <code>org.apache.harmony.awt.wtk.theme.windows.WinButton</code>.
</li>
</ul>
<p class="note">
@@ -1109,8 +1109,8 @@
<p>
For example, if a thread adds a component to a list of child
components for a container without updating this component’s
- field�<code>parent</code>, another thread working with the same
- component gets the wrong value of the�<code>parent</code> field.
+ field <code>parent</code>, another thread working with the same
+ component gets the wrong value of the <code>parent</code> field.
Moreover, the second thread may remove this component from the
container children list, which makes the behavior of the first thread
unpredictable. Synchronization helps avoid such problems.
@@ -1124,7 +1124,7 @@
implementation uses a special monitor <em>AWT lock</em> more powerful
than built-in Java<a href="#*">*</a> synchronized blocks and methods.
The AWT lock is similar to the synchronization tools provided by
- the�<code>java.util.concurrent</code> package. The synchronized
+ the <code>java.util.concurrent</code> package. The synchronized
section using the AWT lock has its own specifics, as demonstrated by
the example below.
</p>
@@ -1133,9 +1133,9 @@
</p>
<p class="exampletext">
This example provides an excerpt of code from
- the�<code>Component</code> class demonstrating a typical synchronized
- section in the AWT code. The methods�<code>lockAWT()</code>
- and�<code>unlockAWT()</code> are the boundaries of the critical
+ the <code>Component</code> class demonstrating a typical synchronized
+ section in the AWT code. The methods <code>lockAWT()</code>
+ and <code>unlockAWT()</code> are the boundaries of the critical
section. The code between them is synchronized by the AWT lock.
</p>
<pre>
@@ -1155,7 +1155,7 @@
</pre>
<p>
From the syntactical standpoint, this is a try-finally structure,
- which guarantees that the�<code>unlockAWT()</code> method is always
+ which guarantees that the <code>unlockAWT()</code> method is always
called after doing the useful work in the body of try block.
Logically, it is used as an ordinary synchronized block, except when
using AWT lock extended functionality.
@@ -1176,24 +1176,24 @@
</p>
<ul>
<li>
- Components, such as�<code>Component</code>,�<code>Button</code>,
- and�<code>Frame</code>
+ Components, such as <code>Component</code>, <code>Button</code>,
+ and <code>Frame</code>
</li>
<li>
- Layout managers, such as�<code>FlowLayout</code>
- and�<code>GridBagLayout</code>
+ Layout managers, such as <code>FlowLayout</code>
+ and <code>GridBagLayout</code>
</li>
<li>
- Auxiliary, such as�<code>Toolkit</code>
- and�<code>KeyboardFocusManager</code>
+ Auxiliary, such as <code>Toolkit</code>
+ and <code>KeyboardFocusManager</code>
</li>
</ul>
<p>
The total number of synchronized classes nears 40.
</p>
<p>
- Simple data structures, for example,�<code>Rectangle</code>
- or�<code>Point</code>, are not protected from concurrent modifications
+ Simple data structures, for example, <code>Rectangle</code>
+ or <code>Point</code>, are not protected from concurrent modifications
for performance reasons.
</p>
<dl>
@@ -1207,7 +1207,7 @@
synchronized by the AWT lock. Package-private methods and private
method are not, with only a few <a
href="#SyncExceptions">exceptions</a>. For an example, see
- the�<code>java.awt.Toolkit</code> class.
+ the <code>java.awt.Toolkit</code> class.
</li>
<li>
A synchronized section of code must not call user code, such as
@@ -1226,12 +1226,12 @@
<li>
Certain methods might get overridden by user code, but are called
under the AWT lock, for example, the
- method�<code>addNotify()</code> in the�<code>Component</code>
- and�<code>Container</code> classes.
+ method <code>addNotify()</code> in the <code>Component</code>
+ and <code>Container</code> classes.
</li>
<li>
Platform-specific code of
- the�<code>org.apache.harmony.awt.wtk</code> package must not use
+ the <code>org.apache.harmony.awt.wtk</code> package must not use
the AWT lock explicitly.
</li>
</ul>
Modified: harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html (original)
+++ harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html Thu Jan 31 09:47:23 2008
@@ -273,7 +273,7 @@
Alexei Zakharov, Nadya Morozova: document created.
</td>
<td class="TableCell">
- � March 23, 2006
+ March 23, 2006
</td>
</tr>
<tr>
@@ -284,7 +284,7 @@
Nadya Morozova
</td>
<td class="TableCell">
- � September 21, 2006
+ September 21, 2006
</td>
</tr>
Modified: harmony/standard/site/docs/subcomponents/drlvm/EM.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/EM.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/EM.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/EM.html Thu Jan 31 09:47:23 2008
@@ -436,13 +436,13 @@
<p>
The VM core component sends requests to EM to execute methods. VM
passes a method handle and parameters to the execution manager through
- the�<code><a href="#EM_VM">EM_VM</a></code> interface. EM selects the
+ the <code><a href="#EM_VM">EM_VM</a></code> interface. EM selects the
engine for compiling the method and sends a compilation request to VM
to compile the method with the selected engine.
</p>
<p>
Instantiating and configuring JIT compilers goes through
- the�<code>JIT_EM</code> interface [<a href="#DRLDevGuide">3</a>]. In
+ the <code>JIT_EM</code> interface [<a href="#DRLDevGuide">3</a>]. In
its turn, the execution manager exports the <code>EM_JIT</code>
interface for accessing method profiles and profile collectors.
Specifically, the <a href="#EM_JIT">EM_JIT</a> interface consists of
@@ -530,7 +530,7 @@
<a id="EM_PC" name="EM_PC"></a>EM_PC Interface
</h3>
<p>
- The�<code>EM_PC</code> interface handles interaction between the
+ The <code>EM_PC</code> interface handles interaction between the
execution manager and the profile collectors and consists of the
following function groups:
</p>
Modified: harmony/standard/site/docs/subcomponents/drlvm/JIT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/subcomponents/drlvm/JIT.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/docs/subcomponents/drlvm/JIT.html (original)
+++ harmony/standard/site/docs/subcomponents/drlvm/JIT.html Thu Jan 31 09:47:23 2008
@@ -1035,7 +1035,7 @@
<span
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol"><span
style="mso-list: Ignore"><span
- style="FONT: 7pt 'Times New Roman'">�</span></span></span>
+ style="FONT: 7pt 'Times New Roman'"></span></span></span>
The inliner finds further inline candidates, if any, in
the analyzed representation and replicates it in the
representation of the caller.
@@ -2673,7 +2673,7 @@
</p>
<p>
<a id="*" name="*">*</a> Other brands and names are the property of
- their respective owners. �
+ their respective owners.
</p>
</body>
</html>
Modified: harmony/standard/site/xdocs/roadmap.xml
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/roadmap.xml?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/xdocs/roadmap.xml (original)
+++ harmony/standard/site/xdocs/roadmap.xml Thu Jan 31 09:47:23 2008
@@ -488,7 +488,7 @@
</tr>
<tr>
<th>
- IA32 <br>(Pentuim III or better)</br>
+ IA32 <br>(Pentium III or better)</br>
</th>
<td>?</td>
<td>+</td>
Modified: harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html (original)
+++ harmony/standard/site/xdocs/subcomponents/classlibrary/AWT.html Thu Jan 31 09:47:23 2008
@@ -239,7 +239,7 @@
<i>AWT events</i> generated and handled by the AWT framework. All
AWT events are subclasses of the <code>AWTEvent</code> class and
are stored in the AWT event queue represented by
- the <code>EventQueue</code> class.
+ the <code>EventQueue</code> class.
</li>
</ul>
<h3>
@@ -247,7 +247,7 @@
</h3>
<p>
AWT has the <i>event dispatch thread</i> (EDT) at its basis,
- represented by the class <code>java.awt.EventDispatchThread</code>.
+ represented by the class <code>java.awt.EventDispatchThread</code>.
This thread handles all generated types of events by going over the
loop. EDT starts on AWT Toolkit creation and stops
on application termination.
@@ -265,22 +265,22 @@
<li>
Dispatch the AWT event: find the target AWT component for this
event and pass it to this component through
- the <code>java.awt.Dispatcher</code> class.
+ the <code>java.awt.Dispatcher</code> class.
</li>
<li>
Push the AWT event to the event queue represented by
- the <code>java.awt.EventQueue</code> class.
+ the <code>java.awt.EventQueue</code> class.
</li>
<li>
Pop all AWT events from the event queue.
</li>
<li>
Pass the given AWT events to the appropriate AWT component by using
- the <code>java.awt.Component.processXYZEvent()</code> methods.
+ the <code>java.awt.Component.processXYZEvent()</code> methods.
</li>
<li>
Call the appropriate AWT component’s event listeners of
- the <code>EventListener</code> interface. Applications should
+ the <code>EventListener</code> interface. Applications should
implement appropriate listeners' interfaces to react to specific
events.
</li>
@@ -302,8 +302,8 @@
If a non-EDT thread generates an AWT event when EDT is waiting for
a native event, a new native event is required to wake EDT and make
it handle the AWT event. Every time a non-EDT thread adds an event
- to the queue, the method <code>awake()</code> of
- the <code>NativeEventQueue</code> interface is called. This method
+ to the queue, the method <code>awake()</code> of
+ the <code>NativeEventQueue</code> interface is called. This method
produces a native auxiliary event so that EDT becomes ready to
handle AWT events. EDT treats this auxiliary event as <a
href="#Native_Event_classification">invisible</a>.
@@ -422,7 +422,7 @@
<ul>
<li>
Interacting with the underlying native window system, such
- as <code>Win32</code> or <code>X11</code>, by way of handling
+ as <code>Win32</code> or <code>X11</code>, by way of handling
native focus events and making native focus requests
</li>
<li>
@@ -469,11 +469,11 @@
</p>
<ul>
<li>
- The <code>java.awt.FocusDispatcher</code> class handles focus
+ The <code>java.awt.FocusDispatcher</code> class handles focus
events received from the window toolkit level.
</li>
<li>
- Package-private methods of the <code>KeyboardFocusManager</code>
+ Package-private methods of the <code>KeyboardFocusManager</code>
class manage focus on the higher AWT level.
</li>
</ul>
@@ -566,7 +566,7 @@
<p>
The AWT level of the focus subsystem handles focus requests
synchronously on every successful focus change request. When the
- method <code>requestFocus()</code> is called, the keyboard focus
+ method <code>requestFocus()</code> is called, the keyboard focus
manager posts all necessary AWT events in the required order
irrespective of the success or failure of the native focus request. In
other words, the AWT subsystem does not wait until the native focus
@@ -589,12 +589,12 @@
<ul>
<li class="notetext">
When a top-level native window gains focus, the focus goes to a
- child of this window or the <code>Window</code> component itself,
+ child of this window or the <code>Window</code> component itself,
in case no child elements are available.
</li>
<li class="notetext">
When a window in another application gains focus, the focus
- dispatcher calls the <code>setFocus(false)</code> method on the
+ dispatcher calls the <code>setFocus(false)</code> method on the
focus owner to clear the focus owner value.
</li>
</ul>
@@ -621,7 +621,7 @@
focus manager ignores events sent to the window that has failed to
become the focused window because the corresponding AWT event was
dispatched and vetoed.<br />
- When handling the <code>WINDOW_GAINED_FOCUS</code> event, private
+ When handling the <code>WINDOW_GAINED_FOCUS</code> event, private
methods in the keyboard focus manager set focus on the appropriate
child component of the window.
</dd>
@@ -652,29 +652,29 @@
<p>
You can paint standard components in many ways, including drawing the
component parts (text, background, shadows and all other elements) by
- the means of class <code>java.awt.Graphics</code>. Note that the
+ the means of class <code>java.awt.Graphics</code>. Note that the
framework must not paint standard components by the
- method <code>java.awt.Component.paint()</code> because it could be
+ method <code>java.awt.Component.paint()</code> because it could be
overridden. Instead, when processing a painting event, the framework
calls the package-private
- method <code>java.awt.Component.prepaint()</code> just before calling
- the method <code>paint()</code>. The <code>prepaint()</code> method
+ method <code>java.awt.Component.prepaint()</code> just before calling
+ the method <code>paint()</code>. The <code>prepaint()</code> method
does the actual painting for all standard components by delegating the
painting task to the theme. This approach might not seem optimal, but
it works on all supported platforms without any changes.
</p>
<p>
- The <code>org.apache.harmony.awt.Theme</code> class implements the
+ The <code>org.apache.harmony.awt.Theme</code> class implements the
default theme. Methods of this class do the following:
</p>
<ul>
<li>
Paint standard components, for example, the
- method <code>drawButton()</code>.
+ method <code>drawButton()</code>.
</li>
<li>
Calculate the optimal component size for each type of component,
- for example, by using the method <code>calculateButton()</code>.
+ for example, by using the method <code>calculateButton()</code>.
</li>
</ul>
<p>
@@ -689,19 +689,19 @@
<p>
You can create a custom theme that inherits from the default theme and
contains specific features. The current implementation contains
- the <code>WinTheme</code> class that extends the default theme as
+ the <code>WinTheme</code> class that extends the default theme as
shown in Figure 5.
</p>
<p>
To use the native API in your theme, extend the default theme
overriding its painting methods. In the derived theme, you can use the
additional features of specific implementation of
- the <code>Graphics</code> class, and explicitly call native API
- functions via wrappers, see <code>org.apache.harmony.misc</code>
+ the <code>Graphics</code> class, and explicitly call native API
+ functions via wrappers, see <code>org.apache.harmony.misc</code>
package for details. Figure 5 below demonstrates theme-related classes
- hierarchy with methods related to the <code>Button</code> component as
+ hierarchy with methods related to the <code>Button</code> component as
an example. A block of code for extending
- the <code>drawButton()</code> method is shown in <a
+ the <code>drawButton()</code> method is shown in <a
href="#ExampleButton">Example 1</a> below.
</p>
<p style="text-align: center">
@@ -713,7 +713,7 @@
</p>
<p>
After creating a derived theme, turn it on by using the
- property <code>awt.theme</code>. This property contains the name of a
+ property <code>awt.theme</code>. This property contains the name of a
subclass of default theme class used as the theme by all components.
If the property points to a non-existent class or if the required
native library is missing, or any other error occurs, the default
@@ -723,7 +723,7 @@
</p>
<p>
To force the default theme, set the command-line
- option <code>-Dawt.theme=0</code>. As long as zero is an invalid class
+ option <code>-Dawt.theme=0</code>. As long as zero is an invalid class
name, this does the job.
</p>
<p class="backtotop">
@@ -739,17 +739,17 @@
and the contained text. Because not all these attributes are visible
through the public API, the DRL AWT module provides a set of
interfaces to allow the theme to access private and public data. The
- package <code>org.apache.harmony.awt.state</code> contains these
+ package <code>org.apache.harmony.awt.state</code> contains these
interfaces, such
- as, <code>TextState</code>, <code>CheckboxState</code>,
- and <code>ButtonState</code>. Each standard component class has an
+ as, <code>TextState</code>, <code>CheckboxState</code>,
+ and <code>ButtonState</code>. Each standard component class has an
inner class that implements the appropriate interface and has the
state field of that class declared.
- The <code>java.awt.Component</code> class stores all functionality
+ The <code>java.awt.Component</code> class stores all functionality
common for all types of standard components. Specifically,
- the <code>java.awt.Component</code> class has an inner
- class <code>ComponentState</code> that implements
- the <code>org.apache.harmony.awt.state.State</code> interface. This
+ the <code>java.awt.Component</code> class has an inner
+ class <code>ComponentState</code> that implements
+ the <code>org.apache.harmony.awt.state.State</code> interface. This
inner class enables implementing the state of a specific component by
overriding only a few methods.
</p>
@@ -760,8 +760,8 @@
</p>
<p>
Platform-specific and component-specific code is concentrated in
- separate helper classes, such as <code>DefaultButton</code>, the
- helper to the default theme, and <code>WinCheckbox</code>, the helper
+ separate helper classes, such as <code>DefaultButton</code>, the
+ helper to the default theme, and <code>WinCheckbox</code>, the helper
to the Windows<a href="#*">*</a> theme. The theme class contains only
simple methods.
</p>
@@ -769,7 +769,7 @@
<a id="ExampleButton" name="ExampleButton"></a>Example 1
</p>
<p class="exampletext">
- This is an example with the <code>Button</code> component.
+ This is an example with the <code>Button</code> component.
</p>
<pre class="exampletext">
public void drawButton(Graphics g, ButtonState s) {
@@ -791,8 +791,8 @@
Figure 6 shows an example of component classes relation, inner states
and the inheritance hierarchy of component state interfaces. The
figure contains short names for convenience, for example,
- <code>Component</code> actually means
- <code>java.awt.Component</code>.
+ <code>Component</code> actually means
+ <code>java.awt.Component</code>.
</p>
<p style="text-align: center">
<img alt="Methods and classes related to state change operations"
@@ -811,11 +811,11 @@
</h3>
<p>
This section illustrates how the state interfaces are used in
- the <code>Button</code> component. In DRL AWT, all standard components
+ the <code>Button</code> component. In DRL AWT, all standard components
follow the same model.
</p>
<p>
- This is a part of the <code>java.awt.Button</code> code that
+ This is a part of the <code>java.awt.Button</code> code that
illustrates how to use visual themes in standard components.
</p>
<pre>
@@ -827,7 +827,7 @@
}
</pre>
<p>
- The framework calls the <code>prepaint()</code> method, which paints
+ The framework calls the <code>prepaint()</code> method, which paints
standard components. The painting itself is done by the theme class,
and all the information it requires is contained in the state
variable.
@@ -838,14 +838,14 @@
</h3>
<p>
In DRL, the Windows<a href="#*">*</a> theme is implemented by the
- class <code>org.apache.harmony.awt.theme.windows.WinTheme</code>,
+ class <code>org.apache.harmony.awt.theme.windows.WinTheme</code>,
which inherits from the
- class <code>org.apache.harmony.awt.Theme</code>.
+ class <code>org.apache.harmony.awt.Theme</code>.
</p>
<p>
- The <code>WinTheme</code> class paints components using the Windows<a
- href="#*">*</a> API function <code>DrawFrameControl()</code> in the
- classic mode and <code>DrawThemeBackground()</code> in the XP mode,
+ The <code>WinTheme</code> class paints components using the Windows<a
+ href="#*">*</a> API function <code>DrawFrameControl()</code> in the
+ classic mode and <code>DrawThemeBackground()</code> in the XP mode,
and basic Windows<a href="#*">*</a> API painting functions.
</p>
<p>
@@ -853,26 +853,26 @@
</p>
<ul>
<li>
- The class <code>org.apache.harmony.awt.gl.WinThemeGraphics</code>
+ The class <code>org.apache.harmony.awt.gl.WinThemeGraphics</code>
has a set of native methods that call the Windows<a href="#*">*</a>
API. This class is tightly coupled
- with <code>org.apache.harmony.awt.gl.WinGDIPGraphics2D</code>,
- which is an implementation of <code>java.awt.Graphics</code>.
- The <code>WinThemeGraphics</code> class
- queries <code>WinGDIPGraphics2D</code> for the current clip,
+ with <code>org.apache.harmony.awt.gl.WinGDIPGraphics2D</code>,
+ which is an implementation of <code>java.awt.Graphics</code>.
+ The <code>WinThemeGraphics</code> class
+ queries <code>WinGDIPGraphics2D</code> for the current clip,
translation and device context.
</li>
<li>
The
- class <code>org.apache.harmony.awt.wtk.windows.WinEventQueue.ThemeMap</code>
+ class <code>org.apache.harmony.awt.wtk.windows.WinEventQueue.ThemeMap</code>
that handles theme-related native events and opens and closes
handles of native theme data when needed.
</li>
<li>
The set of helper
- classes <code>org.apache.harmony.awt.wtk.theme.windows</code>
+ classes <code>org.apache.harmony.awt.wtk.theme.windows</code>
responsible for specific types of components, for
- example, <code>org.apache.harmony.awt.wtk.theme.windows.WinButton</code>.
+ example, <code>org.apache.harmony.awt.wtk.theme.windows.WinButton</code>.
</li>
</ul>
<p class="note">
@@ -915,8 +915,8 @@
<p>
For example, if a thread adds a component to a list of child
components for a container without updating this component’s
- field <code>parent</code>, another thread working with the same
- component gets the wrong value of the <code>parent</code> field.
+ field <code>parent</code>, another thread working with the same
+ component gets the wrong value of the <code>parent</code> field.
Moreover, the second thread may remove this component from the
container children list, which makes the behavior of the first thread
unpredictable. Synchronization helps avoid such problems.
@@ -930,7 +930,7 @@
implementation uses a special monitor <em>AWT lock</em> more powerful
than built-in Java<a href="#*">*</a> synchronized blocks and methods.
The AWT lock is similar to the synchronization tools provided by
- the <code>java.util.concurrent</code> package. The synchronized
+ the <code>java.util.concurrent</code> package. The synchronized
section using the AWT lock has its own specifics, as demonstrated by
the example below.
</p>
@@ -939,9 +939,9 @@
</p>
<p class="exampletext">
This example provides an excerpt of code from
- the <code>Component</code> class demonstrating a typical synchronized
- section in the AWT code. The methods <code>lockAWT()</code>
- and <code>unlockAWT()</code> are the boundaries of the critical
+ the <code>Component</code> class demonstrating a typical synchronized
+ section in the AWT code. The methods <code>lockAWT()</code>
+ and <code>unlockAWT()</code> are the boundaries of the critical
section. The code between them is synchronized by the AWT lock.
</p>
<pre>
@@ -961,7 +961,7 @@
</pre>
<p>
From the syntactical standpoint, this is a try-finally structure,
- which guarantees that the <code>unlockAWT()</code> method is always
+ which guarantees that the <code>unlockAWT()</code> method is always
called after doing the useful work in the body of try block.
Logically, it is used as an ordinary synchronized block, except when
using AWT lock extended functionality.
@@ -982,24 +982,24 @@
</p>
<ul>
<li>
- Components, such as <code>Component</code>, <code>Button</code>,
- and <code>Frame</code>
+ Components, such as <code>Component</code>, <code>Button</code>,
+ and <code>Frame</code>
</li>
<li>
- Layout managers, such as <code>FlowLayout</code>
- and <code>GridBagLayout</code>
+ Layout managers, such as <code>FlowLayout</code>
+ and <code>GridBagLayout</code>
</li>
<li>
- Auxiliary, such as <code>Toolkit</code>
- and <code>KeyboardFocusManager</code>
+ Auxiliary, such as <code>Toolkit</code>
+ and <code>KeyboardFocusManager</code>
</li>
</ul>
<p>
The total number of synchronized classes nears 40.
</p>
<p>
- Simple data structures, for example, <code>Rectangle</code>
- or <code>Point</code>, are not protected from concurrent modifications
+ Simple data structures, for example, <code>Rectangle</code>
+ or <code>Point</code>, are not protected from concurrent modifications
for performance reasons.
</p>
<dl>
@@ -1013,7 +1013,7 @@
synchronized by the AWT lock. Package-private methods and private
method are not, with only a few <a
href="#SyncExceptions">exceptions</a>. For an example, see
- the <code>java.awt.Toolkit</code> class.
+ the <code>java.awt.Toolkit</code> class.
</li>
<li>
A synchronized section of code must not call user code, such as
@@ -1032,12 +1032,12 @@
<li>
Certain methods might get overridden by user code, but are called
under the AWT lock, for example, the
- method <code>addNotify()</code> in the <code>Component</code>
- and <code>Container</code> classes.
+ method <code>addNotify()</code> in the <code>Component</code>
+ and <code>Container</code> classes.
</li>
<li>
Platform-specific code of
- the <code>org.apache.harmony.awt.wtk</code> package must not use
+ the <code>org.apache.harmony.awt.wtk</code> package must not use
the AWT lock explicitly.
</li>
</ul>
Modified: harmony/standard/site/xdocs/subcomponents/classlibrary/DNSsupport.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/classlibrary/DNSsupport.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/classlibrary/DNSsupport.html (original)
+++ harmony/standard/site/xdocs/subcomponents/classlibrary/DNSsupport.html Thu Jan 31 09:47:23 2008
@@ -79,7 +79,7 @@
Alexei Zakharov, Nadya Morozova: document created.
</td>
<td class="TableCell">
- March 23, 2006
+ March 23, 2006
</td>
</tr>
<tr>
@@ -90,7 +90,7 @@
Nadya Morozova
</td>
<td class="TableCell">
- September 21, 2006
+ September 21, 2006
</td>
</tr>
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/EM.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/EM.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/EM.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/EM.html Thu Jan 31 09:47:23 2008
@@ -242,13 +242,13 @@
<p>
The VM core component sends requests to EM to execute methods. VM
passes a method handle and parameters to the execution manager through
- the <code><a href="#EM_VM">EM_VM</a></code> interface. EM selects the
+ the <code><a href="#EM_VM">EM_VM</a></code> interface. EM selects the
engine for compiling the method and sends a compilation request to VM
to compile the method with the selected engine.
</p>
<p>
Instantiating and configuring JIT compilers goes through
- the <code>JIT_EM</code> interface [<a href="#DRLDevGuide">3</a>]. In
+ the <code>JIT_EM</code> interface [<a href="#DRLDevGuide">3</a>]. In
its turn, the execution manager exports the <code>EM_JIT</code>
interface for accessing method profiles and profile collectors.
Specifically, the <a href="#EM_JIT">EM_JIT</a> interface consists of
@@ -336,7 +336,7 @@
<a id="EM_PC" name="EM_PC"></a>EM_PC Interface
</h3>
<p>
- The <code>EM_PC</code> interface handles interaction between the
+ The <code>EM_PC</code> interface handles interaction between the
execution manager and the profile collectors and consists of the
following function groups:
</p>
Modified: harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html
URL: http://svn.apache.org/viewvc/harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html?rev=617171&r1=617170&r2=617171&view=diff
==============================================================================
--- harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html (original)
+++ harmony/standard/site/xdocs/subcomponents/drlvm/Jitrino.html Thu Jan 31 09:47:23 2008
@@ -841,7 +841,7 @@
<span
style="FONT-SIZE: 10pt; FONT-FAMILY: Symbol"><span
style="mso-list: Ignore"><span
- style="FONT: 7pt 'Times New Roman'"> </span></span></span>
+ style="FONT: 7pt 'Times New Roman'"></span></span></span>
The inliner finds further inline candidates, if any, in
the analyzed representation and replicates it in the
representation of the caller.
@@ -2479,7 +2479,7 @@
</p>
<p>
<a id="*" name="*">*</a> Other brands and names are the property of
- their respective owners.
+ their respective owners.
</p>
</body>
</html>