Seaside 3.0.7
Locked
12
12
 
|
Hi
Nick was kind enough to fix Issue 267 [1] and we once again a nice collection of fixes [2]. Nick ideally needs a 3.0.7 release. I propose he does it :-). [1] http://code.google.com/p/seaside/issues/detail?id=267 [2] http://code.google.com/p/seaside/wiki/Seaside307Changelog Cheers Philippe _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
I wouldn't argue with that:)
Dale ----- Original Message ----- | From: "Philippe Marschall" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Tuesday, March 20, 2012 11:17:11 AM | Subject: [Seaside-dev] Seaside 3.0.7 | | Hi | | Nick was kind enough to fix Issue 267 [1] and we once again a nice | collection of fixes [2]. Nick ideally needs a 3.0.7 release. I | propose | he does it :-). | | [1] http://code.google.com/p/seaside/issues/detail?id=267 | [2] http://code.google.com/p/seaside/wiki/Seaside307Changelog | | Cheers | Philippe | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
OK I created a #development version 3.0.7 in ConfigurationOfSeaside30. Initial testing looks good, but....we have a problem on the horizon.
Esteban tells me that for Pharo 1.4: Kom doesn't work - he uses Zinc instead
he is not "loading anything OB related" - that is the Seaside control panel. In Lukas's CI server builds: Loading Metacello breaks the UI - http://permalink.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside/26492 - again I think down to differences in OB.
(this makes using Metacello tooling in CI builds for updating the ConfigurationOfSeaside30 challenging).
Questions:
Do we make Zinc the default server adapter? 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?
Thoughts?
Nick
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Esteban recommends making Zinc the default on Pharo and Kom on squeak.
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Nick
> Esteban tells me that for Pharo 1.4:
> Kom doesn't work - he uses Zinc instead Nobody should use Kom, it is unmaintained for years and has serious security flaws. I don't think it works properly even on Pharo 1.3. For Seaside we have been using a slimmed down and fixed version KomHttpLight. > Do we make Zinc the default server adapter? Yes, I think Zinc should be the default everywhere. I changed the builds on my CI back to Zinc. We didn't use Zinc for a while because it corrupted images, but that issue seems to be solved now. > 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. Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
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 [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Hi,
I have updated ConfigurationOfSeaside30 and ConfigurationOfSeasideRest. I'm using the following to build the one-click image: 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 <[hidden email]> wrote:
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Yeah, I will need to update the GemStone versions ... if you haven't done it already:)
I'll try to get that done in the next couple of days... Dale ----- Original Message ----- | From: "Nick Ager" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | 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 < [hidden email] > 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 | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
I've started the integration work for Seaside 3.0.7 and it looks like there is a missing package: Seaside-FileSystem-pmm.27 does not exist in: http://www.squeaksource.com/Seaside30LGPL Dale ----- Original Message ----- | From: "Dale Henrichs" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Monday, March 26, 2012 8:48:41 AM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | Yeah, I will need to update the GemStone versions ... if you haven't | done it already:) | | I'll try to get that done in the next couple of days... | | Dale | | ----- Original Message ----- | | From: "Nick Ager" <[hidden email]> | | To: "Seaside - developer list" | | <[hidden email]> | | 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 < [hidden email] > 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 | | [hidden email] | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Nick
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" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | 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 < [hidden email] > 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 | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
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 <[hidden email]> 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:) _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
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" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | 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 < [hidden email] > 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" < [hidden email] > | | To: "Seaside - developer list" < | | [hidden email] > | | 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 < [hidden email] > 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 | | [hidden email] | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Hi Dale,
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 ... Yes I created a branch - it seems that longer term we need a better solution not involving OB . 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 ... I created a 3.0.7 baseline - which seems to be missing from your configuration. The changes to the 3.0.6.1 baseline are: spec for: #'common' do: [
spec group: 'Core' with: #('Base' 'Development' 'RSS-Core' 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' );
=> removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' --- spec for: #'squeakCommon' do: [ spec
group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' ); group: 'Tests' with: #('Comet-Tests-Core' );
group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' 'Javascript-Tests-Core' 'Seaside-Tests-Email' 'Seaside-Tests-Functional' 'Prototype-Tests-Core' 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). ].
=> removed Swazoo and Comache and replaced with Zinc --- spec for: #'pharo' do: [ spec package: 'Seaside-Tests-Email' with: [
spec requires: #('Seaside-Tests-Pharo-Email'). ]. => added 'Seaside-Tests-Pharo-Email'
--- These were the deliberate changes - it seems I inadvertently lost spec for: #'gemstone' do: [ spec package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone';
package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] so I wouldn't recommend taking my 3.0.7 baseline as is.
Thanks for the help Nick _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Sorry about removing the baselines ... I thought I had compared the baselines with the 306 baseline and didn't see any changes ... I probably missed them ... we'll just have to limp along with OB as best we can for now and you've addressed the swazoo and kom issues, so I will make those changes to the config unless you've already done so ...
I've fixed the swazoo bugs for gemstone and zinc hasn't been completely ported to GemStone, so I'll leave swazoo in the GemStone config ... besides, I assume there are folks using Swazoo in production... Dale ----- Original Message ----- | From: "Nick Ager" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 2:40:33 AM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | Hi Dale, | | | | | 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 | ... | | | | Yes I created a branch - it seems that longer term we need a better | solution not involving OB . | | | 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. | | | | I created a 3.0.7 baseline - which seems to be missing from your | configuration. The changes to the 3.0.6.1 baseline are: | | | spec for: #'common' do: [ | | spec | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | --- | | | spec for: #'squeakCommon' do: [ | spec | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' ); | group: 'Tests' with: #('Comet-Tests-Core' ); | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). | ]. | | | => removed Swazoo and Comache and replaced with Zinc | | | --- | | | spec for: #'pharo' do: [ | spec | | package: 'Seaside-Tests-Email' with: [ | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | => added 'Seaside-Tests-Pharo-Email' | | | --- | | | These were the deliberate changes - it seems I inadvertently lost | | | spec for: #'gemstone' do: [ | spec | | package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone'; | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | Thanks for the help | | | Nick | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Nick,
I've restored your changes. WAPharoDebuggerTest>>testNamedTempAt is unexpectedly passing in Pharo1.3. That apparently means "temps can be added to the pharo walkback: "The Pharo debugger API is currently broken. When it's fixed this test will pass again and we can add temps to the Pharo walkback again." Dale ----- Original Message ----- | From: "Dale Henrichs" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 10:07:14 AM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | Sorry about removing the baselines ... I thought I had compared the | baselines with the 306 baseline and didn't see any changes ... I | probably missed them ... we'll just have to limp along with OB as | best we can for now and you've addressed the swazoo and kom issues, | so I will make those changes to the config unless you've already | done so ... | | I've fixed the swazoo bugs for gemstone and zinc hasn't been | completely ported to GemStone, so I'll leave swazoo in the GemStone | config ... besides, I assume there are folks using Swazoo in | production... | | Dale | | ----- Original Message ----- | | From: "Nick Ager" <[hidden email]> | | To: "Seaside - developer list" | | <[hidden email]> | | Sent: Wednesday, March 28, 2012 2:40:33 AM | | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | | | | Hi Dale, | | | | | | | | | | 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 | | ... | | | | | | | | Yes I created a branch - it seems that longer term we need a better | | solution not involving OB . | | | | | | 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. | | | | | | | | I created a 3.0.7 baseline - which seems to be missing from your | | configuration. The changes to the 3.0.6.1 baseline are: | | | | | | spec for: #'common' do: [ | | | | spec | | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | | | | --- | | | | | | spec for: #'squeakCommon' do: [ | | spec | | | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' | | ); | | group: 'Tests' with: #('Comet-Tests-Core' ); | | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | | 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' | | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). | | ]. | | | | | | => removed Swazoo and Comache and replaced with Zinc | | | | | | --- | | | | | | spec for: #'pharo' do: [ | | spec | | | | package: 'Seaside-Tests-Email' with: [ | | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | | | | | | => added 'Seaside-Tests-Pharo-Email' | | | | | | --- | | | | | | These were the deliberate changes - it seems I inadvertently lost | | | | | | spec for: #'gemstone' do: [ | | spec | | | | package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone'; | | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | | | | Thanks for the help | | | | | | Nick | | | | | | _______________________________________________ | | seaside-dev mailing list | | [hidden email] | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Nick
Nick,
With all of those changes to the filelibrary hierarchy, what happens if you install the changes into an existing installation? I haven't looked closely, but presumably there are going to be minimal impacts on existing installations? Just curious, Dale ----- Original Message ----- | From: "Nick Ager" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 2:40:33 AM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | Hi Dale, | | | | | 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 | ... | | | | Yes I created a branch - it seems that longer term we need a better | solution not involving OB . | | | 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. | | | | I created a 3.0.7 baseline - which seems to be missing from your | configuration. The changes to the 3.0.6.1 baseline are: | | | spec for: #'common' do: [ | | spec | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | --- | | | spec for: #'squeakCommon' do: [ | spec | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' ); | group: 'Tests' with: #('Comet-Tests-Core' ); | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). | ]. | | | => removed Swazoo and Comache and replaced with Zinc | | | --- | | | spec for: #'pharo' do: [ | spec | | package: 'Seaside-Tests-Email' with: [ | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | => added 'Seaside-Tests-Pharo-Email' | | | --- | | | These were the deliberate changes - it seems I inadvertently lost | | | spec for: #'gemstone' do: [ | spec | | package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone'; | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | Thanks for the help | | | Nick | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
In reply to this post by Nick
Nick it looks like you haven't updated the ConfigurationOfGrease, but there appear to be new packages for Grease?
Are these supposed to be used or are they just floating around? Dale ----- Original Message ----- | From: "Nick Ager" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 2:40:33 AM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | Hi Dale, | | | | | 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 | ... | | | | Yes I created a branch - it seems that longer term we need a better | solution not involving OB . | | | 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. | | | | I created a 3.0.7 baseline - which seems to be missing from your | configuration. The changes to the 3.0.6.1 baseline are: | | | spec for: #'common' do: [ | | spec | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | --- | | | spec for: #'squeakCommon' do: [ | spec | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' ); | group: 'Tests' with: #('Comet-Tests-Core' ); | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). | ]. | | | => removed Swazoo and Comache and replaced with Zinc | | | --- | | | spec for: #'pharo' do: [ | spec | | package: 'Seaside-Tests-Email' with: [ | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | => added 'Seaside-Tests-Pharo-Email' | | | --- | | | These were the deliberate changes - it seems I inadvertently lost | | | spec for: #'gemstone' do: [ | spec | | package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone'; | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | Thanks for the help | | | Nick | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Running tests in GemStone and there are test errors ... no joy tonight ... I've update Grease config with my best guesses...
Dale ----- Original Message ----- | From: "Dale Henrichs" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 4:31:17 PM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | Nick it looks like you haven't updated the ConfigurationOfGrease, but | there appear to be new packages for Grease? | | Are these supposed to be used or are they just floating around? | | Dale | | ----- Original Message ----- | | From: "Nick Ager" <[hidden email]> | | To: "Seaside - developer list" | | <[hidden email]> | | Sent: Wednesday, March 28, 2012 2:40:33 AM | | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | | | | Hi Dale, | | | | | | | | | | 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 | | ... | | | | | | | | Yes I created a branch - it seems that longer term we need a better | | solution not involving OB . | | | | | | 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. | | | | | | | | I created a 3.0.7 baseline - which seems to be missing from your | | configuration. The changes to the 3.0.6.1 baseline are: | | | | | | spec for: #'common' do: [ | | | | spec | | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | | | | --- | | | | | | spec for: #'squeakCommon' do: [ | | spec | | | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' 'Comet-Examples' | | ); | | group: 'Tests' with: #('Comet-Tests-Core' ); | | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | | 'Comet-Examples' 'Base Tests' 'Development Tests' 'RSS-Tests-Core' | | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' 'Comet-Tests-Core'). | | ]. | | | | | | => removed Swazoo and Comache and replaced with Zinc | | | | | | --- | | | | | | spec for: #'pharo' do: [ | | spec | | | | package: 'Seaside-Tests-Email' with: [ | | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | | | | | | => added 'Seaside-Tests-Pharo-Email' | | | | | | --- | | | | | | These were the deliberate changes - it seems I inadvertently lost | | | | | | spec for: #'gemstone' do: [ | | spec | | | | package: 'Seaside-RenderLoop' with: 'Seaside-RenderLoop.gemstone'; | | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | | | | Thanks for the help | | | | | | Nick | | | | | | _______________________________________________ | | seaside-dev mailing list | | [hidden email] | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
#canPerform: in WATestingMetadataFileLibrary>>fileResourceOf: is not portable...Presumably #respondsTo: is the portable selector?
Dale ----- Original Message ----- | From: "Dale Henrichs" <[hidden email]> | To: "Seaside - developer list" <[hidden email]> | Sent: Wednesday, March 28, 2012 4:57:49 PM | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | Running tests in GemStone and there are test errors ... no joy | tonight ... I've update Grease config with my best guesses... | | Dale | | ----- Original Message ----- | | From: "Dale Henrichs" <[hidden email]> | | To: "Seaside - developer list" | | <[hidden email]> | | Sent: Wednesday, March 28, 2012 4:31:17 PM | | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | | Nick it looks like you haven't updated the ConfigurationOfGrease, | | but | | there appear to be new packages for Grease? | | | | Are these supposed to be used or are they just floating around? | | | | Dale | | | | ----- Original Message ----- | | | From: "Nick Ager" <[hidden email]> | | | To: "Seaside - developer list" | | | <[hidden email]> | | | Sent: Wednesday, March 28, 2012 2:40:33 AM | | | Subject: Re: [Seaside-dev] Seaside 3.0.7 | | | | | | | | | Hi Dale, | | | | | | | | | | | | | | | 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 | | | ... | | | | | | | | | | | | Yes I created a branch - it seems that longer term we need a | | | better | | | solution not involving OB . | | | | | | | | | 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. | | | | | | | | | | | | I created a 3.0.7 baseline - which seems to be missing from your | | | configuration. The changes to the 3.0.6.1 baseline are: | | | | | | | | | spec for: #'common' do: [ | | | | | | spec | | | group: 'Core' with: #('Base' 'Development' 'RSS-Core' | | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | | 'Seaside-Tools-OmniBrowser' 'Seaside-FileSystem' ); | | | | | | | | | => removed: 'Seaside-Swazoo' 'Seaside-Adaptors-Swazoo' | | | | | | | | | --- | | | | | | | | | spec for: #'squeakCommon' do: [ | | | spec | | | | | | group: 'Core' with: #('Zinc-Seaside' 'Comet-Core' | | | 'Comet-Examples' | | | ); | | | group: 'Tests' with: #('Comet-Tests-Core' ); | | | group: 'OneClick' with: #('Base' 'Development' 'RSS-Core' | | | 'Javascript-Core' 'Prototype-Core' 'Scriptaculous-Core' | | | 'JQuery-Core' 'JQuery-UI' 'Seaside-Email' 'Seaside-HTML5' | | | 'Seaside-InternetExplorer' 'Seaside-Examples' 'RSS-Examples' | | | 'Seaside-Tools-Web' 'Scriptaculous-Components' 'Seaside-Welcome' | | | 'Seaside-Tools-OmniBrowser' 'Zinc-Seaside' 'Comet-Core' | | | 'Comet-Examples' 'Base Tests' 'Development Tests' | | | 'RSS-Tests-Core' | | | 'Javascript-Tests-Core' 'Seaside-Tests-Email' | | | 'Seaside-Tests-Functional' 'Prototype-Tests-Core' | | | 'Scriptaculous-Tests-Core' 'Scriptaculous-Tests-Components' | | | 'JQuery-Tests-Core' 'JQuery-Tests-UI' 'Seaside-Tests-HTML5' | | | 'Seaside-Tests-InternetExplorer' 'Seaside-Tests-Examples' | | | 'Seaside-Tests-Tools-Web' 'Seaside-Tests-UTF8' | | | 'Comet-Tests-Core'). | | | ]. | | | | | | | | | => removed Swazoo and Comache and replaced with Zinc | | | | | | | | | --- | | | | | | | | | spec for: #'pharo' do: [ | | | spec | | | | | | package: 'Seaside-Tests-Email' with: [ | | | spec requires: #('Seaside-Tests-Pharo-Email'). ]. | | | | | | | | | | | | | | | => added 'Seaside-Tests-Pharo-Email' | | | | | | | | | --- | | | | | | | | | These were the deliberate changes - it seems I inadvertently lost | | | | | | | | | spec for: #'gemstone' do: [ | | | spec | | | | | | package: 'Seaside-RenderLoop' with: | | | 'Seaside-RenderLoop.gemstone'; | | | package: 'Seaside-Tests-RenderLoop' with: 'Seaside-Tests-Render ] | | | | | | | | | | | | | | | so I wouldn't recommend taking my 3.0.7 baseline as is. | | | | | | | | | Thanks for the help | | | | | | | | | Nick | | | | | | | | | _______________________________________________ | | | seaside-dev mailing list | | | [hidden email] | | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | | | _______________________________________________ | | seaside-dev mailing list | | [hidden email] | | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | | | _______________________________________________ | seaside-dev mailing list | [hidden email] | http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev | _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Hi Dale, #canPerform: in WATestingMetadataFileLibrary>>fileResourceOf: is not portable...Presumably #respondsTo: is the portable selector? Opps, fixed in Seaside-Core-NickAger.768 - I've updated the version in ConfigurationOfSeaside30 Nick it looks like you haven't updated the ConfigurationOfGrease, but there appear to be new packages for Grease? Oh dear I really did a half-arsed job on this. I guess when I tested, I didn't clear my package cache so I brought in the latest Grease anyway without updating the configuration. Presumably you mean new Grease versions rather than packages.
I've update Grease config with my best guesses... Looks good. With all of those changes to the filelibrary hierarchy, what happens if you install the changes into an existing installation? The file library changes shouldn't break any existing installations - existing file libraries will continue working as is. However if people want to use libraries such as twitter bootstrap in which css files expect images to have an 'img' path element prepended then they can use the (awkwardly) named: WAFileMetadataLibrary - http://code.google.com/p/seaside/issues/detail?id=267
Apologies if my attempt at updating the Metacello configurations just appear to be making a lot of unnecessary work for you
Cheers
Nick
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
«
Return to Seaside Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |