when i first used beos i notices it looks like windows, and feels like linux, yet is faster than windows, and looks better than linux.
the best think in linux is documentation and commands.
for example i was trying to use the ndis feature. there is nothing to help me. i finally stumbled upon two pages on the internet giving some paths (which were not fully right, i belive).
i think that everything should be documented in a manual. and have something like the manpages of linux.
and more…
even if people would be against this non beosian idea, i think that typing man something if a very very efficient tool. i used to guesswork things. but on linux i have the answers right under my nose. that’s what makes linux easier (i dare say it) that windows. in windows you don’t know what’s going on. you click like a maniac and you learn things. sometimes things don’t work for some reason. in linux there is always some reason, and you check the manpages.
haiku need a manual. and not an html manual, but a plain text one that you can do grep on. just a simple text document at first burried somewhere. and when you type man, it uses cat and grep combined to get the stuff you need.
whoever thinks that man is against beos think again. haiku is not beos, but its half linux. it is linux and beos, yet neither. it’s haiku.
more linux should be mixed up with haiku. at least the nice ideas. when i say more linux, i mean more unix or freebsd or whatever.
there are some nice ideas out there. don’t just stick with beos. some things are worth trying. the gui is beos, but underneath things change.
even more…
it sounds a bit strange but what if a linux user installs haiku and opens the terminal and sees that this is a bit like linux. and a windows user installs haiku and looks closely and realises this is a bit like windows.
when i first used beos i notices it looks like windows, and feels like linux, yet is faster than windows, and looks better than linux.
the best think in linux is documentation and commands.
for example i was trying to use the ndis feature. there is nothing to help me. i finally stumbled upon two pages on the internet giving some paths (which were not fully right, i belive).
i think that everything should be documented in a manual. and have something like the manpages of linux.
and more…
even if people would be against this non beosian idea, i think that typing man something if a very very efficient tool. i used to guesswork things. but on linux i have the answers right under my nose. that’s what makes linux easier (i dare say it) that windows. in windows you don’t know what’s going on. you click like a maniac and you learn things. sometimes things don’t work for some reason. in linux there is always some reason, and you check the manpages.
haiku need a manual. and not an html manual, but a plain text one that you can do grep on. just a simple text document at first burried somewhere. and when you type man, it uses cat and grep combined to get the stuff you need.
whoever thinks that man is against beos think again. haiku is not beos, but its half linux. it is linux and beos, yet neither. it’s haiku.
more linux should be mixed up with haiku. at least the nice ideas. when i say more linux, i mean more unix or freebsd or whatever.
there are some nice ideas out there. don’t just stick with beos. some things are worth trying. the gui is beos, but underneath things change.
even more…
it sounds a bit strange but what if a linux user installs haiku and opens the terminal and sees that this is a bit like linux. and a windows user installs haiku and looks closely and realises this is a bit like windows.
displays information about that <something> in plain text (optionally a gui version with grep capabilities) in the same format as the linux manpages so that is familiar to linux and haiku users for both oses.
plain text is grepable, can pe spoken by voice synthesizer, and is simple to edit.
all final release features should be documented. you could have pictures of gui objects and refer to them in the manual for explaining visual things (here you could have a long discussion of how to do this).
displays information about that <something> in plain text (optionally a gui version with grep capabilities) in the same format as the linux manpages so that is familiar to linux and haiku users for both oses.
plain text is grepable, can pe spoken by voice synthesizer, and is simple to edit.
all final release features should be documented. you could have pictures of gui objects and refer to them in the manual for explaining visual things (here you could have a long discussion of how to do this).
I don’t think we plan to make any man documentation for Haiku features. At most you should expect man pages for imported console tools (coreutils …).
At most you should expect man pages for imported console tools (coreutils ...).
That is probably enough for now.
But I still think that Haiku should have some form of universal documentation like the BeBook, but bigger and better, in GUI format. Should contain everything from kernel minute details to keyboard shortcuts, with how to program with Haiku API in between.
I’m sorry for replying a bit later than I was supposed to.