Release Notes: Java WorkShop(tm)
Release: 1.0 - August 1996
CONTENTS:
- General Information About Release 1.0
- Limitations
Please use the Help => Send Comments dialog box to send suggestions
or comments about this release to the development team.
Your comments will be read by the development team, but
due to the large number of comments, the development team is
unable to reply to each comment individually.
1. General Information About Release 1.0
Online Help Updates
Updates to the online help will be posted on the Java
WorkShop website as they are completed. You can check this
URL periodically to see if new documentation has been
added:
http://www.sun.com/developer-products/java/help
Other Sources of Technical Information
The Java WorkShop website contains a number of sources of
technical information about the product. See the
main Java WorkShop page and follow links in the See Also
area for support information and links to other technical
information:
http://www.sun.com/developer-products/java
Distribution of Visual Java Runtime Classes
Click here to view the list
of Visual Java runtime classes you can reproduce and distribute with your applications. See the online license agreement for
legal obligations.
Startup on Solaris Systems
- By default, the maximum available memory for Java is
set to 16 Mbytes. You can increase this value when you
start the WorkShop by using the
-mx
option.
For example, use the following command to set maximum
memory to 32 Mbytes:
% jws -mx32M
- The startup script depends on the
/bin/uname
utility. Make sure that it is in
the execute path ahead of any other utilities named
uname
when you start the WorkShop.
- If the Java WorkShop menus have poor contrast between
foreground and background color, such as black text on a
black background, change the foreground color. The
following example changes the foreground color to white.
(Use a different color if your background color is white.)
- Add the following line to your ~/.Xdefaults file:
AWTapp*foreground: white
- Run the command:
% xrdb -merge ~/.Xdefaults
- Restart the Java WorkShop.
2. Limitations
General
- Java WorkShop does not properly process files or
directories with space characters in their names. Do not
insert space characters in the names of directories or files.
- On Solaris systems, the WorkShop occasionally (but rarely)
dumps core (SIGSEV) during startup. If this occurs, simply
restart the WorkShop.
- When you click on "Set Proxy..." in the Registration window, the Options dialog box opens and the Java WorkShop browser fronts, covering the Registration window. Look for the Registration window behind the browser. Or, in Windows 95, click on the Taskbar button to front the Registration window.
- On Windows 95/NT systems, browser window positions are not
remembered between sessions.
The WorkShop Browser
- In this release the browser supports only basic HTML 2.0
(except Forms) and two minor extensions, the
<
center
> and <nobr
>
tags. This limitation means that the WorkShop browser will
not properly display HTML pages that contain tables, forms, and
frames, including pages from the Java WorkShop website.
- Text is sometimes repainted incorrectly and the page
appears blank. You can often fix this problem by
refreshing the display, resizing the window, or scrolling
the page.
- In some cases the browser does not display list
bullets and numbers. This occurs most often in nested lists
(lists within lists).
- The browser does not support printing of HTML
pages or source pages.
- On Windows NT systems, extra screen repaints are done if you
resize the browser when one of the WorkShop tools is
loaded.
- In some cases when a horizontal scrollbar is added to
the browser, the bottom arrow in the vertical
scrollbar does not appear. If this occurs, resize the
browser window to make the arrow appear.
- On Windows 95/NT systems, the background color of HTML
pages may be rendered incorrectly.
Debugger
- On rare occasions the Debugger may lose connection to
the program you are debugging. The typical symptom is that
the Debugger does not respond to user actions. For
example, in the Threads/Stack tab, clicking on a thread
group does not expand the group. In this case, click the
Restart button to restart the Debugger.
- If you click on the Step Into or Step Over controls in
rapid succession, you may lose the green highlight in the
Source Editor. This highlight indicates where program
execution stopped. To regain the highlight, click on the
Show Source button in the Threads/Stack tab or try stepping
again.
- If the program you are debugging is stopped at a
breakpoint and you choose Minimize All from the Windows 95
Taskbar, you will not be able to deiconify the windows by
clicking on their icons. To deiconify a window, use
Alt-Tab.
- If, during a debugging session, you change the source
path in the Debug/Browse tab in the Project Manager, the
new path will not take immediate effect. You may see the
message "No source for classname, set project's
source path." To make the debugger recognize the source
path, open the Source Editor and load a file in that source
path. Use the Toggle Breakpoint control to set and remove
a breakpoint. The debugger now recognizes the path.
- In the Classes tab, if you select a method and then
click the Show Source button, the WorkShop displays the
method's source in the Source Editor. Although the method
may contain breakpoints, they will not be highlighted in
red in the Source Editor. Use the Breakpoints tab to view
the breakpoints.
- On Windows 95, if your the program is stopped at a
breakpoint, any ongoing America Online session stops
running until you resume execution of your program.
Visual Java
- Paths to images set in the attribute editor for image
labels and image buttons should be specified relative to
the codebase. Alternatively, when you run the application from the command line, the image path must be located relative
to one of the paths set in the CLASSPATH.
- If you generate and build an application that contains an
image button or image label with the default image, the image
is not displayed in the built application. The path to the
default image is not correct. See the preceding limitation
for details.
- On Windows 95/NT systems, the background color of components
is not altered when you click Apply in the background dialog.
- If you programmatically set the value of
allowMultipleSelections
to TRUE and then do a
get("selectedItems")
, you are returned the null
string. If only one item is selected it works properly
until more than one item is selected.
- Visual Java behaves unpredictably if you:
- Click on the browser reload button while Visual Java
is loaded
- Clone the browser while Visual Java is loaded
- On Windows 95 systems, when you switch from layout to
preview mode, the preview window is not fronted properly
and may be hidden behind other windows.
- You must either generate or save a layout before you
build it. If you do not generate or save, the layout is
not included in the build.
- If you copy a Visual Java project and give the copy a
different project name, then you must update the project
name in the .gui file. For example, if you copy
a project named Lion into a project called
Tiger, you must edit the file
Tiger.gui. Change
java.lang.String generateClass Lion
to
java.lang.String generateClass Tiger
- On Windows 95/NT systems, you may encounter the follow error message when setting the foreground color of a component:
java.lang.InternalError: getGraphics implemented only for Canvas Components
You can ignore it.
Project Tester
Build Manager
- To determine if a class file is up-to-date or must be
rebuilt, the Build Manager compares the
.java
and .class
files of the same name. Java
source files can contain only one public class and the
class file produced by that public class is the one that
has the same name as the source file. If a Java source file contains private classes that
produce .class
files with names different than
the .java
file, the Build Manager cannot
determine whether or not these classes are up-to-date.
If your source files contain private classes, to ensure
correct compilation, you can use the Build All tool bar
control, or compile a file that you know is out-of-date
individually.
Source Browser
- The Class Browser includes a default constructor even when
a program does not define one.
Online Help
- The online help included with this release covers basic
Visual Java functionality. Help pages that describe
advanced functionality, including examples, will be
available in the future from the Java WorkShop website:
http://www.sun.com/developer-products/java/help
- In some cases the Help browser does not display list
bullets and numbers. This occurs most often in nested lists
(lists within lists).
- Because the WorkShop browser does not yet support the
printing of HTML pages, you must use a different browser
(such as Netscape Navigator) to print help pages. To
determine the URL of a help page:
- Load a help page in the browser.
- Note the URL of the page in the WorkShop URL bar. The
URL consists of the "doc:" protocol, followed by the path
name of the help page (relative to the installation
path). The installation path is the path to the
directory in which you installed the WorkShop.
- You can construct the entire path name of the URL by
prepending the installation path to the relative path name.
Use the "file:" protocol to load the help page in the
Netscape Navigator and print it. For example:
file:/home/bill/work/jws/lib/html/help/build/build.html
Copyright ©
1996 Sun Microsystems, Inc., 2550 Garcia Ave., Mtn. View, CA
94043-1100 USA. All rights reserved.