Using imagevue.exe standalone
In the release version imageVue .15 we included an imageVue.exe standalone gallery
which allows you to run imageVue on your local desktop.
What is imagevue.exe standalone?
Just to remove all possible misunderstandings here: imageVue.exe is not an application that allows you to view images that are on your local machine(unless
you are using a http localhost server). Then what is it ImageVue.exe can simply
be setup to connect directly to your online imageVue gallery. Why would you do
this? There are three possible reasons:
1. No need for a browser, less loading, and the imageVue.exe application is a much
faster and more stabile application than the general browser using flashplugin.
ImageVue simply runs smoother, faster, and opens in a fullscreen shell, enhancing
the image browsing experience.
2. If you are able to setup a localhost server, you can connect the imageVue.exe
directly to your localhost, viewing images locally without having to use a browser.
3. Distribute your gallery to clients with no requirements of player/plugin. Obviously
you need to mention that internet connection is required.
How to set up the imagevue.exe standalone
Locate the standalone files under source/standalone/ in imagevue.zip. Open standalone.ini, which by default looks like this and hooks up to our testserver:
|
globalpath=http://imagevuex.inn.no/imagevue/ |
Change the value of globalpath to the absolute path of your online gallery. Save
file... You can also define a configfile in the standalone.ini, as you might want
to use another configuration than the default config.ini. Example:
|
globalpath=http://imagevuex.inn.no/imagevue/&configfile=standaloneconfig.ini |
To run imageVue.exe standalone successfully, you need imagevue.exe and standalone.ini in the same folder on your harddrive.
Notes
The main reason why you might want to use a different configfile, is because
the standalone imagevue.exe does not support popup windows, because it has no
support for javascript. You also need to disable starfx and slideshow if you are
using standalone because there seems to be some problems with permissions when
running these features/modules.
