@Elwood
Quote:
Elwood wrote:
@lazi
Quote:If you would be able to directly use API calls and OS structures
I understand that. Hollywood could provide a way to do stuff in an independant manner.
As an example you could use a function called Getprogramdir and Hollywood would use DOS/GetProgramDir() on AmigaOS and something else on other platforms.
Noboby said it is technically impossible.
The problem is that old scheme: new hardware-new users-more support...
Hollywood is a great software even in the current form. I hope that the author will be inspired enough by users (buyers) to continue development.
Maybe I do not reveal secrets when paste here some lines from the "To Do" section of the Hollywood documentation just to arouse your interest:
"Here are some ideas that are on my to do list:
- support for new platforms like Windows, Linux and MacOS
- automated scaling engine which allows you to scale the display of any application; when layers are enabled this scaling engine should use lossless scaling for vector and text forms
- multiple displays
- a library which allows you to implement GUI elements in your scripts (i.e. an interface to gadtools.library)
- support for rotating text objects
- support for miter and bevel line join types (currently only rounded join type supported)
- support for AROS PPC
- support for video streaming; a suitable API would be required here
- asynchronous anim playback through layers
- support for palette images: a blast from the past!; dithering would be necessary when rendering RGB data to palette brushes
- speed of all the transition fx functions should be passed in milliseconds instead of a custom type; would help to time scripts correctly
- text transition effects
- new tag for preprocessor commands so that the data specified in them is not linked but loaded dynamically when required
- a version for PowerUP?
- a version which can render to palette screens? was possible in 1.x and removed in 2.0 but could be reimplemented quite easily though it would be totally slow
- more features"