"Brent Vukmer" <bvukmer at blackboard.com> wrote:
> More generally: I think the projects framework ought to become SqueakMap aware, and vice-versa.  
> 
> --SqueakMap package information could include "projects built using me". 
> --The project loader code could do a lookup of "SqueakMap packages required for me".  
> 
> I think that this could foster neat interaction between people who create Squeak projects, people who build SqueakMap packages, and people who load and play with projects -and- packages.

Well, I don't wish to give Projects "special treatment" in the model.
SqueakMap can install Projects today and in SM1.1 we will have "package
releases" and dependencies with that. If a Project (I don't master them
- obviously you can make isolated Projects etc - have no idea what you
get when you save/load those etc) has dependencies on other packages
then that will be handled as any other dependency.

Or are Projects different in any special way that I am missing?

Another option available in SM1.1 is SMResource which is meant as a
"downloadable something" that doesn't have releases but *does* have a
"current version" (much like packages on SM today in fact). You will be
able to associate these with packages - much like loose attachments.

I am not sure I propose this for Projects but typcially you could then
post a demo Project of Connectors 1.2 as an SMResource and link that
with the package release "Connectors" version 1.2. Such a link will not
have any special semantic meaning - it is just a "clue" to the users.

regards, Göran