[Glass] upgrade seaside image when requiring MetacelloPreview?

[Johan Brichau]

Hi Dale,

You mean the global to set the list of metacello configurations?
I am including glass 9, seaside 3.0.9 and the project's own metacello config.
It's the latter that is referencing other projects (like twitter bootstrap for seaside), which in turn references seaside #stable. However, that will thus upgrade to a later version of seaside, which I do not want. Hence, we use the Metacello preview scripting API, but the upgrade script just takes the plain configuration and loads it, which tries to load seaside 3.1

Now, the use of the #repositoryOverrides in the script did allow me to include an older version of the twitter bootstrap configuration, where it referenced seaside 3.0.x . This made a load using plain metacello possible and all went fine except for the BaselineOfZinc, which I had to remove manually before running any of the upgrade scripts.

In any case, I was quite impressed by the way the upgrade process works. If you have well working process configurations, the process is a walk in the park. Thanks a lot for that.
Apart from dealing with BaselineOfXXX classes, I even think the scripting api can very well fit into the way the script works. What I generally do is create a load method on the class that uses the scripting api. So, if you can provide that parameter to the upgrade script, I think it would be sufficient.

Johan

> On 12 Jan 2014, at 21:28, "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com> wrote:
> 
> Johan,
> 
> There is a global that allows you to set the version of GLASS that is loaded as part of the upgrade. What did you set that as?
> 
> For the next release of 3.1.x and 3.2 I will make sure that we do testing (prior to the release) of Metacello Preview based loads ... 
> 
> It appears that there will need to be some changes  in the upgrade script...
> 
> Dale
> 
> ----- Original Message -----
> | From: "Johan Brichau" <johan at yesplan.be>
> | To: glass at lists.gemtalksystems.com
> | Sent: Saturday, January 11, 2014 8:40:49 AM
> | Subject: [Glass] upgrade seaside image when requiring MetacelloPreview?
> | 
> | Hi Dale,
> | 
> | If one needs the MetacelloPreview to load the application, the
> | upgradeSeasideImage script does not seem to work.
> | Because I need to prohibit an upgrade to #stable Seaside (and
> | others), I am using the MetacelloPreview scripting API to load our
> | project.
> | But when I need to pass the list of configurations to load to the
> | upgrade script, it is using plain Metacello.
> | 
> | I am now trying to perform the loading of the application itself
> | using MetacelloPreview only -after- executing the upgrade script.
> | Taking a look at the upgrade script, I don’t think it does anything
> | else after the loading of the configurations that I would need.
> | Does that sound ok?
> | 
> | In this case, it concerns an upgrade from 3.1.0.2 to 3.1.0.5 but I
> | will be trying the 2.4 to 3.1 upgrade soon too.
> | 
> | best,
> | Johan
> | _______________________________________________
> | Glass mailing list
> | Glass at lists.gemtalksystems.com
> | http://lists.gemtalksystems.com/mailman/listinfo/glass
> |