A bloated binary executable file of 2876136 bytes is just unacceptable on a Commodore Amiga computer, even the most high-end.

Some nice features though.

_________________
SAM440EP-FLEX @ 733 Mhz, AmigaOS 4.1 Update 1

It's an Hollywood program hence the size.

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

Thanks, I had noticed that.

_________________
SAM440EP-FLEX @ 733 Mhz, AmigaOS 4.1 Update 1

@Messi

Should not be shocking, all RNO software is Hollywood.
it’s a trade off, he could made in C/C++ but wont support as many operating systems, he gets less users, and less income, he is trying to make a few bucks in donations.
Yeh does not make a lot of sense to me that Hollywood programs are so big, if we look at Amos Pro for example is pretty compact, but that’s nothing RNO can do anything about, how big the program is I don’t care, as long don’t run out of resources to the point where effect other programs, takes too long to load, or is too slow use.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Nuts

OK got it.

_________________
SAM440EP-FLEX @ 733 Mhz, AmigaOS 4.1 Update 1

Looks nice!

_________________

I love it on MorphOS. It reminds me of Rhythmbox on Linux and has a proper handling of tags even in FLACs. I don't care if it's written in Hollywood or not. It feels like a native application.

Quote:

A bloated binary executable file of 2876136 bytes is just unacceptable on a Commodore Amiga computer, even the most high-end.

As told in the previous replies, my program is made with Hollywood. Programs made with it can be distributed as executables that include the whole Hollywood player code or as applets that need to be run with a separate Hollywood player application. I have decided to publish my programs as standalone executables, which means the binary size of an executable is a bit bigger. RNOTunes as an applet would be 75k in size, but I think it's better to distribute it as an standalone program (including all Hollywood functionality), it makes it bigger than 2MB.

In my opinion HDD space is cheap nowadays and it's better to "waste" some mass storage space rather than using CPU time to decrunch executabes. At least I have tens of gigabytes of space on each Amiga, or compatible, I have.

And yes, if I wouldn't have coded these programs in Hollywood, I probably wouldn't have released them at all. Or I would have just coded one or two programs with less features, and they would have been for MorphOS only. So, take it or leave it :)

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@jPV

Fine that you use Hollywood.

My point is that the C= Amiga is designed for optimal use of resources and speed and that huge size looks in contrast with this design (...).
It is not only about the HDD space used but rather how the system works and performs after say your app is loaded.

Anyway, I understand that you want to support as many systems as possible and also I think some features are nice.

_________________
SAM440EP-FLEX @ 733 Mhz, AmigaOS 4.1 Update 1