[Seaside-dev] a note on Seaside30Loader

[Dale Henrichs]

Next week I plan to add some new features to Metacello that will make the Seaside30Loader packages specs a little bit cleaner. So I just wanted to give you guys a heads up that I'll be making major changes to the structure of Seaside30Loader over the next week or so.

If you've taken a look at the Seaside30Config, you may have seen a series of lines like the following in the packages spec:

    merge: 'Seaside-Canvas' requires: { 'Seaside-Pharo-Core'. };
    merge: 'Seaside-Session' requires: { 'Seaside-Pharo-Core'. };
    merge: 'Seaside-Component' requires: { 'Seaside-Pharo-Core'. };
    merge: 'Seaside-Tools-Core' requires: { 'Seaside-Pharo-Core'. };
    merge: 'Seaside-Environment' requires: { 'Seaside-Pharo-Core'. };

They are necessary to get Seaside-Pharo-Core loaded correctly with the current version of Metacello. I've been thinking about alternatives over the last few days and have finally come up with a solution to the  problem that has the side effect of eliminating the need for groups. When I'm done the custom load expression will look more like the following:

    Seaside30Config
      load: 'development'
      group: { 'Seaside-Development'. 'Seaside-Tools-OmniBrowser'. 
               'Seaside-Email'. 'Scriptaculous-Core'. }
      filterTranscript: false
      runTests: true

Anyway, once I've added the new features to Metacello, I'll be changing Seaside30Loader to use the new features and at that point in time, Seaside30Loader will require version 0.17 of Metacello...

Dale