[interfacekit] Re: Open BeOS Interface Kit

Howdy, Uli!

There is definitely a lot of work for this team to do, so help is quite 
welcome.  We'll be doing design and prototyping work for a while, 
hopefully finishing up by the end of the year.  This is going to require 
a lot of documentation since the rest of the team will need to review 
it, and is probably not going to be the most enjoyable thing to do.  
Aside from prototyping some stuff, we're not going to be doing a lot of 
coding until that's done.

Even if that doesn't appeal to you and you'd rather wait until we're 
ready to roll up our sleeves and really dive into coding (which is 
totally fine), we'd be very interested to hear your ideas.  Our research 
will give us a lot of good information, but there will be a ton of holes 
to fill in.

Let me know what you think,

e

>Hi Erik Jakowatz,
>
>on the page of  the Open BeOS project I read that you're working on the
>Interface Kit. I would like
>to support your team by re-writing controls of the BeOS. I didn't work 
on a
>bigger project on the
>BeOS yet, but I know the Interface Kit well. Now I have a lot of 
experience
>in programming in C++
>since it was a big part of my diploma thesis to write a program for 
Windows
>(was the requirement :( ) using
>Visual C++.
>
>I have a lot of ideas concerning the Interface Kit and I think there is 
a
>lot of work to be done. It would
>be nice to join your team or to activate one of the non-active 
Interface Kit
>projects. If you have any
>questions write ma an email.
>
>Regards,
>Uli Wimboeck
>
>

Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams

Other related posts: