[openbeos] Re: BeAPI++

Hi

I just thought I'd comment, since I'm one of the possible *recruits* that you 
are talkin of.
I've been wanting to join this team for a couple of months, or just contribute 
to the BeOS community in some way.. like most people participating here, I've 
been a BeOS fan since I discovered it (R4). 

This is what's been keepin me from contributing:

1. I want to know what parts are really needed.

2. For those parts, I'd like a little introduction.. I've learned the 
fundamentals of beos, coded a couple of test apps.. got the programming guide 
books and the bible back in 2001.. but since I have but a few hours at a time, 
it would really help to learn some theory for the specific part that needs to 
be done. 

3. Take a car as an example..  I don't wanna go through each part of the engine 
just to find out that pressing the gas will prolly make the engine spin faster. 
If someone were to tell me this, I'd more easily find out for myself how each 
part of the engine makes this happen, and what parts are missing, or 
intentionally left out.

4. Trying to get such directions/guidelines/starter tips from other developers 
isn't the easiest task. All of you prolly got as little time as me, and wish to 
spend that time workin on other things. But even finding out what parts need to 
be worked on isn't the easiset thing, since alot of Haiku developers appear a 
bit hostile to newcomers. I've found the step-by-step guides for simple things 
like getting the cvs tree (I'm new to cvs) very usefull, and very much 
appreciate the people who take time to write such guides.

5. The biggest problem though, is me. Even though I full-heartedly love this 
system, I'm having a hard time dedicating 100% of my concentration/freetime to 
something where I'm not even sure where to begin. Most of the time I end up 
reviewing some already existing software/code for myself and get stuck with 
some silly config scripts or trying to compile some linux game or whatnot. This 
is really my own problem, and I should try to focus and gain some inspiration, 
but I know there's more developers who feel like me, and perhaps you could 
inspire them a bit, or just open a door to that house called Haiku development 
that seems all coosy and nice from the outside.

Don't know it this helps at all, but I'm gonna send this now anyways..

Regards, Linus

PS. I'm tryin to learn how to write drivers, since that's always needed.. but 
it's a slow process for someone with little hardware-coding experience and next 
to noone to get pointers or answers from.. DS.

PS. My dream is to develop a midi/audio sequencer on some system that isn't 
Winblows or bloatnux that would combine the best of my experiences from workin 
with almost every commercial sequencer there is in studios and in garages. I 
found BeOS through some T-Racks newsgroup. DS

Other related posts: