You wouldn't have to create a category to put it in, you'd simply make your package dependant on the VMMaker package.  If you use a class from VMMaker, then your package is dependant on that package.  The first word before the first dash in a category name "is" the package name.  You can't depend on a class, only on another package.  If VMMaker doesn't have a package in your image, you simply create one named VMMaker, then add VMMaker as a required package on your package.  You don't have to change or modify VMMaker classes in any way for your package to depend on them.  You are not adding those classes to your package, you are declaring that your package depends on that other package, that's all.  Classes have no role in dependencies, only Packages, which are derived directly off of the category names.

________________________________

From: squeak-dev-bounces at lists.squeakfoundation.org on behalf of Brad Fuller
Sent: Fri 12/9/2005 5:41 PM
To: The general-purpose Squeak developers list
Subject: Re: What does Squeak application development look like?



Ramon Leon wrote:

>>That's how I use it today.
>>But, what if you want to add classes from other categories,
>>that do not have the prefixed name?
>>For instance, I have an app and all the classes are in the
>>same category. No problem. But, I have a plugin that I want
>>to include in this package, but I want to to stay in another
>>category. It does not have the prefixed name (in your
>>example, it does not have the "CoolProgram" prefix.) How do
>>you add that -- w/o adding that complete category as a
>>required package?
>>   
>>
>
>That's what the dependency mechanism is for, add that other package as a
>dependency of this package, rather than trying to put it in this
>package.  Packages are the proper level of reuse, not classes, so if you
>use one class from another package, then you rightfully depend on that
>other package.
> 
>
Not if I only depend on that one class. I only want to add one class,
not all of the classes in the category. Unless I'm missing something
very basic -- which is entirely possible :-)

What I would like is to add single classes from different categories.
Sure, I could change the category of, let's say, a plugin class. But, I
would like to keep the plugin under the VMMaker-Plugins category, and
not create a new category just to add it to a package.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5168 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20051209/93080c01/attachment.bin