>>
>>>> So the natural follow up would be to go in the direction of
>>>> 	- having a run-time package knowing its class and methods
>>>
>>> Eh, PIs do that, right?
>>>
>>
>> No it queries the system organization this is different (ask avi if 
>> you chat with him).
>
> Well, let me play devil's advocate here a bit.  PI defines a packaging 
> semantics where the package a particular class or method is in, is 
> defined by the system organization.  So, under the PI definition of 
> "package", Göran is correct.  Now, you may prefer a different 
> semantics for the package system (for example, so that you can have 
> classes from multiple packages within one system category), but that's 
> a separate issue.

  My point (and you know it but play the devil advocate if this is fun 
for you) is that the mid-term solution is to stop to rely on category 
conventions and have a real object as package entities.



Goran about your static script: what is the difference between a static 
script and a bundle of package?
For example
SteApp1.2
	is composed of packages
		MW3.2
		TurtleEnvironment10.3

....
So is a script a separate entity, is it a composite? why and what are 
the pros and cons?
I'm a bit afraid to have yet another entity: package, SMpackage, 
Script...

Stef