symbolic version proof of concept...

> You can complement:
>         using symbolic versions also avoid to change all the configurations when a change happen. You just change the mapping to stable for example.
>         and the guys depending on you do not have to get updated.
> I hope that this is correct
>
> Stef
> On Nov 26, 2010, at 7:47 PM, Dale Henrichs wrote:
>
> > Yes...!
>
> > On 11/26/2010 10:03 AM, Tudor Girba wrote:
> >> Hi,
>
> >> Let me try an explanation.
>
> >> Metacello versions are used for versioning your configurations.
>
> >> However, these numbers do not have any meaning regarding the intended use and context. For example, when we want to specify what is #stable for various combinations of platforms, we need a slightly different kind of versions. Dale calls these the symbolic versions.
>
> >> Cheers,
> >> Doru
>
> >> On 26 Nov 2010, at 18:06, Dale wrote:
>
> >>> Stef, Alexandre,
>
> >>> I know I'm missing something, but I'm not sure what:) I don't think I
> >>> understand the confusing part...I know that I'm too close to the
> >>> soution, so I'll appreciate your patience while you educate me a
> >>> little bit more...
>
> >>> Dale
>
> >>> On Nov 26, 1:04 am, stephane ducasse<[hidden email]>
> >>> wrote:
> >>>> dale
>
> >>>> It would be really nice if you could take 10 min and extract a small but true example describing the problems
> >>>> like that we can paste it in the book chapter :)
> >>>> I'm sure other people will get confused.
> >>>> I think that the key point is to be able to specify that stable is relative to a platform version and that
> >>>> you do not have to write all the way such methods
>
> >>>>>>>> ConfigurationOfMondrian class>>   loadForPharo12
> >>>>>>>> (self project version: 'default') load
>
> >>>>>>>> ConfigurationOfMondrian loadForPharo111
> >>>>>>>> (self project version: '2.1.2') load
>
> >>>> this way you avoid ripple effect and get much more stable (non volatile) specs.
>
> >>>> Stef
>
> >> --
> >>www.tudorgirba.com
>
> >> "Beauty is where we see it."

>
> Dale
> On 11/26/2010 09:29 AM, Alexandre Bergel wrote:
>> Personally, the biggest problem I have with Metacello, is that when something is going wrong, the error messages are not that useful. Several times I had to ask you and the mailing list to know what's going wrong. I had started to work on a support for Metacello in the Monticello browser. I use it and it helps me.
>>
>> Supporting version to platform mapping is important (we are currently being bitten by this). But I spend more time on getting a configuration right than missing the mapping.
>>
>> This is just my personal feeling and opinion.
>>
>> Cheers,
>> Alexandre
>>
>>
>> On 26 Nov 2010, at 14:06, Dale wrote:
>>
>>> Stef, Alexandre,
>>>
>>> I know I'm missing something, but I'm not sure what:) I don't think I
>>> understand the confusing part...I know that I'm too close to the
>>> soution, so I'll appreciate your patience while you educate me a
>>> little bit more...
>>>
>>> Dale
>>>
>>> On Nov 26, 1:04 am, stephane ducasse<[hidden email]>
>>> wrote:
>>>> dale
>>>>
>>>> It would be really nice if you could take 10 min and extract a small but true example describing the problems
>>>> like that we can paste it in the book chapter :)
>>>> I'm sure other people will get confused.
>>>> I think that the key point is to be able to specify that stable is relative to a platform version and that
>>>> you do not have to write all the way such methods
>>>>
>>>>>>>> ConfigurationOfMondrian class>>   loadForPharo12
>>>>>>>> (self project version: 'default') load
>>>>
>>>>>>>> ConfigurationOfMondrian loadForPharo111
>>>>>>>> (self project version: '2.1.2') load
>>>>
>>>> this way you avoid ripple effect and get much more stable (non volatile) specs.
>>>>
>>>> Stef
>>

> > With the 1.0-beta.28 release I am introducing configuration validation and a toolbox.
>
> I will try
>
> > I plan to expand on your initial additions to the Monticello Browser with more toolbox-based support.
>
> That will be very cool. I do not know whether supporting Metacello in the Monticello is the best thing to do (as Stef pointed out). However, it seems to be okay in practice. Once we will reach a fix point on this, I will do a screencast. Metacello has greatly simplified my life :-) We should keep going! :-)
>
> Cheers,
> Alexandre
>
>
>
>
>
> > Dale
> > On 11/26/2010 09:29 AM, Alexandre Bergel wrote:
> >> Personally, the biggest problem I have with Metacello, is that when something is going wrong, the error messages are not that useful. Several times I had to ask you and the mailing list to know what's going wrong. I had started to work on a support for Metacello in the Monticello browser. I use it and it helps me.
>
> >> Supporting version to platform mapping is important (we are currently being bitten by this). But I spend more time on getting a configuration right than missing the mapping.
>
> >> This is just my personal feeling and opinion.
>
> >> Cheers,
> >> Alexandre
>
> >> On 26 Nov 2010, at 14:06, Dale wrote:
>
> >>> Stef, Alexandre,
>
> >>> I know I'm missing something, but I'm not sure what:) I don't think I
> >>> understand the confusing part...I know that I'm too close to the
> >>> soution, so I'll appreciate your patience while you educate me a
> >>> little bit more...
>
> >>> Dale
>
> >>> On Nov 26, 1:04 am, stephane ducasse<[hidden email]>
> >>> wrote:
> >>>> dale
>
> >>>> It would be really nice if you could take 10 min and extract a small but true example describing the problems
> >>>> like that we can paste it in the book chapter :)
> >>>> I'm sure other people will get confused.
> >>>> I think that the key point is to be able to specify that stable is relative to a platform version and that
> >>>> you do not have to write all the way such methods
>
> >>>>>>>> ConfigurationOfMondrian class>>   loadForPharo12
> >>>>>>>> (self project version: 'default') load
>
> >>>>>>>> ConfigurationOfMondrian loadForPharo111
> >>>>>>>> (self project version: '2.1.2') load
>
> >>>> this way you avoid ripple effect and get much more stable (non volatile) specs.
>
> >>>> Stef
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.