>> This sounds obvious, I know, but I'm not clear on the whys behind the
>> implementations proposed so far... Avi, what do you want to accomplish
>> with your proposal?
>
> Currently, we "namespace" classes by prefixing them - WAComponent,
> RAPostgresRelation, OBBrowser, etc.  That's fine.  All I'm really 
> looking
> for is a convention for this prefixing such that the tools can tell, 
> just
> as we can, which part is prefix and which part is the "real" class 
> name.
> This would allow them/us to sometimes leave the prefix off if the 
> context
> was obvious (like if every class in the set you're browsing has the 
> same
> prefix).  It's not much, but as you know I like minimal, incremental
> improvement.
>
> It doesn't really matter what the convention is as long as it's
> consistent, but Prefix::Name is aesthetically pretty good.

Yes
What you see is that in VW you have namespace but I'm not convinced 
that they bring
something really worth because you still have to resgiter to reserve a 
namespace name.
So the big part of the gain is solved by the registration