|
Choose either Java or Flash output here. Check the advanced options for
enhanced features such as Flash compression and floating layers. Simply
paste the Generated HTML code into your web page and copy the content
of the Build Folder to your server.
This is where you decide
how and where to build the menu applet - by default this folder is named
the same as your project and located in the _MenuFX_Output
folder.
Getting your applet up and running on the Internet is easy.
Just follow these simple steps:
- Enter the folder where you want to build the applet.
- Press the Build Menu button.
- Upload ALL the files in the Build Folder
to your web server.
Use <applet> Tag:
Automatically converts the generated code to use the applet tag
according to HTML Specs. (Deprecated in HTML 4.0 Specifications.)
Use <object> Tag:
Automatically converts the generated code to use the object tag
according to HTML Specs. (Used in place of applet tag in HTML 4.0 Specifications.)
Note: Even though
the <applet> is depreciated in 4.0 specification it is still currently
supported by all browsers. We note that some users have had issues with
Javascript->Java coding when using <object> tags. We recommend
thta you use the <applet> tag to maximize compatibility.
Include Content in Archive:
Specifies whether to include content used by the applet in a compressed
archive file. 1 Cool Menu FX Tool builds two archive files; a Cabinet
(.cab) file for use by Internet Explorer, and a Java Archive (.jar) for
use by Netscape 4. (Netscape 3 and earlier does not support compressed
archive files).
If this option is checked, the archive files will be called
projectname.cab and projectname.jar respectively. If this option is not
checked, only the menu_fx_*.class file will be included in the archives,
and the archive files will be called menu_fx.cab and menu_fx.jar.
The advantage of using an archive is that the applet and
all its content will be downloaded in a single HTTP transaction, which
considerably improves the download time for content-heavy applets. In
addition, when GIF animation's are restarted, the animation is reloaded
from the archive, rather than the server, which would otherwise be the
case.
However, applets which use an archive will take longer to
start running because the entire archive must be downloaded before the
applet can start. Also, if you are running many button applets on the
same page (or different pages at the same site), it can be more efficient
to not use archives. This is because the common archive file (menu_fx.cab/menu_fx.jar)
can be shared by multiple applets, and will be downloaded once only.
Note 1: You
can only create JAR files if your system has the Java Virtual Machine
(JVM) installed. If you do not have the latest JVM, no JAR files will
be created. See the FAQ for help on upgrading your JVM.
Note 2: The .cab and .jar files
serve the same purpose as the menu_fx.class file. If the .cab and .jar
files are not uploaded to your web server, the button applet may not run.
Where should the applet load files
from?
This tells the applet where to look for certain file types when it is
running on the web-server. In all four cases you should specify a path
relative to the HTML file that contains the <applet> or <object>
HTML. The default folder is ".", or the same folder as the HTML
file.
Examples:
The parent folder = ".."
JavaClasses sub-directory = "../JavaClasses"
Note: Absolute paths beginning with
a slash, or even http://, will be accepted, however we recommend you use
relative paths.
Put the menu in its own floating layer:
When check this will create the HTML code required to display the applet
in its own floating layer. The menu will appear to display over the top
of your HTML contents and follow the user as they scroll down the page.
Note: Floating layers are only support by Internet Explorer. Other browsers
will display the menu but it will not follow the user as they scroll down
the page.
| Test
in Selected browser:
|
Runs the finished applet file in your default browser. The
Test in selected broswer button rebuilds the applet before running it.
Note: You should close the browser after testing
the applet because some browsers cache the applet in memory. This means
that the next time you test the applet it will appear not to have changed.
Shift-Reload on Netscape Navigator 3 (or later) will force the applet
to be reloaded. Control-Refresh on Internet Explorer 4 (or later) will
force the applet to be reloaded.
Copies all the files necessary for running the menu applet
into the Build Folder.
The Build Folder contains the following files:
| All images and sound used |
Any .gif, .jpg and.au files you have used
in your project. |
| menu_fx.cab |
Compressed class file - used for Microsoft
browsers (If you have selected to include content in archive,
this will also contain all of your graphics and sounds) |
| menu_fx.class |
Uncompressed Player - used only in older
browsers |
| menu_fx.jar |
Compressed class file - used for Netscape
browsers (If you have selected to include content in archive,
this will also contain all of your graphics and sounds) |
| projectname.bak |
Backup of the project file - by keeping
this on the live server many people have been saved a re-build when
their PC fails. |
| projectnameMap.jpg |
Automatically generated imagemap - used
when people do not have a java-enabled browser (extremely rare these
days) |
| projectname.html |
The HTML page used in when you Test in
Browser - only displays the applet |
If you are using non-standard Java font you will have associated
class files for those fonts.
At a minimum you need to put all the BtnPlayer files (class,
cab and jar) and all of the images and sounds used in your java project
on the live server in order for project to work.
After the applet has been built you will able to click on
the Build Folder link - this will open the folder inside Windows
explorer. You will need to upload ALL the files in this folder to your
web server. Nothing further is necessary for the applet to run.
Note:
Be aware that applets made with the unregistered version of 1 Cool Menu
FX Tool will display a large UNREGISTERED message when they are
run over the Internet.
This is the HTML code that describes the menu project.
The Java program reads this information, decodes it, and "plays"
the button project inside the browser. A single menu_fx.class, .jar or
.cab file may be shared by many menu applets. Everything necessary to
describe the button project is in the HTML code, not in the BtnPlayer.class
file.
This specifies the folder on your local hard drive
where the applet will be built. This folder is known as the Build Folder.
It defaults to a folder with the same name as your project located
in the _MenuFX_Output folder which is located in the
1 Cool Menu FX Tool folder.
The Build Folder contains the following files:
| All images and sound used |
Any .gif, .jpg and.au files you have used
in your project. |
| menu_fx.cab |
Compressed class file - used for Microsoft
browsers (If you have selected to include content in archive,
this will also contain all of your graphics and sounds) |
| menu_fx.class |
Uncompressed Player - used only in older
browsers |
| menu_fx.jar |
Compressed class file - used for Netscape
browsers (If you have selected to include content in archive,
this will also contain all of your graphics and sounds) |
| projectname.bak |
Backup of the project file - by keeping
this on the live server many people have been saved a re-build when
their PC fails. |
| projectnameMap.jpg |
Automatically generated imagemap - used
when people do not have a java-enabled browser (extremely rare these
days) |
| projectname.html |
The HTML page used in when you Test in
Browser - only displays the applet |
If you are using non-standard Java font you will have associated
class files for those fonts.
At a minimum you need to put all the BtnPlayer files (class,
cab and jar) and all of the images and sounds used in your java project
on the live server in order for project to work.
After the applet has been built you will able to click on
the Build Folder link - this will open the folder inside Windows
explorer. You will need to upload ALL the files in this folder to your
web server. Nothing further is necessary for the applet to run.
Note:
Be aware that applets made with the unregistered version of 1 Cool Menu
FX Tool will display a large UNREGISTERED message when they are
run over the Internet.
| Automatically
Replace HTML code:
|
If this option is checked 1 Cool Menu
FX Tool will replace the assocated HTML in the specified file(s), every
time you build the menu. This option is very handy if your menu is embedded
in an existing page, and you want to make changes to your menu without
having to copy/paste HTML code.
Note: If HTML tags matching the current
button menu cannot be found, an error message will be displayed and no
HTML code will be replaced. If this occurs, please use the copy to clipboard
button method for inserting your code.
|
