Re: unprotected object - protected object - component ...

Hi Herman

I agree with your hierarchy of protection for objects. We will have to try 
to be very explicit about the level of access in objects (to avoid confusion).

One thing that I really like about the Java approach to design of libraries 
is the consistency in access to members. I think it is essential that we 
try to have a similar standardization to allow for an easy learning curve. 
In Java if you have used it for a few days you can almost predict the 
accessors or data members to be used in objects. This is very convenient.

Anders and I have started to draft the object hierarchy (and name space) 
for typical functions in a mobile robot navigation system. We are working 
on a standard document to give people an impression of the functionality 
and some basic functions in the hierarchy (where the missing entries will 
be filled out gradually by us or other contributors). Hopefully we can 
release a version of the document before July 1. Anders has promised to 
release his communication ... code this week (alpha release). With this and 
the basic hierarchy I hope we can start to build simple systems that can 
form a basis for evaluation of the design and also be a core for added 
functionality for mobility.

--Henrik