Java-Help-System generates an
advanced help system for JDK and J2SE docs automatically without
speeding your any time and energy, which even does not occupy hard-disk
Main features of Java-help-system generated
Similar to MS html help contents but with more
features, which displays not only html files, but
also all of text (such as java, policy and xml) files, class files, jar and zip
files (refer to picture 5, 6, 7).
Contain four tables (refer to picture 1 - 4), which offer you the
most convenient environment for using JDK docs.
Java-Help-System accelerates your programming
speed and qualities because you can retrieve java information much easier
The page contains 6 top items (i.e. Online, Document etc), you can add user
top items for advance use.
List-box on the table contains all JDK documents (html files without their
file extensions), you can input a short name to find a class (i.e. Frame), a
tool (i.e. javac) and any info required.
Button Search at top is used for searching files by file extension.
Button Search at bottom is used for searching documents by short name.
You can add a topic currently displayed as favorite topic and re-display it
Besides html files, the help system can display class, jar, zip and all text
class file is displayed with its scope code.
jar and zip files
They are extracted in memory and displayed as their compressed structures.
All text files are displayed in plain format (similar to notepad)
Java-Help-System is protected by copyright law and international treaties.
The software is free based on one of following three conditions.
You are an end user
Download the software directly from this site.
Or use the software distributed by us or authorized organizations.
If you are a school, university or any kind of education organizations,
you can copy and distribute the software as a whole inside the
organization, to your students, teachers and staffs, but the
distribution must be for free.
Please feel free to announcer the software to your customers, but please
use our download link directly.
In any other cases, this program, any files, images or any parts of this
program can not be copied, reproduced in any form or by any means if without
prior written permission from us.
If you accept the agreement, you can download it now.
With the new Java-Help-System standard edition, Java programmers can now use online
help that rivals traditional help systems on other platform of Windows. Aimed at
Java developers and technical writers, creating effective JavaHelp provides a
very concise guide to you.
The help system provides hyperlinks and browsing capabilities, does a good
job at orienting the reader to JavaHelp and how it relates to these
documentations. It also includes a short, useful section on project planning for
online help. It shows how the JavaHelp standard uses HTML, jar, zip and other
files to structure content layout (for such options as navigation and the table
of contents; help content itself is organized into HTML pages). Creating
Effective JavaHelp works through a sample help system from Sun and shows you how
to create a simple, custom help system to illustrate these concepts, the Help System ventures into a discussion of the JavaHelp
APIs, which allow a program to call up context-sensitive help at run-time. Other
sections show how to take advantage of more advanced help features, like using
secondary windows to display content or using embedded help within custom
abilities. The Help System ends with reference material on relevant tags, plus
the JavaHelp API itself.
Chances are JavaHelp won't change the way you create help systems. (As the
Help System notes, third party tools will actually let you deploy help systems
to JavaHelp automatically.) But this compact text points out the differences and
advantages of JavaHelp for creating online help on the Java platform. Whether
you are a technical writer, developer, or project manager, you'll want a
software of JavaHelp to see the future of online help for the next
generation of Java applications.
Effective, instantly available online help is a requirement for today's
interactive applications. Until now, Java application developers have been
forced to develop their own help system. That's no longer necessary. With the
release of JavaHelp™, there is a complete and standard online help system for
the Java™ platform.
The help covers the main features and options of JavaHelp. It shows how to
create a basic JavaHelp system, prepare help topics, and deploy the help system
in an application. Written for all levels of Java developers and technical
writers, the Help System takes a chapter-by-chapter approach to building
concepts. It imparts a complete understanding of how to create usable JavaHelp
systems and integrate them into Java applications and applets.
We continues to roll out as fast as you can use. The new Help System,
currently in beta testing, includes components, applications, desktops, and HTML
pages. (That's a big target.) The Java Help documentation envisions a
Java-Help-System written purely for JDK. That means you can embed items within
it or transport to another destination.
The primary component of the Java-Help-System seen by a user is the he lp
viewer, which comprises a toolbar, content pane, and navigation pane. (Java Help
relies heavily on swing user-interface components.) The contents of the help
viewer ought to be familiar to anyone who has interacted with a help system. The
conte nt pane displays help topics. The navigation pane is a tabbed pane that
lets a user select from among the table of contents, index, and text search
Java Help permits a single help system to support varying "navigational
views" of help content. The navigational view is a description of how a
particular kind of content is to be viewed. In that sense, it is metadata --
data about data. For example, a navigational view is defined by (among other
things) its format (how it is to be shown) and data that identifies the format
and location of the view. A navigational view is implemented by a Help
Navigator, which is a subclass of the JHelpNavigator class (a swing component).
The Java-Help-System already understands several n navigational views. The
table of contents, index, and search information (displayed in the help viewer)
already have navigational views defined. Java Help provides mechanisms for
registering new navigational views. Consequently, the diversity of data
permitted, and the means by which the data is viewed, is limited only by
The data structure that carries all the information needed to provide a view
into a help system is bundled into a help file. Note that there are two
"loose" terms at use here. First, a Help file isn't necessarily a
file, in the same sense as files that you store on your hard disk. A help file
could be bound into an application, for example. Second, it's probably more
accurate to say that the information is rooted in the help file. The structure
of a help is Extensible Markup Language data. The data points to the URLs from
which you can find the info necessary to build the help system.
Here's an example. One portion of the help file points to yet another
structure called the Map file. A Map file is a series of "key = value"
pairs. Each key is a help topic (i.e., an entry from the table of contents), and
the value is the URL of another file that stores the actual content that the
system will display when the user selects a table-of-contents item.
The help browser has a storage facility on your hard drive that stores
graphics and text from web sites that you visit. This storage facility is called
the cache using very little memory, or temporary internet files. The reason web
browsers have a cache is that it is quicker and easier to load images, applets,
etc. from cache on your hard drive than downloading them again. Over time, your
browser's cache gets full and the information gets outdated. This can cause
problems with Java applets and can result in that Applets are freezing or not
working at all. The solution to this is to clear cache and reload the page. If
this does not work, try clearing your cache, closing your browser and then
revisiting the page.
The upshot is that the data structures used by a Java-Help-System are
flexible enough to permit a wide variety of delivery scenarios: Help can be
bundled into an application, help can be a separate file outside the
application, help can be pulled in from across the network, and so on. The
architecture is initially daunting, but it looks as if it will serve the broad
(and ever-broadening) needs of Java applications and applets.