Now we have our project file and class template. We need to add some common TINI packages so that we can use their classes. Do that using 'import'. Add these lines of code below our 'package' statement but before our class definition.

import com.dalsemi.comm.*;
import com.dalsemi.system.*;
import com.dalsemi.jellybeans.*;

Also we need to add something for the program to do. To make it a little more interesting, we'll add the action as part of our new class:

// our default constructor
public hello_world()
{
}

// a method we are adding
static void PrintHello () throws Exception
{
System.out.println("Hello World from TINI");
}

And we need to invoke this method from within the main() method of our class, so add this code below the instantiation of hello_world:

hello_world hello_world1 = new hello_world();

try
{
System.out.println("My First Program Starting");
hello_world1.PrintHello();
System.out.println("Normal Exit");
}
catch (Throwable e)
{
System.out.println("Exception");
System.out.println(e);
}

Now we're ready to build. In the main JBuilder toolbar, click Project->Make project. If you have no typos you'll see a "Build Succeeded" message at the bottom of the JBuilder frame.

Here's a link to the complete hello_world.java file in case you want a copy of the source code as it exists on my PC.

So far we haven't used anything unique to TINI in our hello_world class, so we should be able to execute it on the PC. This is one of Java's nice features. Within limits, you can run the same code on any Java-enabled platform.

Let's try it. On the main JBuilder toolbar, click Run, and a 'runtime properties' dialog will open. JBuilder wants to know what we want to run (it won't make the obvious assumption that since our project has only one class it might be that class...).

So here are the messages from our program:

"My First Program Starting" from the main() method.

"Hello World from TINI" from our call of the PrintHello() method.

"Normal Exit" from the main method.

So far so good.

Now that we know it works, let's run it on TINI.

First we need to create the special hello.tini file which TINI can execute. This is a special class file which TINI's JVM can process.

In the project pane, right click on "hello.jpr", and select "Add to Project", then "Add File", a dialog box opens. Browse to the location of our hello_world class file, and type in the filename hello.tini.

Note that the .tini file does not need the same name as our .class file, and it does need to be in the same folder as the .class file, I just find it convenient to keep it there. One caution: the Dallas conversion utility operates starting with the first class file it finds in a folder, without regard to that file's name or whether it is in the project you are intending to convert. So don't mix class files from different projects in the same folder - it will result in unreliable conversions.

Click Open.

In the Host tab, set your TINI's IP address, click OK. Note: this IP address is the public TINI here at Systronix. If you don't have a TINI of your own yet and are desperate to try one, go ahead and access ours. Otherwise, be sure you enter your TINI IP address, not ours!

If several people try to use our TINI for the tutorial at the same time, I'm not sure what may happen...

Now TiniTools is set up for this project and it knows how and where to create the hello.tini file. There are two ways we can create the hello.tini file:

1. Rebuild the project. Since the TiniTools "automatically convert after build" option is checked, along with auto ftp upload, both these actions will occur every time the project is rebuilt.
2. Convert and upload manually. If you right click on the file hello.tini in the JBuilder project pane, you will get a popup list with options "TINI Convert" and "ftp put".

Let's do the manual conversion this time. Right click on hello.tini, then click on TINI Convert.

1. At this time (April 20, 2000) there is a bug in TiniTools telnet which prevents the automatic login from working properly more than once per JBuilder session. Therefore it's better to leave the Telnet automatic options off.
2. TiniTools should automatically convert and ftp only if the JBuilder compile was error-free. It doesn't work that way at the moment. Therefore you need to be sure you check that there were no errors in the JBuilder build (check the JBuilder message pane). Don't assume just because your program converted and ftp'ed that all is well.
3. The telnet window pane doesn't always scale or center itself properly, automatically. You may need to resize the pane in JBuilder to see the full telnet output from TINI.

Since we turned off the TiniTools automatic telnet connection and login, we need to do that manually. Double click on the hello.tini file in the JBuilder project pane. A new "hello.tini" tab should be created in the JBuilder source pane. This is the window into the telnet connection between JBuilder and your TINI.

Click on the Connect button. You may need to hit the enter key and/or resize your telnet pane to see the TINI login prompt. You should see the RX and TX lights on your tini flash briefly with every keystroke while your telnet connection is active.

You're connected to "slush", the TINI command shell.

You will be logged into TINI's root folder. Type "ls -l" for a detailed listing. You should see hello.tini in the root folder.

Note: these screen captures were taken using the Systronix public TINI system which has other files installed and was also running TiniHttpServer.

We're ready to execute hello.tini on TINI!

At your telnet slush prompt, type:

java hello.tini &

This invokes the TINI java interpreter on our sample program. The ampersand (&) tells TINI to execute this program as a thread. This lets us still use slush commands and kill our process if a bug sends our program into an endless loop. Otherwise we'd have to reset TINI and reboot.

Enter the command line above followed by the enter key, and after a brief pause you should see output similar to this:

The TiniTools 'convert' and 'ftp put' commands are grayed out when they are active. For example I have auto convert and auto ftp enabled. If I do a build, it starts the convert and ftp which takes 10-15 seconds. During that time the convert and ftp put items are grayed out because they are already running. See th e image below.

They can also gray out if TiniTools can't connect to TINI. Unplug your ethernet or power off TINI. Start an ftp put and the commands will be grayed out forever or until the ftp connection times out and fails.

If the properties popup is open and the TiniTools options are grayed out, they will stay that way even after the cause of the grayness-causing condition is resolved. The popup doesn't refresh itself. You have to close the popup and open properties again to see if the commands are available.