Local editor
Using a local program running on the user's computer is usually the
best way to edit files. The user can use the HTML editor, drawing
program or word processor she is most familiar with.
By pressing the Edit button the appropriate local
program is started with the correct file loaded. The user can edit and
save normally. In case a HTML file is edited the user will still have
to press the View button to see the end result after the
template has been added. When the result is finished the user has to
use the Commit button to commit the changes to the version
control repository.
It is however very important to close the file in the local editor
after commiting. Because it will no longer be possible to save the
file, or rather if the file is saved SiteBuilder might not find
it. The reason for this is that the file being edited is only
available to the local editor while SiteBuilder thinks the user is
editing it, or rather while the file exists in the user's edit
area. As the user commits the changes SiteBuilder assumes that the
user is no longer interested in editing that particular file and
removes it from the user's edit area.
In case the user continues to edit a file that has been commited
she must save the file on the local hard disk and use the
Upload button to upload the changes. It is also possible to
press the Edit button after commiting the changes, in which
case SiteBuilder will start the local program again.
The user must always press the Edit button in the
content editor to start editing a file. It is not possible to use the
Open function of the local program, since the file will likely
not exist in the user's edit area yet. Nor is it possible to rename a
file by using the Save As function in the local
program. SiteBuilder will not find the new file. It is however
possible to use Save As to save the file to the local hard disk
and then use the Upload new file button in the content
editor to upload the new file to SiteBuilder.
Roxen Application Launcher
To start a local program on the user's computer a small program,
Roxen Application Launcher, has to be installed. This program
is the necessary glue between the web browser and the other programs
installed on the user's computer.
SiteBuilder must also be instructed to start the Roxen Application
Launcher for the appropriate file types. This is done by choosing the
correct Editor profile with in User preferences wizard
under the Configuration tab. Which editor profile are
available is dependent on the actual SiteBuilder installation. The
editor profile controls for which file types Roxen Application
Launcher should be started.
What program to start for a particular file type is not configured
in SiteBuilder but rather in the registry for the local computer (this
assumes the Windows version of the Roxen Application Server is
used). This is a security precaution, it must not be possible to start
every program on the user's hard disk from the web. Usually there will
be a site specific registry file containing the appropriate
configurations. It is installed simply by downloading the registry
file and double-clicking on it.
Sometimes the web browser will open a dialog about a "possible
security hazard", before invoking the Roxen Application Launcher. The
user will be asked whether to open the file or save it to disk. It is
safe to open it is also safe to instruct the web browser never to ask
that question again.
|