Some good questions. >Hi all, > >I have finished the Keyboard Preference application now. > >There are a few things to do like : > >o Add the pretty icons, I don't actually know how to do this yet; Get with the Creative Design team to draw something. Add it as a resource to your application. Load it as a BBitmap and copy it into your BView. >o Tidy my code up with accessor funtions rather than sticking objects in >the public sections of classes; Tsk Tsk. :-) >o Make sure if the Windows co-ords are off screen, re-position it in the >middle of the screen. Very nice. >o It also may have some constants that are declared elsewhere in the >OpenBeOS project, the kb_settings struct is an example of this, >I don't actually know how to include files like that, it didn't download >when I cvs co'd my teams work. This is something that source control really needs to deal with. >Other than that, it *should* work :) (Thats asking for trouble!) :-) >If people want to test it be my guest, and you can download the binary >here: > >http://www.h2o.demon.co.uk/OpenBeOS_Keyboard_Preference_Panel.zip > >***NOTICE*** > >This file may destroy your life, your BeOS partition, whatever. It >probably won't but this is a beta release and it reads/writes system >files. > >If it does - don't get mad with me - you tried it. > >************ > >Do we have some sort of charter for releasing software? I wasn't too >sure if I was to just email like this, or contact the team leader >first... Sort of. Really the thing to do here is mail your team leader. While everything is accessible (since it is in CVS, after all), I want to give bundles of things to the beta testers... In any case, this was a good opportunity to talk about these things. ;-)