Linked by Razvan T. Coloja on Mon 3rd Jan 2011 23:30 UTC
BeOS & Derivatives To understand what the BeOS and Haiku operating systems are, we first must remember that BeOS was developed with the multimedia user in mind. BeOS wanted to be what OS X has become today: an easy to use, attractive operating system. However, BeOS was a niche OS, destined for the media-hungry user. The percentage of audio and video applications available for Haiku is greater than the one in Linux, OS X or Windows, and the inner workings of the operating system were created in such a way, that the same multimedia passionate would find it easy to work with the user interface and files. Each application can interfere with other applications of its kind. A WAVE file selection can be dragged from a sound editor and onto the desktop, to create an audio file. Audio applications can interfere with each other via the Haiku Media Kit -- the corespondent of a Linux sound server. Applications like Cortex are a perfect example of how BeOS and Haiku deal with multimedia files: you can have more than one soundcard and use each one of those soundcards independently or separately. You can link one soundcard to the Audio Mixer, start a drum machine application and link that software to the Audio Mixer. If you want to output whatever you create with the audio application, all you have to do is drag the microphone and link it to the application's icon in Cortex.
Thread beginning with comment 455948
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: No it won't
by matako on Wed 5th Jan 2011 08:53 UTC in reply to "RE[4]: No it won't"
matako
Member since:
2009-02-13

Well, I did some casual programming on the BeOS, I have an app listed on BeBits and Haikuware (hey, that binary compatibility thing actually works!).

If I had to choose one BeAPI concept that really stands out I would definitely choose the whole handler/looper concept. It _is_ simple. As a matter of fact my first thought was "where is stuff?". I really feel that the whole concept is both simpler and more flexible that many other frameworks and it does its magic with very basic C++, no template voodoo or anything, so it can be easily mapped to any OOP prog. language.

You pass messages, you handle them - essential locking (handlers) is done for you. If you make another message looper (like a window), then a new thread is created for you automatically. Of course, you can still do MT the old-fashioned way, remember - this is a messaging framework it is not a solution to everything, but for what it is designed, it works well.

As long as you pass and handle messages, you are fine. On top of that there is a high level of orthogonality - drag and drop, inter-app messaging, app scripting, mode monitoring.. you name it - it is all the same concept, the learning curve is excellent! The only thing I miss is perhaps some handy hooks for app scripting. I mean they did them for everything else.

HOWEVER... BeAPI is not for a total beginner. You do need to be a reasonably proficient computer programmer. But you know what - what's wrong with that requirement? Nothing any of us could not achieve.

Edited 2011-01-05 09:01 UTC

Reply Parent Score: 2