HomeSite 4.5.2 Release Notes

November 30, 2000

This maintenance release achieves several goals:

You can use this document to trace the development history of this release and to learn about known issues that are still outstanding. The bugtracker issue number is included for items where applicable.

New Features and Enhancements

Related items in this section are grouped by feature or function, the remainder are in the Other Enhancements section.

FTP

Windows System Resources and Memory Usage

A major effort was made to correct memory usage issues in all the components of the product. These issues primarily affect Windows 95/98/ME systems, but can affect Windows NT/200 systems, as well. For details of individual issues, see bugtracker issues 17614 - 17624.

Web resource on Windows 9.x resources

For a useful description of memory usage on Windows 95/98/ME systems, see this article on InfiniSource.

On Windows 9.x systems, the product will check the system resource levels (User and GDI) on startup and will monitor these levels while the program is running. If either User or GDI resources reach a critical level while running the application, you will be given the option of saving all documents and exiting, saving all documents and continuing to run the program, or continuing without saving.

The behavior of this feature is controlled by two Registry string values. The first is:
HKEY_CURRENT_USER\Software\Allaire\HomeSite45\ResourceLevelCheck
This value sets the resource level threshold which triggers the warning dialog. The default value is "30", meaning that if the GDI or User level drops to 30%, the warning will be displayed. If you continue to run the application, the threshold will drop by 5% (e.g., 25%).

The value of the second key sets the interval between resource level checks (in minutes). The default value is 10 minutes.
HKEY_CURRENT_USER\Software\Allaire\HomeSite45\ResourceLevelInterval

Notes on freeing Win95/98/ME start-up resources

Thanks to Geoff Crenshaw for posting some valuable information to the Allaire Beta Forum. His original note has been edited a bit.
To free some of your start-up resources:

  1. On the Windows Start menu, click Run.
  2. Type msconfig in the Run dialog box and click OK.
  3. Carefully uncheck items you are absolutely certain you do not need, use, or have.
    Make a list of changes as you proceed.
  4. Click Apply before moving to the next tab.

XML Language Validation

Improvements were made to code validation of XML-based languages. [18543].

Tag Definitions

JavaServer Pages

The complete set of JRun tag definitions is installed with this release of HomeSite. This enables the following features:

If you develop Web applications with JSP, you can install the JRun Developer version from the the HomeSite CD-ROM to test JRun locally. To try the JSP productivity tools available in JRun Studio, download the latest evaluation version from the Allaire site. The Allaire JRun DevCenter features developer resources and product news.

SMIL, IMFL, RTML

Corrections and enhancements were made to SMIL 1.0, IMFL, and RTML tag definitions and to the Tag Chooser:

WML

Visual Tools Object Model (VTOM)

Other Enhancements

Bug Fixes

Related items in this section are grouped by feature or function, the remainder are in the Other Fixes section.

FTP

Tag Tree/Tag Inspector

Search and Replace

Other Fixes

Known Issues

XML Language Tag Definition Support

If a tag has an attribute of the form namespace:attribute="value" and the tag is supported with a tag definition, then editing that tag in either the tag editor or the Tag Inspector causes the value of that attribute and all attributes following it in the same tag to be lost.

The WML standard defines an attribute - xml:lang - that causes this behavior when parsed. A parser fix is not possible for this release, but a partial solution has been implemented in the tag definitions for WML.

WML tag editors now ensure that when a tag containing the xml:lang attribute is inserted or entered, that attribute will always be written as the very last one for the tag. Lost values can be re-entered in the tag editor or Tag Inspector to complete the tag coding.

If you use a tool other than a tag editor to write the tag, make sure that you place xml:lang after any other attribute, so that further editing will cause minimal problems.

FTP issues

Other Known Issues