seaside-dev August 2014

seaside-dev@lists.squeakfoundation.org

10 participants
32 discussions

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann 16 Jul '18

16 Jul '18

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

3 7

WAAdmin clearConfigurationCaches not working
by Philippe Marschall 23 Dec '14

23 Dec '14

Hi As part of fixing Issue 820 [1] I have to change some configurations. I though that if I do WAAdmin clearConfigurationCaches all the configuration caches should be cleared. However that is not what is happening. #preferenceAt: in WAApplication instances still return the old value. [1] https://code.google.com/p/seaside/issues/detail?id=820 Cheers Philippe

3 10

Jenkins build became unstable: Seaside » 30,development,vm #526
by ci-pharo-contribution＠inria.fr 06 Sep '14

06 Sep '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=30,VERSION=develop…>

1 13

Build failed in Jenkins: Seaside » 20,development,vm #525
by ci-pharo-contribution＠inria.fr 06 Sep '14

06 Sep '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=develop…> ------------------------------------------ Started by upstream project "Seaside" build number 525 originally caused by: Started by upstream project "Grease" build number 392 originally caused by: [URLTrigger] A change within the response URL invocation (log) Building remotely on pharo-contribution-linux64.ci.inria.fr in workspace <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=develop…> Deleting project workspace... Deleting old artifacts from #523 Deleting old artifacts from #522 [vm] $ /bin/sh -xe /tmp/hudson5911874464658631708.sh + dirname Seaside/PHARO=20,VERSION=development,VM=vm + export JOB_NAME=Seaside + bash + wget --quiet -O - get.pharo.org/20+vm Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/stable.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Downloading PharoV30.sources: http://files.pharo.org/sources//PharoV30.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save Seaside --delete-old + ./pharo Seaside.image --version + REPO=http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main + ./pharo Seaside.image config http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main ConfigurationOfSeaside3 --install=development --group=CI [31m[33m =============================================================================== Notice: Installing ConfigurationOfSeaside3 development =============================================================================== [0m[0m[31m==== Startup Error: MessageNotUnderstood: MetacelloVersionConstructor>>load: [0mMetacelloVersionConstructor(Object)>>doesNotUnderstand: #load: ConfigurationOfGettext>>baseline11: in Block: [spec load: #('Base' );... BlockClosure>>ensure: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>with:during: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>setProject:withBlock: BlockClosure>>setProject:withInMetacelloConfig: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>project:with: ConfigurationOfGettext>>baseline11: in Block: [spec blessing: #baseline.... BlockClosure>>ensure: MetacelloVersionConstructor(MetacelloAbstractVersionConstructor)>>with:during: MetacelloVersionConstructor>>specResolverBlock in Block: [:block | self with: versionSpec during: block] OrderedCollection>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:attribute | | blockList | (blockList := self att...etc... OrderedCollection>>do: MetacelloVersionConstructor>>specResolverBlock in Block: [:versionSpec :pragma | (pragma argumentAt: 1)... MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:pragma | ... OrderedCollection>>do: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: in Block: [:versionString :pragmaColl | ... Dictionary>>keysAndValuesDo: in Block: [:assoc | aBlock value: assoc key value: assoc val...etc... Dictionary>>associationsDo: in Block: [:each | each... Array(SequenceableCollection)>>do: Dictionary>>associationsDo: Dictionary>>keysAndValuesDo: MetacelloVersionConstructor>>collectAllVersionsFromVersionPragmasInto:using: MetacelloVersionConstructor>>calculate:project: MetacelloVersionConstructor>>on:project: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: MetacelloVersionConstructor>>load: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

1 13

Jenkins build became unstable: Seaside » 20,bleedingEdge,vm #518
by ci-pharo-contribution＠inria.fr 06 Sep '14

06 Sep '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=20,VERSION=bleedin…>

1 18

Jenkins build became unstable: Seaside » 30,bleedingEdge,vm #518
by ci-pharo-contribution＠inria.fr 05 Sep '14

05 Sep '14

See <https://ci.inria.fr/pharo-contribution/job/Seaside/PHARO=30,VERSION=bleedin…>

1 15

WABuilder and Render Context
by Maximilian Bareis 02 Sep '14

02 Sep '14

Hi, I use WABuilder for creating small chunks of html-Code to test the SVGTags. Unfortunately it is not possible to pass a RenderContext into WABuilder>>render: WABuilder>>render: anObject ^ String streamContents: [ :stream | | context document renderer | ... context := WARenderContext new. ... renderer := self rendererClass context: context. self openDocument: document context: context. renderer render: anObject; flush. self closeDocument: document ] so I would like to change the method and split it up in two methods: WABuilder>>render: ^ self render: anObject withContext: WARenderContext new. and WABuilder>>render:withContext: WABuilder>>render: anObject ^ String streamContents: [ :stream | | context document renderer | ... context := aWARenderContext. ... renderer := self rendererClass context: context. self openDocument: document context: context. renderer render: anObject; flush. self closeDocument: document ] Is that OK and conforming to your development rules? How do I proceed if it is ok to implement? Regards Max

5 10

Re: WABuilder and Render Context
by Stephan Eggermont 29 Aug '14

29 Aug '14

Hi Max, Are you just trying to improve testability here? Or do you need a different kind of rendering context? And do you need to be able to change it in a builder, or is it sufficient to have a WABuilder>>renderContextClass ^WARenderContext that you can override in a WABuilder subclass, similar to the rendererClass? Stephan

2 1

Seaside32 repo
by Johan Brichau 26 Aug '14

26 Aug '14

Hi guys, I arrived at home and have access to a working computer again. So I created a script to copy all the latest package from Seaside31 repo to the Seaside32 repo. Some of those packages should be left out though (Grease, empty html5 package, etc…) and I will thus not copy them or remove them afterwards. Getting back up to speed asap… Johan

3 4

Exploring the WACallbackRegistry: how?
by phil＠highoctane.be 25 Aug '14

25 Aug '14

I'd like to see what's in the callback registry for a given session. How can I do that? TIA Phil

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev August 2014