AMIGASYSTEM wrote:

@AMIGASYSTEM - With the new version of the Hollywood language released a while ago, there have also been changes to the binary files, where, in my opinion, something doesn’t quite add up.

In practice, the new development version of Hollywood significantly streamlines the binaries by removing libraries that are now required externally.

Well, or rather badly: previously, some applications ‘that didn’t include the library internally’ would look for it in the programme folder or in the system’s Libs/Hollywood folder.

Now, however, all required libraries, “and there are quite a few”, must be located in the programme folder. In practice, this means the system will end up with dozens and dozens of duplicate libraries. If we then add that some older Hollywood applications refuse to use new libraries and instead require a specific older version, the confusion only increases.

The Amiga philosophy dictates that all libraries, as is the case with other operating systems, must be located in a single system folder: ‘Libs’ for AROS and Amiga. This ensures there is only one copy, making updates straightforward; otherwise, they would all need to be updated as applications are updated.

Quote

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.

Templario wrote:

@Templario - Perhaps a little solution to this problem is that the Hollywood programs and games have the plugins embeded the plugins inside of executables.

ntromans wrote:

@ntromans - .

I've just removed the plugins folder to ensure libs:Hollywood is always used.

Cheers,
Nigel.

AMIGASYSTEM wrote:

@AMIGASYSTEM -

ntromans wrote:

@ntromans - .

I've just removed the plugins folder to ensure libs:Hollywood is always used.

Cheers,
Nigel.

Are you sure? The latest applications compiled with Hollywood 11 no longer use Libs:Hollywood, but look for plugins ‘only’ in the binary folder.

In new applications, such as Image2PDF, try deleting the plugins from the programme folder and you’ll see that it no longer launches and will request the plugins from the folder.