[squeak-dev] Integrating Packages into squeak.

Integrating Packages into squeak.

Commenting on "Overrides in newest Monticellos?"
thread

Why do overides keep cropping up?

In looking a packages, people lose sight
 that each of the packages have to be joined into squeak.

The joining, how is that done?

I don't have a good complete answer to that.

Everytime I have tried it has entailed
 adding to classes more core than my additions.

Some methods are at the very crossroads
 of all the behaviors that a new package wishes to modify.

PasteUpMorph>>mouseDown:  is an example.
Loook at its history.
Its been modified and remodified to accomodate
 new behaviors in other packages.

Menus and menu building methods are another crossroad.
Eventually I have to write something that overides
 the version of an earlier package.
And if my addition is to be removable then what happens?

Shakespeare's Merchant of Venice was required to obtain his fee
 by removing a pound of flesh without spilling a drop of blood.

And he lost all because it could not be done.

So the question of what to do about overides comes down to:
how do you add and remove packages without touching any other package?

Do you know of a way to do that?
Can you tell the Merchant?

Yours in curiosity and service, --Jerome Peace.


     

Jerome Peace wrote on Sun, 13 Jul 2008 19:14:47 -0700 (PDT)
> So the question of what to do about overides comes down to:
> how do you add and remove packages without touching any other package?

Allow more than one version of an object in a single image, where
needed.

> Do you know of a way to do that?
> Can you tell the Merchant?

PIE is nearly 30 years old:

http://portal.acm.org/citation.cfm?id=802792&dl=ACM&coll=GUIDE

It is about time something like that is included as a basic part of
Smalltalk.

-- Jecel