Author |
Message |
casimir
NewBe
Gender:
Joined: 21 Jan 2003
Posts: 4
Location: Vancouver, Canada
|
Posted: Wed Jan 22, 2003 5:22 am Post subject: Want to contribute
|
|
|
|
I apologize for posting 2 in a row, but I figured this needed it's own topic.
I have been reading some forums and talking to some people and I have come to the conclusion that there is a pretty big population of people who want to contribute to BeOS in some form.
Take me for example I really want to help out, I am starting a vancouver based user group but I want to atually help development... but I have no clue how. As I dont have any skill in C++. What do I need to know to help and what needs to be done?? obeos? zeta?
There should be a guide or tutorial... I wll even make on eif provided with the information.
|
|
Back to top |
|
|
Mik
NewBe
Gender:
Joined: 28 Dec 2002
Posts: 4
|
Posted: Wed Jan 22, 2003 9:49 am Post subject:
|
|
|
|
Well you could start learning c++, by buying a book about it One good one I can recommend is The c++ programming language 3th edition written by Bjarne Stroustrup, sometimes it's a bit unclear but it really contains everything about c++. (Bjarne Stroustup is the designer of c++). Also watch the http://www.neo-programmers.com/ site which wants to help starting beos-programmers, but it is, at this time, down. (anyone know the reason?) Also look at the be-book which is a great help for writing the beos-specific code like gui's etc. Also there's a major need for driver writers, the http://www.bedrivers.com/ site has some articles about it. Also if you want start programming for beos make sure you assign to the bedrivertalk, bedevtalk and becodetalk lists(forgot the links).
regards,
Tim
|
|
Back to top |
|
|
Monni the Cat
Pencil Pusher
Gender:
Joined: 28 Sep 2002
Posts: 27
Location: Kaarina, Finland
|
Posted: Wed Jan 22, 2003 11:04 am Post subject: Learning how to program...
|
|
|
|
I think it is a good way to learn to program by using both a basic reference book and examining sources made by others. Then if you notice something you don't understand, you can look it up in the reference book or maybe ask the author or in some online group.
Start by doing something simple that you think will sound useful and then start to add features and remember to make notes why you did something in one way, so when you look at the sources few months later, you still know what every line or paragraph of code does.
|
|
Back to top |
|
|
donan71
NewBe
Joined: 14 Jan 2003
Posts: 5
Location: Ontario Canada
|
Posted: Wed Jan 22, 2003 7:20 pm Post subject: help
|
|
|
|
I emailed Zeta and offered help but Bernd replied saying he only needed backgrounds for the desktops. I guess if you have more experience that i do they may need your help.
|
|
Back to top |
|
|
|