Haiku in media

I always wondered, why we do’t have a hey open deskbarmenu like command in the first boot script?


There is a quick tour and userguide icon on the desktop. If people don’t click there, guess what they will do with the quick tour window? My guess is they will go “I know this, it’s a UNIX system!”, close the window, and start messing around. Especially video reviewers who really want to do “I know what I’m doing and I’ll show you guys” type of videos, and not “I just sit there for an hour reading the user manual of an operating system”.

Video reviews are not the same thing as normal users getting their hands on the system. The fix for better video reviews is making a press kit with some help for reviewers (here’s the things to take care of in setting up your VM so you don’t run into network problems, here’s how to start apps, here is a few cool features to show). And also don’t forget to “roast” these people in their youtube comments (kindly and politely of course) so they don’t do such a mistake again.

We can also improve the user interface, of course, but it doesn’t have to be so dramatic. Subtle changes like a little arrow/triangle on the leaf button could do a lot already.


When it comes to the user guide, I fear that they genuinely just overlook the desktop icon or ignore it since there is just so much new stuff to take in, or ignore it expecting a lengthy tech manual. It doesn’t really strike me as a conscious decision to ignore it, more like people being used to there being a lot of random default stuff on their Windows desktops.

If it’s really them actively ignoring the icon to prove how smart they are, then I’m afraid they probably won’t really look at a press kit either,

1 Like

Perhaps the first time the desktop is started on release builds, the Quick Tour should be automatically opened.


To make people lesrn faster where webpostives quit button is?

The firstbootprompt already mentions the quicktour iirc, if people dont even read that small snipper they will hardly read the quick tour.

I would remove the bebook from release builds, and change the deskbar Icon/UI slightly to make it more noticeable as a menu.

Other than that, why not do some grandmother testing? I did that once and deskbar was not that much of a problem but the german locale removing translated application names plus the untranslated deskbar folders made the system unusable.


Why do we have to have the same discussions over and over again? First search the forum and then inform, then write something.

March 2021: Making the QuickTour even more visible - Development / OS - Haiku Community (haiku-os.org)
Dezember 2021: A “Welcome” App for Haiku - Ideas - Haiku Community (haiku-os.org)
November 2017: Haiku needs a welcome app - Ideas - Haiku Community (haiku-os.org)

Here we go again :wink:


It’s presumably because those discussions inevitably fizzle out and become forgotten until the next video or article where the reviewer can’t find the application menu/never finds stack&tile/any number of other issues that crop up over and over, all of which could be helped by auto-opening the quick tour on first boot or making some minor UI tweaks.


We can talk about it then we release the first R1 and not for a beta. There is no one who have the time to manage this at the moment. There are enough other problems around.


Maybe people could discuss how to improve the quality of the reviewers , instead.

Maybe the “grandma test” could show some places for improvement, but some self-called reviewer of an operating system that do not try to automatically click on the only thing in the screen that is not obviously an icon ?

1 Like

We need articles of people who know Haiku and then explain how to use the system. And not only newbees


Exactly like that.

1 Like

The discussion don’t fizzle, they reach a conclusion that someones needs to do something about it, and then nothing is done. Re doing the discussion step everytime doesn’t get us any further. What we need is someone to submit a patch.


It’s not a bad thing to continue discussing relevant issues. Just because no one has time to submit a patch doesn’t mean it’s not still valuable to have conversations about it, especially since different options/ideas can be brought up each time.

A very nice tutorial, video, about Haiku in VirtualBox from “The Retro Dev”:

Website: https://www.theretrodev.com/

In this video we will be installing Haiku inside of VirtualBox plus taking a quick look around the operating system.


Just watched an interesting video from “DS-Tech Media” about Haiku Beta 4 on YouTube.

It’s not the usual, we throw Haiku into a virtual machine, click around a bit, realize YouTube doesn’t work, and then the conclusion comes. But you can see that the guy has dealt with the system and tried to show the system in its entirety. Especially for new users it should be interesting.
Also he tried to show the multimedia properties of the system. And maybe there is more to come on the subject.

For me this was the most interesting video about haiku in a long time.

Big thanks to the creator :+1:


Easily the best of all the “reviews” of Haiku R1 B4.

Most of us non-devs have no idea of the depth and complexity of this OS.


A nice presentation of Haiku, with an elaborate intro, and it’s looong. :slight_smile:

It does try to cover everything, but necessarily has to stay close to the surface to not blow up the 45 minutes to a few hours. And it’s extremely fast paced. It might have been better to concentrate on a few features and cover them in-depth.

There may be a second video focusing on media creation in the future, which will be interesting. In this video he already spent some time with Cortex, and I’m quite surprised how well it still appears to work, considering it’s code comes straight from the BeOS days and AFAIK hasn’t been seriously touched for decades.

One has to admit, Be Inc.'s marketing ploy of proclaiming to be the “Media OS” was extremely successful, when people still have these nebulous expectations from its spiritual successor Haiku…

Anyway, good work, Jay! :clap: :clap: :clap:


anyone venturing into webcam and other types of usb devices

this might be helpful

I’ve just tried compiling libuvc under both Linux and Haiku, and yes, the Haiku version compiles and even the test application on the website compiles, and starts running, gets some initial success from talking to libuvc (connects and lists the webcam device), but then it gets stuck in libusb_wait_for_event / pthread_cond_clockwait / cond_wait / _kern_mutex_switch_lock.


Our libusb port is still broken. It’s possible that porting libuvc to use the USB Kit backend instead would fix the problem. Or, of course, investigating and fixing the problem in libusb.