noware
Purchase noware

what is
noware
applets
menu
and
preview
be a
noware
developer
custom
noware
applets
download
noware
purchase
noware
return to
noware

noware faq
&
java@noware


This FAQ answers the following questions:


Section One

Where is the .exe file after extracting the archive? How do I run the activator?

Problem - after extracting the activator archive, I can see a couple of html files, and a directory called classes, but no .exe file to run. How do I start the activator?
Reason - the activator is written in Java, and as such is loaded directly from a web page. There is no .exe file.
Solution - to run the activator, open the Activator.html file into a java enable browser such as Netscape 2. Then wait a few seconds while it loads. On a slower machine this can take up to 30 seconds.
If after this time you still don't see the Activator floating window appear, try using the ALT-TAB key combination to cycle through all the open Windows programs - sometimes the Activator gets hidden behind other windows.

Applets work on my hard disk, but not on the server

Problem - The applets I customise work when I test them on my hard drive, but don't work from the web server when I upload my html pages.
Reason - The java applets rely the presence of the classes directory. This directory contains all the java code needed to make things work.
Solution - you must upload the classes directory (and all its contents) to your web server as well as your html files.
You only need to upload the classes directory ONCE. If you make small changes to your html files, you only need to re-upload them (you don't have to upload the classes directory again after it has been done once).
This uploading step can often cause problems.
The two most common are as follows:

- failure to get all the classes files onto the server.
There are two guaranteed ways of doing this.

- putting the html files and classes directory in different places compared to where they were on your hard disk.
The easiest way around this problem is to make sure that the positions of the files on the server are exactly the same as they are on your hard disk. For example, if your html files are in the same directory as your classes files, make sure this is the same on the server.
Alternatively, if they are in different directories, you need to change the codebase section of your html file.
When you look at the html code for eg the nervous text applet, you will see something like the following
<applet codebase="./classes", code="infoweb.noware.NervousText.NervousText"width=368 height=100> The codebase tells the browser where to find the classes.
The line "./classes" means "look in the current directory for a directory called classes"
The single dot means current directory. Two dots mean go up one directory (to the parent of this html file). The codebase always starts relative to the html file that containts this codebase text. If you have put your classes directory somewhere else, you can tell the browser where by changing the codebase section, for example
codebase="../javastuff/classes"
This examples says "go to the parent directory of this html file, and there you will find a directory called javastuff, and in the javastuff directory is the classes directory, which is what you want"

Do I need to upload the classes directory for each html file?

Problem - the instructions say I need to put a copy of the classes directory (and all its contents) onto the server for each html file. Is this really necessary? I don't have enough space on my server to waste space!
Answer - No, you DO NOT have to do this for each file. You only need to do it once. For each subsequent HTML file, you simply need to change the codebase information to point to where your single master copy of the classes directory is.
See the question above for more information on setting the codebase tag.

How do I display information to non java browsers?

Problem - I want to show users with old browsers who do not understand java something on screen, rather than nothing as currently happens.
Solution - Any html code you put in between the <applet> and </applet> tags will be ignored by java enabled browsers, and displayed by older browsers.
For example, if you put the following line (with the H2 tags) after the <applet .....> stuff in any of your html files, non java browsers will display the advice message.
<applet ..... etc>
<h2>To see this animation, you need a java enabled browser</h2>
<other applet tags....>
</applet>

Problems unzipping the files when not using Winzip95

Problem - using an older version will result in lots of errors, where it will ask you if you want to overwrite files.
Reason - because the Activator relies on long file names, you must be using the latest version of Winzip to extract the zip file's contents.
Solution - The latest version of winzip can be found at www.winzip.com.
Alternate solution - download the .exe file, which will extract itself automatically when you run it.

Problems using Netscape Navigator Gold and other WYSIWYG editors

Problem - when you paste the Activator's HTML Code into your web page using a WYSIWYG editor, you see the code rather than the applet.
Reason - because WYSIWYG editors assume you want to see on your page exactly the same text as you are copying and pasting, it puts the text on your pages as text, rather than as HTML code.
Solution - if your editor allows you to view the raw HTML source code, do so, and paste the Activator code into your HTML code at the appropriate place.
If your editor does not allow you to view and edit the raw HTML source code, you can still use the activator by doing the following.
Save your file from your editor, and then close the file.
Run a simple text editor like Notepad, and open the file in Notepad.
Scroll through the raw HTML text to the place you want the Activator applet to appear.
Paste in the code that the Activator produced.
Save the file.
Now when you open the file in Netscape (from File menu, Open File), you will see the applet running!

Problems with placing image and sound files

Problem - why do image and sound files have to be within a directory in the classes directory, rather than in the same directory as your html files?
Reason - to allow you to move your files easily from your hard disk to your server, all links have to be relative.
When you run the activator, it uses relative links to access all the files it needs. Thus the code it produces also use relative paths.
However, since your html files and the activator are not in the same directory, the relative paths the activator would have produced would not work with your html files.
To remove this dependency (ie to avoid problems with relative paths being different for the activator and your own html files), all files are placed in a common, known directory. This directory is the classes directory.
So unfortunately, you need to put extra files in a directory in the classes directory, to stop this problem from occurring.

Problems with .au sound files not working.

Problem - recording a sound and saving it as .au format will not work with the activator.
Reason - the most common reason for this is sampling too high. You must sample at 8000 Hz, in either 8 or 16 bit resolution.
Solution - we recommend Cool Edit, and before recording, set it to 8000 rather than the default 44000 sample rate.

How do I use the on-line Activator?

1. Click any "preview" button.
2. Click "use the Activator on-line". Wait for it to load.
3. Choose a java applet from the Activator menu. (A generic demo linked to the menu shows you the basic applet idea.)

4. While you're on-line, you can customize the applet (size, color, speed, etc), using the Activator's point-and-click screens.

5. When you get to the "View, Size or Resize Applet" button, click for an on-line demo of your applet.

6. You can fine-tune your applet as much as you like on-line.


Any other questions? Please mail us at noware@noware.com.au

go to FAQ - Section Two

go to noware


General Enquiries: noware@noware.com.au
Sales Enquiries: noware@sales.com.au
Help/FAQ's: techsupport@noware.com.au
Custom Applets/Third Party: custom@noware.com.au

© 1996 noware
noware is a registered trademark