Suggestion Box

I'm a bit disappointed with the default image viewer in Haiku. Images should be shown in their original sizes by default with no black border. Window size should fit the image, not the other way around. Animations should be shown animated, not just a static first frame. Controls should take up minimal space.

I suggest that the default Haiku image viewer should be more like Xee on the Mac (the best simple image viewer I've ever used):
http://wakaba.c3.cx/s/apps/xee.html

The source code is available for download.

I know there are many more important things to worry about fixing in Haiku, but I hope somebody can look into this eventually.

I think something like an 'appstone' would be great.
Why not create a simple, easy to use, Scripting language
wich has full accses to the haiku API and the Computer.Or
you use the executable format from haiku and download a simple program
wich will run faster than a app.Or a packet , wich contains a script or
program and files wich are needet.
I couldt work like this :
The user enter the 'store' and search a application.
He looks a da description and rate of the app finaly
by a simple click he starts it out of the store.
The Appstore-program or even a browser download and starts
the script / program / package and runs it.

Such an appstore will make the use of haiku much easyer i think, because
the user finds a lot of programs and information about the program
in a central point.He can easy check for updates or the store tells the user
about an update or automatic updates an app.The store also can manage
apps and programs already downloaded, so you just have to download an app
and the use it offline.

Sorry about my bad english, i try to become better, but it is
hard for me.I hope you understand wath im try to explan you above :D

1) Support to install Haiku on ZFS! ZFS rocks!
2) Support of ZFS installation on setup!
3) Package manager (GUI - Bash)
4) Compilation of packages / Flags. I don't like binary packages :P
5) Support for Kernel Config!
6) Support to read - write UFS ,ZFS ,JFS (Ext2/3 ,NTFS I think already do it)
7) Support for ARM. The reason that I don't install Haiku on Motorola Xoom tablet is that Haiku is not already written for ARM processors!
8) SOS!!! 64bit support! We are one step before 2012!!!
9) Haiku must come without NONE package by default! We must have the ability to choose what we really need on our computers! From editors to players etc.
10) Must follow BSD, Solaris and serious UNIX philosophy! UNIX is alive and very very strong and every day proove that worths!!!

I hope you find this insightful...

First, a log of my experience so far. Note: I have never used beOS, or even heard of it until a few days ago. I have experience in windows, mac, and linux, but not much in mac.

-first heard about it on wikipedia a few days ago

-today, install disk failed to boot on my new Dell Inspiron laptop with Dual-core Athlon CPU, 4GB RAM, ATI Radeon graphics card.

-today, successfully installed in a small partition on my old Pentium 4, tried it out a bit.

Now for my first impression of the pros, cons (aside from general alpha-state bugginess) and a few general comments and suggestions.

Pros:

-lightweight runs, fast even on old hardware

-nice UI, more elegant than the X11 stack of Linux/BSD

-surprisingly, 3D acceleration works better here than on the Debian Linux on my laptop.

-seems to have a strong "breakout potential" of suddenly becoming relevant and mainstream (mainstream in the sense that linux and BSD are mainstream, not necessarily Windows mainstream), if only more focus was put on making high quality native-ui ports of recent opensource software.

Cons:

-Development seems to have misplaced (in my opinion) priorities. Very devoted to getting binary compatibility with 10 year old closed-source software, even if it comes at the expense of focusing on facilitating the porting of recent open-source software.

-I've heard that it's using OpenGL 1.5 or something like that. I'm no expert but I think that means that programs relying on newer versions of OpenGL won't compile, or at least won't run, on haiku.

A suggestion: I think it would be a good idea, while this is in alpha, to get some "infrastructure" ports in place, of shared libraries such as native ports of the gtk+ and the Qt which call directly on haiku's native windowing system, a newer version of OpenGL, etc. so that modern apps can be easily ported later on. In fact, I think that someone has already has made a port of Qt, as part of a full package port of KOffice which I saw on haikuware, so it is possible. I think that more of a focus should be put on that sort of thing than is put on it now, if haiku is ever to become relevant. Without software, the OS will not thrive. If the OS does not thrive, neither will native development. The only way to break the chicken-egg dilemma is through ports, and lots of them. Ironically, the only way to get native development thrive is by making as many ports as possible, in my opinion.

I'm not an expert of course, and not very invested in this, but that's what I think, and you can listen to me, or ignore me, whatever you think is best.