6.2 Compatibility notes

Hollywood 9.0 API changes

There have been a few API changes in Hollywood 9.0. Most likely you won't have to adapt your scripts to work with 9.0. Just check the following notes to see if your script requires any adaption.

Hollywood 8.0 API changes

There have been no API changes for Hollywood 8.0.

Hollywood 7.1 API changes

There have been some small API changes in Hollywood 7.1. Most likely you won't have to adapt your scripts to work with 7.1. Just check the following notes to see if your script requires adaption.

Hollywood 7.0 API changes

New plugin and keyfile location on Windows, macOS, Linux, and Android

First of all, Windows, macOS, and Linux users should note that in Hollywood 7.0 plugins must now be stored in a Plugins subdirectory that must be in the same directory as the Hollywood executable on Windows and Linux. On macOS, the Plugins directory must be stored inside the application bundle, i.e. inside the HollywoodInterpreter.app/Contents/Resources/Plugins directory. Note that HollywoodInterpreter.app is stored inside the Hollywood.app application bundle, namely in Hollywood.app/Contents/Resources. On Android, plugins must now be stored inside the Hollywood/Plugins directory on your SD card (instead of Hollywood/_Plugins as in earlier versions). On AmigaOS and compatibles, plugins must be copied to LIBS:Hollywood as usual.

Note that executables compiled by Hollywood will still load plugins from the same directory as the executable (except on macOS where they must be inside the app bundle's Resources directory). Hollywood itself, however, will now need the plugins inside a Plugins subdirectory on Windows, macOS, and Linux as described above.

macOS users please do also note that the file Hollywood.key must now be copied to HollywoodInterpreter.app/Contents/Resources as well. It must no longer be in the HollywoodInterpreter.app/Contents/MacOS directory.

Important Unicode notes and other API changes

Since Hollywood 7.0 introduces Unicode support there might be some compatibility issues with your old scripts. If you don't want to adapt your scripts, you can simply run them in non-Unicode mode by disabling Unicode like this:

 
@OPTIONS {Encoding = #ENCODING_ISO8859_1}

If you add this as the very first line of your script, Hollywood will run your script in legacy mode and there shouldn't be any compatibility issues. However, your script will run in ISO 8899-1 mode then which means that it won't run correctly on non-Western European systems.

Thus, it is recommended that you don't run your script in legacy mode but use Unicode mode all the time. Most scripts will probably run just out of the box without any issues and without any need for adapting anything. If your script shows compatibility issues with Hollywood 7.0, please read the following list of API changes in Hollywood 7.0 to learn how to fix your scripts.

Hollywood 6.0 API changes

There have been some small API changes in Hollywood 6.0. Most likely you won't have to adapt your scripts to work with 6.0. Just check the following notes to see if your script requires adaption.

Hollywood 5.0 API changes

There have been some small API changes in Hollywood 5.0. Most likely you won't have to adapt your scripts to work with 5.0. Just check the following notes to see if your script requires adaption.

Hollywood 4.5 API changes

There have been some small API changes in Hollywood 4.5. Most likely you won't need to adapt your scripts to work with 4.5. Just check the following notes to see if your script requires adaption.

Hollywood 4.0 API changes

There have been some small API changes in Hollywood 4.0. Most likely your won't need to adapt your scripts to work with 4.0. Just check the following notes to see if your script requires adaption.

Hollywood 3.1 API changes

There have been some small API changes in Hollywood 3.1. Most likely your won't need to adapt your scripts to work with 3.1. Just check the following notes to see if your script requires adaption.

Hollywood 3.0 API changes

There have been some small API changes in Hollywood 3.0. Most likely your won't need to adapt your scripts to work with 3.0. Just check the following notes to see if your script requires adaption.

Hollywood 2.5 API changes

There have been some small API changes in Hollywood 2.5. Most likely your won't need to adapt your scripts to work with 2.5. Just check the following notes to see if your script requires adaption.

Hollywood 2.0 API changes

Although Hollywood 2.0 is a gigantic update, only little API changes were necessary. Here is a list of things you have to change in your script:

Hollywood 1.9 API changes

There were some minor API changes in Hollywood 1.9, which are listed here:

Hollywood 1.5 API changes

Unfortunately I had to make some API changes to the Hollywood language in the 1.5 update. If your script does not work correctly under Hollywood 1.5 but worked under 1.0, please read the following information and adapt your script.


Show TOC