On 16 févr. 04, at 21:22, Julian Fitzell wrote:

> I don't know StORE, so I don't know how similar it is, but it seems to 
> me that you end up always working in a package.  It's not another view 
> for a novice user, they just create a package (or there's a default 
> package, whatever) and all the code you write ends up being in that 
> package.  I don't think novices need to know any more than that.  More 
> experienced folks would need to know that if they want to make changes 
> to the base system, they should actually be in the appropriate base 
> package, etc...
>
>> well.  Would you propose, for example, another browser akin to the 
>> Package Pane Browser?  Personally, if StarBrowser could browse all 
>> components of a Package (as expressed in PackageInfo) then I would be 
>> pretty happy with it.  Maybe this has already been done?
>
> Exactly, the browsers just need to be package aware.  And if you make 
> packages first-class citizens, they would be.  Packages wouldn't be 
> optional features, they're just the things in which classes and method 
> extensions live.

Yeap. and we could just map them to categories :)