[interfacekit] Re: So, What can one do currently with the A/S and how does one do it?

Thanks, 

I got a reply from Adi just earlier; it doesn't appear to have turned up
on the list for some reason.  Thanks for your post, especially given
your situation.  I hope you're dictating your posts for a secretary /
slave to type for you... :-)

I'm going to spend the next few weeks playing with the server and source
getting to know it and reading the bebook; I've also got to write an
Ethernet driver for the NVIDIA MCP chipset, so I'll be doing that today.

The BeIDE route for development sounds like the path I'd take.  I'm not
a Makefile person.  In fact I've been investigating using VisualStudio
and /or cygwin to cross compile.  SkyOS do it that way.  I just want my
code-completion!

Thanks for the response.

Euan

-----Original Message-----
From: interfacekit-bounce@xxxxxxxxxxxxx
[mailto:interfacekit-bounce@xxxxxxxxxxxxx] On Behalf Of DarkWyrm
Sent: 06 March 2004 13:03
To: interfacekit@xxxxxxxxxxxxx
Subject: [interfacekit] Re: So, What can one do currently with the A/S
and how does one do it?

I was hoping Adi or Gabe might answer this, but seeing how they haven't 
(not a potshot at them, either), I'll try to get you pointed in the 
right direction.

> Clue me in guys, how does developing this operating system component
> work in reality?   Do you all for example develop in BeOS, and run 
> the
> app_server instead of the original Be V5 app?  Do you have to
> serial/remote debug?  My only experience of development in BeOS is
> drivers using BeIDE.  Most debugging has been reliant on serial debug
> output.
It's been set up to run either under R5 or on its own, depening on 
compile-time options. Debugging is done with bdb and print debugging. 
Development environment is up to you. I use BeIDE. IIRC, Gabe uses 
gvim.

> Give me an example of one of your simpler tasks, how and what you 
> used
> to write the code (be ide, Styled edit, Linux, other?)  What you did 
> you
> do for test and verification?
Components that can be easily tested separately were tested using 
custom test apps. Components that couldn't (ServerWindow, for example) 
were tested by temporarily tweaking the server sources to test. We 
haven't used cppunit because things have been in a constant state of 
flux concerning the internal APIs.

> On another note, is the A/S server usable?  Does it run, just not
> functionally complete?  What about the other kits, I can't get a good
> grip on the status and run-ability of the current teams.  What can I
> currently play with, and see for real?  I heard something about 
> builds
> of app_server a while a go.  Are there any recent binary builds?
> Darkwyrm's site (may he rest his fingers in peace) doesn't appear to 
> be
> up according to www.openbeos.org
Somewhat usable. Most of it is just not functionally complete. There's 
a _lot_ to do. Adi could give you a better idea of what can be done in 
its current state. The link on the OBOS site is broken. Try http://
darkwyrm.beemulated.net/ for my website.

--DW

Other related posts: