[Seaside-dev] Seaside 3.1 ready

[Dale Henrichs]

BTW, I'll take a pass through the configurations this afternoon so perhaps I'll get some insight into this when I look at and critique specific configurations...

Dale

----- Original Message -----
| From: "Dale Henrichs" <dhenrich at vmware.com>
| To: "Seaside - developer list" <seaside-dev at lists.squeakfoundation.org>
| Sent: Monday, May 14, 2012 1:00:58 PM
| Subject: Re: [Seaside-dev] Seaside 3.1 ready
| 
| Philippe,
| 
| "If you find a package you don't know look for it in
| ConfigurationOfSeaside31."
| 
| Who is 'you'?
| 
| How do 'you' have a 'package you don't know'?
| 
| Paul gave you the "proper Metacello answer" for how to use project
| references, perhaps you should describe in more detail what you are
| trying to do...
| 
| Dale
| 
| ----- Original Message -----
| | From: "Philippe Marschall" <philippe.marschall at gmail.com>
| | To: "Seaside - developer list"
| | <seaside-dev at lists.squeakfoundation.org>
| | Sent: Monday, May 14, 2012 12:25:18 PM
| | Subject: Re: [Seaside-dev] Seaside 3.1 ready
| | 
| | On Sun, May 13, 2012 at 7:40 PM, Paul DeBruicker
| | <pdebruic at gmail.com>
| | wrote:
| | > On 05/13/2012 09:40 AM, Philippe Marschall wrote:
| | >>
| | >> spec
| | >>        project: 'Seaside Core' with: [
| | >>                spec
| | >>                        className: 'ConfigurationOfSeaside31';
| | >>                        versionString: #'bleedingEdge';
| | >>                        loads: #('Core' );
| | >>                        repository:
| | >> 'http://www.squeaksource.com/MetacelloRepository' ].
| | >>
| | >> Does this actually load the 'Core' group of
| | >> ConfigurationOfSeaside31?
| | >> If so how do I just import package definitions (eg. dependencies
| | >> on
| | >> 'Seaside-Canvas') from ConfigurationOfSeaside31 especially
| | >> considering
| | >> that since ConfigurationOfSeaside31 is the package it's already
| | >> loaded.
| | >
| | >
| | >
| | > I think in your ConfigurationOfXXX if you wanted to load
| | > 'Seaside-Canvas'
| | > and its dependencies (whether that overlaps 'Core' or not) from
| | > the
| | > ConfigurationOfSeaside31 you would put:
| | >
| | >
| | > spec
| | >        project: 'Seaside Canvas' with: [
| | >
| | >                spec
| | >                        className: 'ConfigurationOfSeaside31';
| | >                        versionString: #'bleedingEdge';
| | >                        loads: #('Seaside-Canvas');
| | >                        repository:
| | > 'http://www.squeaksource.com/MetacelloRepository' ].
| | >
| | >
| | > And I think you don't want
| | >
| | >        versionString: #'bleedingEdge';
| | >
| | > either because at some point in time  in the future the
| | > #'bleedingEdge'
| | > could be a different package than what it is today and instead
| | > you
| | > want
| | >
| | >        versionString: #stable;
| | 
| | This isn't really what I want to express. What I want to express
| | is:
| | 
| | "If you find a package you don't know look for it in
| | ConfigurationOfSeaside31."
| | 
| | The #'bleedingEdge' /  #stable doesn't really concern me. We're
| | just
| | talking about the baseline, I set it to a specific version in the
| | version.
| | 
| | Cheers
| | Philippe
| | _______________________________________________
| | seaside-dev mailing list
| | seaside-dev at lists.squeakfoundation.org
| | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| | 
| _______________________________________________
| seaside-dev mailing list
| seaside-dev at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
|