IndeView - Usage: Preparations

HOME | USAGE | DEVELOPMENT | AUTHORS | LICENSE
concept | prepare | state |  |  |
structure | user | future |  |  |
sources | power user | chances |  |  |
| show |  |  |  |

# IndeView - Usage: prepare
INSTALL - CREATE - TEST

- unpack
- install:
  `ROOT_DATA` directory
  Creator modules
- build:
  load original presentation
  start Creator module
  test the presentation
  burn a CD

TOP

### unpacking the archive

By unpacking the archive file `indeview-[version number].tgz` you get a new directory `indeview-[version number]` with the contents of the archive.

Windows: | Use `Winzip` or `PicoZip` or another program capable to process *.tgz (tar gzip) files to unpack the downloaded archive file. Extract the archive and store its contents on the desktop (temporarily). Change the resulting folder's name from "indeview-[version numner]" to `IndeView`.
Mac OS/X: | Unpack the downloaded tar gzip archive file on the desktop: change the folder name from "indeview-[version numner]" to `IndeView`.
Linux: |
users of Gentoo Linux: | If you have used `emerge indeview` just skip this step. No need to unpack the archive, emerge has done it for you.
Call `tar -xzf indeview-[version number].tgz` in a directory where you have read+write rights, e.g. in a sub-directory of `$HOME`.

TOP

### installing IndeView

#### Creating the `ROOT_DATA` directory.

| Note: The `ROOT_DATA` directory is not the directory in which you will later store your presentations to be burned on CD, but it will be used by the Creator modules: there they will find the IndeView program runtime files to be copied over into the respective target directory. So the contents of the `ROOT_DATA` directory to be created now will not be changed nor supplemented later: the `ROOT_DATA` directory will just be the source directory of copy actions automatically taking place during Creator module runs.
Windows: | In the previous step you have unpacked the downloaded archive and renamed the resulting folder to `IndeView`. Move this folder into the program directory (typically `C:\Programs\`).
Mac OS/X: | In the previous step you have unpacked the downloaded archive and renamed the resulting folder to `IndeView`. Move this folder into the `Applications` folder.
Linux: |
users of Gentoo Linux: | If you have used `emerge indeview` just skip this step. The `ROOT_DATA` directory has been set up by emerge.
Open a console (e.g. an `xterm`) and go into the directory `indeview-[version number]`, which was created by unpacking the IndeView archive. This directory contains a sub-directory `ROOT_DATA` - move that into an extra IndeView directory all IndeView users have read permission to, e.g. like this: `mkdir /net/share/pub/IndeView mv ROOT_DATA /net/share/pub/IndeView/ROOT_DATA cd /net/share/pub/IndeView` By assigning the following access permissions you make the IndeView ROOT_DATA basis world-readable but only you are allowed to modify its contents: `chmod a+r-w+x ROOT_DATA/BIN/WINDOWS/* chmod a+r-w+x ROOT_DATA/BIN/LINUX/* chmod a+r-w+x ROOT_DATA/BIN/MAC_OSX/indeview.app/Contents/MacOS/* chmod a+r-w+x ROOT_DATA/BIN/MAC_OSX/indeview.app/Contents/* chmod a+r-w+x ROOT_DATA/BIN/MAC_OSX/indeview.app/* chmod a+r-w+x ROOT_DATA/BIN/MAC_OSX/* chmod a+r-w+x ROOT_DATA/BIN/* chmod a+r-w+x ROOT_DATA/*` In case you are Superuser on this machine it might be wise to specify root as owner of these files: so you make sure only root is allowed to modify them: `su -c"chown -R root ROOT_DATA"` Go back to the previous directory: `cd -`
NOTE: | The Creator modules will copy everything that is stored in the `ROOT_DATA` directory into the respective target directory. Thus you may store additional content in the `ROOT_DATA` directory: things you want to have on all of the IndeView presentation CDs - no matter what presentation that will be nor by whom the CD will be created.

TOP

#### Installing Creator modules.

As you unpacked the IndeView archivs (see unpacking the archive) a directory called `Creator` got created, containing the available Creator modules stored in separate sub-directories named after their respective presentation programs.
OpenOffice: | It is easy to install the `IndeViewExport.bas` script in OpenOffice but it takes a while: the description has several steps described on a page of their own.
KOffice: |
users of Gentoo Linux: | If you have used `emerge indeview` just skip this step. The `kpr2iv.sh` script is adjusted and installed already.
The `kpr2iv.sh` script needs a little adjusting, please load it into your preferred editor. Ths first lines should look like this:
    #!/bin/bash

    ROOT_DATA=unknown
| Replace the word `unknown` by the complete path of the `ROOT_DATA` directory created in the previous step but make sure to not add a trailing Slash! The script should now look similar to this:
    #!/bin/bash

    ROOT_DATA=/net/share/pub/IndeView/ROOT_DATA
| Save it and close the editor. Make the `kpr2iv.sh` script available by moving it to a place all authorized users are having in their `$PATH` variable, and assign the access right, e.g. like this: `su mv kpr2iv.sh /usr/local/bin/ chmod a+r-w+x /usr/local/bin/kpr2iv.sh chown root /usr/local/bin/kpr2iv.sh exit`

TOP

### building an IndeView presentation

#### Loading the original presentation:

To create an IndeView presentation first load your presentation into the original program (e.g. into OpenOffice Impress or into KOffice KPresenter, resp.).
IndeView will show the titles of all pages when the [L] key or middle mouse button is pressed: make sure to use your presentation program to specify expressive titles for all pages, before starting the Creator module.

TOP

#### Starting the Creator module:

OpenOffice: since release 1.1 | Before (see installing IndeView) you have embedded the `IndeViewExport` module into OpenOffice, so you may now start this module by clicking onto the respective toolbar icon: A directory selection dialog box appears, use it to specify the target directory for the IndeView presentation to be created. Data processing takes a while (for longer presentations it might a few minutes), you will notice the end of script runtime looking at the IndeViewExport icon in the toolbar: it will return to its original colouring when done.
KOffice: since release 1.3.1 | Before (see installing IndeView) you have stored the `kpr2iv.sh` script in your filesystem, now open a console window to get a command prompt and start it like this:
`kpr2iv.sh target-directory`
e.g. you write:
`kpr2iv.sh /home/paola/myData/presentation-A`
This creates an IndeView presentation from the presentation currently loaded in KPresenter, the IndeView presentation will be stored in the directory specified.

TOP

#### Testing your presentation:

| You may test your presentation without burning a CD(-RW): just invoke IndeView from command line: Windows: Open the command line, in the Start menu - you find an entry saying "DOS shell" (or similar) - this gets you a command line window. Linux: Open a shell, e.g. "xterm" or "konsole" On this command use the "`cd`" command to go into the directory you had choosen as target directory when starting the Creator module - according to the sample shown above this would be: `/home/paola/myData/presentation-A/` . From there you start the IndeView program like this: Windows: `BIN\WINDOWS\INDEVIEW.EXE` Linux: `BIN/LINUX/indeview` Mac OS/X: `BIN/MAC_OSX/indeview` IndeView will try to find a file `INDEVIEW.RUN`, if it succeeds your presentation will be shown. |

IndeView makes it possible to test your presentation down to the last detail:
As shown below you may examine the pages in different zooming levels to be sure pictures adjusted to these resolutions by OpenOffice (or KOffice, resp.) look fine.
There is no magic in the Creator modules: all they do is using some of your presentation program's capabilities: this might go wrong, like you know it from using your presentation program - IndeView however gives you the chance to detect and correct any erroneous pages while preparing you presentation at home.
Perhaps it requires some trial-and-error loops with your presentation program to find a set of fonts looking good at all zoom levels: make use of these testing options given by IndeView to spare yourself and your audience the conventional unpleasant surprises during presentation time!

Hint: | In case there is a photo in the presentation which your presentation program by no means is able to nicely adjust to all of the display sizes there is a last option you might want to try: delete the erroneous image file! This might do the job as IndeView will take the next bigger image format and automatically scale it down to screen size if no image file matching the screen size is found for a page of the presentation. Actually this scaling function is a stopgap measure for the rare case of your presentation being to be displayed using a screen resolution not supported by the Creator modules. Look at the respective page information file listing all image files (and their respective dimensions) available for a page. Keep in mind to also remove the respective line from the page information file whenever you delete an image file, else the Viewer application will assume a CD error and display a symbol:
| (You may use this for testing if you have removed the right image file: just refrain from deleting the line in the page information file and watch out for the error symbol.)

TOP

#### Burning an IndeView CD:

| Right bevor burning the CD you may test your presentation: just start IndeView on your production computer. |

Make sure to burn everything onto your CD that is inside of the IndeView presentations directory created in the previous step. (For testing you might want to use a CD-RW.)
If your target directory was `/home/paola/myData/presentation-A` you would take all of the files and directories found in there and burn them in exactly the same way onto your CD as you find them in the `presentation-A` directory, this will be:

`AUTORUN.INF` | Control file for the Windows Autostart option
`BIN/` | Binary directory, among others holding the Viewer programs
`DATA/` | Data directory, with all data of your presentation
`INDEVIEW.RUN` | Control file for the Viewer

You should see the four entries listed above in the CD's main directory after it is burned. Feel free to add other directories or files, e.g. to also add your native OpenOffice (or KOffice, resp.) presentation file or store a special HTML version created by Impress (or by KPresenter, resp.)...

TOP | GO TO THE SHOW CHAPTER

If you like IndeView
please consider sending a little picture postcard
of your town / your village to
Your feedback will be very much appreciated:
we will be glad about receiving a visual representation
of where on earth our IndeView users are living.