concept     prepare     state  
  structure       user     future  
  sources       power user     chances  


   IndeView - To The Max   






Let us look at the control file of a very short "presentation" having just three pages:

The run file controls in which order the pages are shown.
Empty lines and lines starting with [#] are ignored.
You may change the order of pages by editing the "next=" entries: you may skip over pages (as shown in section "[Page0]" following the word OR) or jump to a previous page as shown in section "[Page2]". Doing the later creates a never ending loop to be leaved by the user pressing the [Esc] key (or the [Q] key resp.) only.
IndeView obtains detailed information about each page by reading the Page*.INF files specified in the run file, as shown in the following section.
   # IndeView presentation run file
# visit: http://www.indeview.org
Version=IndeView 1.0
# This is the title of the first page
next=Page1   OR   Page2
# The 2nd page's title text
# Here goes the title of the last page
next=NONE   OR   Page0


edit PAGE*.INF

Creator modules save one Page*.INF file for any page of your presentation, they look similar to this sample:

These page information files contain the page title, as shown in the page list to be opened by the [L] key, and they specify the image files with their respective resolutions. Any image file is covered by one "File=" entry having this format:
  • Filename, optionally with leading path, e.g. /net/share/pub/presentations/pre03/P0W6.PNG. If no path is specified or a relative path is used IndeView takes it as relative to the directory where the page information file is stored: by default the Creator modules store the Page*.INF files in the same directory as the image files.
  • White space
  • Width of the image in pixels
  • The letter x
  • Height of the image in pixels
   # IndeView page information file
# visit: http://www.indeview.org
Name=This is the title of the first page
File=P0W6.PNG 640x480
File=P0W7.PNG 704x576
File=P0W8.PNG 800x600
File=P0W10.PNG 1024x768
File=P0W11.PNG 1152x864
File=P0W12.PNG 1280x1024
File=P0W16.PNG 1600x1200

By deleting a "File=" entry you prevent IndeView from loading the respective image file, this would cause it to display the next larger image by automatically scaling it down to the screen size.
You may add your own entries, e.g. for saving other image formats on the CD or to compose a new presentation using a text editor (or a self-written shell script, resp.) putting together some image files without using a presentation program... You may ignore the default image sizes used by the Creator modules: it is even possible to use just one single image per page, in this case it will be zoomed by IndeView to match the screen size if you don't prevent IndeView from scaling / stretching.
Each "File=" entry must be terminated by image width/size information as shown above: IndeView would assume the page information file corrupt when not finding the size values.  
Actually there are a few additional entries in the page information files as of yet not processed. These parameters will be documented here once implementation of the respective features has been done.


don't scale / stretch

If no exactly matching image is found IndeView by default would scale ("zoom") an image to match screen size (or height, resp.).

You may prevent it from scaling by invoking IndeView using this command line parameter:

Additionally to scaling IndeView might also adjust the image's proportions in case a scaled image would fit only by height (or by width, resp.). By stretching the image a bit IndeView would try to make it matching. To prevent over-stretching IndeView will not stretch an image if this would result in changing the image's proportions by more than 10 percent. Also IndeView will display an image without stretching it if it did not scale the image before: if your original images are matching only in one direction (width or height) IndeView will not stretch them but display two border bars instead.

You may prevent it from stretching any images by invoking IndeView using this command line parameter:

To make these changes persistent on your CD please edit the file AUTORUN.INF to be found in the basis directory of data to be burned onto the CD.
The file contains this entry:
Add your desired parameter(s) like this:
or like this:
or like this:


If you like IndeView
please consider sending a little picture postcard
of your town / your village to
white space
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.