Fially got round to downloading and installing Hollywood 11 to my AROS machine (x86) but hit some problems:
The GUI does not work. 'Display' does nothing and 'Compile' always complains that there are errors in the script and compilation has failed. This is with both the supplied examples and other known working scripts. If the compiler is used durectly from the command line, the scripts can be run and compiled.
The plugins in libs:hollwood are ignored and Hollywoodplayer (usually kep in c:) or the Hollywood compiler (in Hollywood:system/) complains the plugin is not present. If the 'plugin' directory is set up within the directory Hollywoodplayer or Hollywood is run from, the script works. Amigasystem has also noted this behaviour (please see https://arosworld.org/print.php?type=F& ... 12236&nr=1).
Cheers,
Nigel.
Hollywood 11 GUI and libs:hollywood/ do not work on AROS
- airsoftsoftwair
- Posts: 5983
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Hollywood 11 GUI and libs:hollywood/ do not work on AROS
How have you installed Hollywood on AROS? Have you used the included installer or have you installed it manually?
Keep in mind that the installation structure has changed significantly in Hollywood 11. The main executables (Hollywood, Miniwood) must no longer be placed in Hollywood:System but in Hollywood: for consistency with other platforms. Also Hollywood.sys must be stored in Hollywood: and not in Hollywood:System. The included installer will also copy those files to Hollywood:System but that is only for Hollywood Designer compatibility. Hollywood itself (e.g. the GUI) no longer looks for files in Hollywood:System but in Hollywood: directly. If you have installed it manually, you might still be using the old structure from the days before Hollywood 11 which could explain why the GUI doesn't work...
...that is another piece of evidence that strongly suggests something is wrong with your installation... see above...
This might be related to another significant change in Hollywood 11: Plugins are no longer loaded automatically. Cf. this description from the manual:
Plugins will no longer be loaded automatically on startup now. With almost 50 different plugins available now, it would be a waste of CPU time and memory (especially on low-end systems like AmigaOS 3) to always load all of the installed plugins on startup so only the plugins that the scripts explicitly requests by using the @REQUIRE preprocessor command will be loaded now. If you want the old behaviour back, you can set the new AutoLoadPlugins tag in the @OPTIONS preprocessor command to True. In that case, Hollywood will behave as before and load all installed plugins on startup every time. Note that this change also affects executables compiled by Hollywood: Executables compiled by Hollywood will no longer automatically load all Hollywood plugins that are stored in the same directory as the executable either now. Only plugins that the script explicitly requests by using the @REQUIRE preprocessor command will be loaded. This behaviour is much better than the old one because previously you could manipulate how a Hollywood program behaved just by dropping some new Hollywood plugins in the same directory as the executable, which isn't a good default behaviour. Once again, if you want the old behaviour back, just set the new AutoLoadPlugins tag in the @OPTIONS preprocessor command and Hollywood executables will automatically load all plugins that are in the same directory as the executable, just like it was in previous Hollywood versions. Amiga users do note that if you also want to have plugins stored in LIBS:Hollywood loaded, you need to set the GlobalPlugins tag in @OPTIONS to True as well, but only when compiling executables. When running scripts Hollywood will automatically scan LIBS:Hollywood too if AutoLoadPlugins is set to True or you use @REQUIRE or LoadPlugin() to load a plugin.