Upgrading from USoft 8

The underlying architecture of USoft Web Designer has changed drastically between USoft 8 and USoft 9.

If you only used configured functionality (standard controls and methods in Interface.js), it is likely that the application will work more or less as before. But there are a lot of possible reasons why an application might no longer work and would require manual repair work. Here are a few:

You have created or changed existing controls in XSL

Version 9 does not use XSL anymore. Adjustments in one of the XSL files will have no effect. Changes must be transferred to the initial document, CustScript.js, or usoft.ui.controls.js. The xsl-directory has become obsolete and can be removed from the alt-directory.

You have overridden functionality in JavaScript files

Most of the JavaScript files of USoft 8 have become obsolete and are no longer used. The only survivor is CustScript.js. It is not easy to tell where to apply the changes. That depends on context.

Changes in CustScript.js can also be overrides of functionality defined in other JavaScript files. As a result, for each change in this file, you need to evaluate whether or not the change is still relevant and if so, whether it should be rewritten.

You have custom CSS settings on HTML id values and class values

In USoft 9, the number of HTML elements, ids and classes has been greatly reduced. Some controls have a different HTML structure and, in some cases, classes have been renamed. This can have its impact on defined CSS instructions.

One document

Version 8 had a complete reload of the HTML in the IFRAME on every page navigation. In version 9, this no longer is the case. There is only a single HTML document. Instead, parts of the DOM are dynamically altered. This can have its impact on JavaScript that is executed. Scripting dependent on this functionality may not function as before.