[Netscape users may need to option click to keep these from opening at text files.]
Installing TINA.
The basic application can be downloaded here here. -- This is a single binhex of the application. Macintosh versions of the house and calibration set (bsteel) are included in the *.hqx archive. For this release. These are the only things that are tested. The readme is the same as the Unix version. Since the scripting is not complete a few extra steps are needed.
While we try and keep the distribution Mac friendly, Data sets downloaded from the NiAC site are stored in a Unix format. These must be converted to Macintosh format for the program to parse the file correctly. This is most necessary for the *.cam calibration files. A number of hangs or crashes is due to this minor detail. Where this conversion is not possible is in the .AIFF files.(Avru image file format predates the more recent audio files.) -- Care must be used when converting to insure that extra (CR) 0x0D values are not inserted into the data and the (LF) 0x0A stripped.
Open the tinatool.cls file for the demo. This is a bit cryptic. It will however tell you what buttons to press.
Several of these are for choice or checkboxes. The first number is the button, choice or check. The second is xxx
is used internally. For checkboxes convert the number to hexidecimal this is (xxx)
For text entry ignore the ____ padding.
At the end are window positions. These will have to be moved with the mouse. Now follow the instructions in the Readme. The resulting data will be output to the main tool's window. The text is selectable, copy is not implemented at this time. This is a high priority. There are some cosmetic bugs that cause extra graphics to be drawn into incorrect windows. Only the two demos have been tested. As the TINA redraw procedure is called on window updates. It is best to make sure the window is not covered.
For the truly adventures The Macintosh interface to TINA is available as source code. It can be downloaded here.
Compiling and installing the program requires a professional development system such as Code Warrior Pro. Tina comes from NiAC as a Tar gziped file. You will need utilities to decompress it. Follow the instructions to detar the files into A directory named Tina. This directory is created in the .hqx archive. You can choose to work with the library to the source or we have made a Macintosh version of the Tina library tinaLibPPC. This can be included without the Tina source. the mg_ and X sources are still needed as well as the tinatool sources.
There is a Unix script unpack which will not work on the Macintosh. Ignore it. Also ignore the lib directory It is not used. expand the *.hqx of the Macintosh distribution. This will make a folder named Tina. It will also create the directory hierarchy. Copy the tar files into the directories with the same names. src into src and inc into inc If the de-tar program used does not contain the ability to create symbolic links, Then the header files will have to be copied by hand. If the compiler can not resolve aliases then. The header files will also need to be copied. For this one will need to read the inc.tar file and make copies of the paths. Use a text editor that can handle large files If it can read hex all the better. A tar file is quite simple. Look for the pattern ../include/
When you de tar a newer distribution make sure a mg_* directory as well as some code warrior projects are not over written. If you are not using code warrior, then you will have to read the makefiles to create a project. The IDE must recognize filepaths. Do not use pre-compiled headers on the library. Instead use the header file provided in the include directory. This contains important stubs and overlay definitions for the X interface code. You will need the ANSI libraries as well or some sort of POSIX interface. Tina is strict ANSI. However the Macintosh header files are not. The compiler barfs on // comments. So it is a bit of a mishmash. Remember that installing TINA from scratch is not for the feint of mind. If all has gone well the library projects can be compiled without any errors. There are about 400 or so warnings. Tina is Standard C and takes advantage of blind library calls. I did try and fix this in an earlier version It made including the latest from Manchester time consuming.
when the library is compiled the front end can be compiled. This is only the tinatool .c and skeleton.c Most researchers will only want to recompile this to change the tools that appear in the main menu.
When the library and front end are compiled then the frame work can be compiled. This should compile without errors. There may be a few warnings on link as TINA attempts to re-define a few standard objects.
A pre compiled version of the library is here. This can be integrated with the front and the frame work If the researcher wants to customize their own tools.