[Seaside-dev] a note on Seaside30Loader

[Dale Henrichs]

----- "Julian Fitzell" <jfitzell at gmail.com> wrote:

| I was thinking about improving WAPackage a bit along similar lines.
| I'm getting annoyed at having to maintain the dependencies of the
| Pharo- packages. For example, Pharo-Environment has to depend on the
| Pharo versions of all the packages that Environment depends on. If one
| of those packages doesn't have a Pharo version and you later load it,
| you have to go find all the appropriate places and add the new
| dependency. :P
| 
| I was starting to think about adding a method that marks a package as
| an platform extension and making our tools smarter to just know if
| you're loading a Pharo packages, you need to load the Pharo versions
| of all the other dependencies, if they exist.
| 
| Haven't tried to do it yet but thought I'd through it in there since
| you're obviously thinking about similar things.
| 
| Julian

Julian,

Metacello is aimed at doing just what you are proposing to do, so yes they are similar things:)

Seaside30Loader (Metacello) and WAPackage are definitely recording the same kinds of information ... package load order/dependencies, so there probably should be 'database of record' from which the the other representation is derived, so that one doesn't have to manually keep the two representations in sync.

With Metacello, I am able to record dependencies that are gemstone/pharo/squeak-specific ... WAPackage is missing the platform-specific component, consequently at the moment at least Seaside30Loader has 'more information' than WAPackage.

I would think that Metacello could be slipped underneath WAPackage to provide the basic dependency/package information that is used by WAPackage....

anyway, more food for thought,

Dale