WebChange for RISC OS

from Soft Rock Software

User Guide

Introduction

What is WebChange 2?

WebChange 2 is an application designed to help with the maintenance of websites, and is particularly suitable for those people who prefer to design their pages in a text editor, such as StrongEd, Edit or Zap. It provides a number of functions in order to simplify those tasks which can be repetitive in nature, such as changing a single item of text on every page.

What the program is NOT is a website design package which will do it all for you except provide the content - there are other packages which aim to provide this function, and WebChange does not aim to compete with or replace them.

[Main Contents]

About These Instructions

These instructions are written with the following assumptions in mind:

• That the reader understands RISC OS conventions and knows what is meant by terms such as 'icon bar menu' and '<SELECT>', etc.
• That the reader understands HTML and what is meant by 'comment tags', 'ALT text', and 'relative file references' and so on.

The former should be covered by the user guide which came with your computer, and the latter by any number of books and on-line tutorials. For example, John Alldred's tutorial can be found at www.protovale.co.uk/john.html

[Main Contents]

Compatibility Issues

WebChange 2 should run on RISC OS versions 3.1 and higher, and in a system with a minimum of 4Mb RAM. It should be compatible with the various image filing systems and patches used on the RISC OS platform to provide longer filenames and more entries per directory - however, there are some known issues:

• raFS: WebChange 2 is unable to handle files found in the root directory of an raFS disk/directory; all files should be in subdirectories of same.
• MemFS (Memphis): The filename case changing functions do not appear to work with MemFS.
• WBModule: Because the last build of WebChange's front-end was done with an older version of WimpBASIC, some versions of the runtime module greater than v2.03 can cause odd behaviour. The most common is for the main window options not to be saved (and therefore acted upon). One solution, if no other WimpBASIC programs are being used which need a newer version of the module, is to stick with WBModule v2.03. An alternative (untested) option is to quit WebChange, modify the !WebChange.choices text file by hand, then re-load the software.

Main contents