seaside-dev May 2014

seaside-dev@lists.squeakfoundation.org

7 participants
11 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

HTTP 302 vs 303
by Philippe Marschall 07 Jun '14

07 Jun '14

Hi I came upon this HN thread [1]. The linked article suggests we should use HTTP 303 instead of 302 (because we want a change from POST to GET). [1] http://insanecoding.blogspot.ch/2014/02/http-308-incompetence-expected.html Cheers Philippe

3 3

Sprint at ESUG
by Philippe Marschall 25 May '14

25 May '14

Hi We're planning to do a sprint this year as well (Friday, Saturday, maybe part of Sunday) but we don't have confirmation for a location yet. Cheers Philippe

1 0

Seaside 3.1.1 released
by Johan Brichau 25 May '14

25 May '14

We are pleased to announce Seaside 3.1.1 [1]. This is a bugfix release for Seaside 3.1 but features a couple of notable enhancements: • Ported to Gemstone 3.1 • Slime is now available on Squeak, Pharo1.4, Pharo2.0 and Pharo3.0 • Gettext is now included in the ConfigurationOfSeaside3 • DateAndTime>>jsonOn: now prints the ISO8601 representation in a string • Issue 783 : Don’t require nesting #object: in #value: in JSON arrays A big thanks to everyone involved for making this release happen. best regards, The Seaside Team [1] https://code.google.com/p/seaside/wiki/Seaside311Changelog

3 5

Jenkins build became unstable: Grease » 20,bleedingEdge,vm #357
by ci-pharo-contribution＠inria.fr 24 May '14

24 May '14

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

1 2

Magritte versions
by Diego Lont 21 May '14

21 May '14

Hi all, We would like to have more communication about the Magritte configuration. We will start by describing the current state, as far as we know it. The current released version of Magritte is 3.1.3. This versions contains the latest changes and is a release version, so should not be changed. Please use #release3.1 in referring to this version, to allow for minor updates and bug fixes to be automatically integrated. The #release3.0 is also maintained, as this refers to #release3.0 of Seaside. And as long as #release3.1 of Seaside is not released on Gemstone, I will maintain this version. There is also versions 3.2. We do not know why this version is created. It uses a duplicate baseline (only the Grease version differs), and no big changes for Magritte are planned (to my knowledge). So we propose to remove this version. If you want this version to be kept, please reply this mail with a reason. Version 3.2 is outdated, but it implies to be more recent than 3.1.3. For the time being I will only remove the 3.2-baseline, as it is duplicate. If I do not receive a mail saying 3.2 should be kept, I will remove this version beginning of June. For development I will create a version 3.1.4. I will also point #development to this version. Discussion on Magritte List. Cheers, Stephan and Diego

2 2

Configuration management Magritte and Pier
by Diego Lont 21 May '14

21 May '14

Hi all, I notice that for Grease and Seaside changes in the versions are always discussed on the Seaside list. Now maybe not all changes should be discussed, but for the major projects, like Magritte and Pier, I would like to have at least an announcement if a change is made in the configuration. To be more exact, I have no idea why version 3.2 was created in Magritte. I cannot find any mail on the list about this version. Secondly I would like people to use release versions of Grease, Seaside, Magritte and Pier as much as possible. I have introduced releases for Grease, Seaside, Magritte and Pier to all have a #’release’. These release “remove” the last index. So for Seaside the current released version is: 3.1.0.2. This means there is a #release3.1, referring to ‘3.1.0.2' and a #release3.0 referring to ‘3.0.12’. When there is an important bug fix, version 3.1.0.3 will be created with this fix, and release3.1 will point to that version. And when 3.1.1 is released, #release3.1 will point to this version. To be completely consistent, there should be a #release3.1.0 as well (referring to 3.1.0.2). There is also a #release3, that is the latest recommended release. As this is different for squeakCommon and gemstone at the moment, this is a special case for Seaside, but normally it would simply point to release3.1. It might be a good idea to introduce #releases to more configurations. Discussion on the Magritte list. Cheers, Diego

1 0

release 3.1.1 ?
by Johan Brichau 18 May '14

18 May '14

Hi there, I guess we can release 3.1.1 https://code.google.com/p/seaside/wiki/Seaside311Changelog With the various bugfixes for Pharo3 and the Gemstone port passing all tests in 3.1.1, it's a better option than using 3.1.0 Any objections? Johan

2 1

Wiki page - Repositories: still current?
by phil＠highoctane.be 18 May '14

18 May '14

On http://seaside.st/community/contribute I see links to Squeaksource. Wouldn't it be more accurate to put the Smalltalkhub links there instead? Phil

2 1

Configuration
by Diego Lont 18 May '14

18 May '14

Hi all, I continued with testing my configurations, as Pier add ons had trouble loading again, due to inconsistent versions of Grease. I am still working on this, as my tester is not complete yet, but in the process I found another (dormant) problem in the configuration. Seaside refers to Swazoo and SPort, and Swazoo refers to SPort. The direct reference to SPort from Seaside has version 2.33 (the more recent) and Swazoo still refers to 2.31. I am willing to fix the configuration if someone gives me access to Swazoo. The stable version should refer to SPort 2.33. Cheers, Diego

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev May 2014