... and material. Sometimes we need other things than code in an app... For instance, I'd like to do a BeOS clone of an app that uses: http://clapcrest.free.fr/revol/beos/SmileyWavs.zip but I can't include them in the app, since I don't even know who these loops are copyrighted by (and the app was a shareware) So it would be nice if some audio guy could create / find royalty-free loops like these for my small app :) (mail me off-list of you have something) François. En réponse à philippe.houdoin@xxxxxxx: > "Deej" wrote: > > Along these lines, search out the specs and source code for > > drivers you'd like to see. Gather as much info together as you > > can (emailing hardware manufacturers for info if they'll give > > it), and then ask a driver dev to give it a go. > > Yes, this first phase of any project can be really painfull, and > can consume all coder motivation at same time it consume... time. > > Some good starting points I use to search for documentation, > inspiration or help: > > - Google ;-) > - Former Be Inc. www.be.com and ftp.be.com mirrors > - Linux & *BSD sites: code source, mailings-lists > - SourceForge & Freshmeat, looking at any similar project you can > learn from > - BeDevTalk, BeCodeTalk & BeUserTalk web archives, for any > already known BeOS coding issue, solution, link, etc > - Former BeBugs database even > > For some project, gathering specs, documentation, inspiration, > sample codes or whatever could help *start* the coding take MORE time > than the coding itself... > > -Philippe. > else > >