[Seaside-dev] Seaside 3.0.7

Dale Henrichs dhenrich at vmware.com
Tue Mar 27 23:23:51 UTC 2012


Lukas doesn't use Metacello so there's really no telling what get's loaded into his custom images.

I've just loaded your config into a Pharo 1.3 image and cleaned it up ... we're bouncing against the 256 literal limit for Pharo methods, so it will be a bit of fun to monkey with that.

Another pair of eyes and hands on the configuration is helpful so don't sweat it....

I've committed the new version ... and as I've tooled around I noticed that Seaside-Tools-OmniBrowser-lr.26 is not loaded and you've got Seaside-Pharo-Tools-OmniBrowser.pharoOB-NickAger.7 loaded instead of Seaside-Pharo-Tools-OmniBrowser-pmm.9 presumably this is because Lukas' changes breaks OmniBrowser in either Pharo1.3 or Pharo1.4 or is it something else ... OmniBrowser appears to be working in the image so I assume that it's the best we can hope for ... 

Besides the standard Swazoo test failures, the WAPharoDebuggerTest>>testNamedTempAt test failed on first run, but doesn't fail on a second attempt ... something subtle going on there ...

Presumably Swazoo should be removed from the config and someone needs to figure out what's up with kom ... leave it in remove it? replace it with kom lite? I don't use any of these boys in Pharo, so I'm not the best one to make a judgement here. 

Now that the Pharo config is in decent shape, I'll be able to start on the GemStone port tomorrow ...

Dale
----- Original Message -----
| From: "Nick Ager" <nick.ager at gmail.com>
| To: "Seaside - developer list" <seaside-dev at lists.squeakfoundation.org>
| Sent: Tuesday, March 27, 2012 3:46:00 PM
| Subject: Re: [Seaside-dev] Seaside 3.0.7
| 
| 
| Hi Dale,
| 
| 
| I had some problems following the process - I initially used an image
| from Lukas's build server - but AFAICT there is an incompatibility
| between Lukas's version of OB and one the Metacello bootstraps
| itself with which caused the UI to become unusable. However I
| thought I'd recovered from that issue - but clearly not.
| 
| 
| I'm not sure where Seaside-FileSystem-pmm.27 came from. I've search
| my local disk and can't find a version of it.
| 
| 
| Apologies for making your like harder.
| 
| 
| Nick
| 
| 
| 
| On 27 March 2012 19:52, Dale Henrichs < dhenrich at vmware.com > wrote:
| 
| 
| There are some issues with the configuration as well that I am in the
| process of fixing missing version specifications? ... I'll review
| the 'development process notes' and revise them as necessary as I'm
| guessing at what happened ... now that I'm not the only person doing
| the configuration, I need to make sure that the instructions are
| up-to-date:)
| 
| 
| Dale
| 
| ----- Original Message -----
| | From: "Nick Ager" < nick.ager at gmail.com >
| | To: "Seaside - developer list" <
| | seaside-dev at lists.squeakfoundation.org >
| | Sent: Monday, March 26, 2012 4:00:43 AM
| | Subject: Re: [Seaside-dev] Seaside 3.0.7
| | 
| | 
| 
| 
| | Hi,
| | 
| | 
| | I have updated ConfigurationOfSeaside30 and
| | ConfigurationOfSeasideRest.
| | 
| | 
| | I'm using the following to build the one-click image:
| | 
| | 
| | 
| | Gofer new
| | squeaksource: 'MetacelloRepository';
| | package: 'ConfigurationOfSeaside30';
| | load.
| | 
| | 
| | (ConfigurationOfSeaside30 project version: '3.0.7') load:
| | 'OneClick'.
| | 
| | 
| | 
| | 
| | Gofer new
| | squeaksource: 'MetacelloRepository';
| | package: 'ConfigurationOfSeasideRest';
| | load.
| | 
| | 
| | ConfigurationOfSeasideRest project stableVersion load: 'Tests'.
| | 
| | Before we announce the 3.0.7 I'd like to push some Pier updates I
| | have and put those in the Developer image.
| | 
| | 
| | Is there anything else that needs doing? Does Dale want to update
| | ConfigurationOfSeaside30 with Gemstone versions?
| | 
| | 
| | Cheers
| | 
| | 
| | Nick
| | 
| | 
| | On 23 March 2012 18:28, Nick Ager < nick.ager at gmail.com > wrote:
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | > Should we drop the Seaside control panel unless someone steps up
| | > to
| | > create/maintain a version that works on Pharo 1.3, Pharo 1.4 and
| | > Lukas's CI
| | > server?
| | 
| | There are no plans in supporting OB in Pharo 1.4.
| | 
| | 
| | OK as an interim solution in-order to get 3.0.7 released:
| | For Pharo 1.3 we can support the control panel by loading
| | Seaside-Tools-OmniBrowser-lr.25 rather than
| | Seaside-Tools-OmniBrowser-lr.26
| | In Pharo 1.4 we won't load the control panel.
| | In CI builds the control panel will load correctly.
| | 
| 
| 
| | _______________________________________________
| | 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
| 
| 
| _______________________________________________
| seaside-dev mailing list
| seaside-dev at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
| 


More information about the seaside-dev mailing list