seaside-dev March 2011

seaside-dev@lists.squeakfoundation.org

13 participants
10 discussions

Webtester on squeak?
by Lawson English 30 Mar '11

30 Mar '11

When was the last time anyone tested running Webtester with seaside running on squeak? Just tried it with the 4.2 image and its beyond broke, it seems. Lawson

4 8

Problems loading seaside con Pharo 1.1.1
by Hernan Wilkinson 28 Mar '11

28 Mar '11

Hi, sorry if it is a know issue, I have not been reading the list latetly, but I'm having problems loading Seaside on pharo 1.1.1 I'm just doing: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (Smalltalk at: #ConfigurationOfSeaside30) load. and I got two different errors because I tried twice. The first one was an instance var redefinition on a subclass (the inst var name was stream) and the second time I got 'No version found for #stable of ConfigurationOfOmniBrowser' So, beside downloading a Seaside image from the seaside home page, how should I load the latest seaside version on pharo 1.1.1? -- Hernán Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com

2 2

new features in Seaside-REST: multi element matches and or matches
by Philippe Marschall 26 Mar '11

26 Mar '11

Hi The latest version of Seaside-REST supports multi element matches (*argumentName*) and or matches ([option1|option1]). This allows you to write matches like the following: getFile: fileName at: pathTerms fromProject: projectName <GET> <Path: '/projects/{projectName}/*pathTerms*/{fileName}.mcz/[classes|methods]'> You can find more examples and documentation at [1] [1] http://code.google.com/p/seaside/wiki/SeasideRest Cheers Philippe

5 12

[Seaside] Requests & Components Caching
by Avi Shefi 16 Mar '11

16 Mar '11

Hi all, I've taken the time to implement issue 435 and encountered some issues. 1. I have created a caching filter which caches the response according to the request URL using WACache. It uses the request url without the query params (i.e. aRequestContext request url withoutQuery). This causes problems however with WAComponent>>#script, which uses the same URL (without query params) and therefore serves the content of the page (instead of the contents of the #script method). Any suggestions how to solve this? 2. I think it's also important to provide component caching, so that individual components can be cached. (Rational: navigation components that pull data from databases should be cached, instead of generated each time) I guess the way to do this is to add a decoration around a component, and use that as a cache for the component's contents. However, the contents of the component is inserted through a canvas, which writes its contents directly to the returned document. We can use an additional document and get its output specifically for the component caching, however this feel a bit awkward. Any other ideas how to get a component's output so it can be cached? Cheers, Avi.

2 6

Re: [Pharo-project] Fwd: [squeak-dev] Re: SqueakSource down... again
by Tobias Pape 15 Mar '11

15 Mar '11

Dear anyone who wants to try Am 2011-03-15 um 08:05 schrieb Stéphane Ducasse: > It would be nice if somebody would give a try to install this version of squeaksource > > Stef […] >> >> For SqueakSource with a GemStone-Backend, >> look at: http://seaside.gemstone.com/ss/ss2.html >> IIRC, I used ConfigurationOfGsSqueakSource-DaleHenrichs.8.mcz >> to Load it into my Gemstone 2.3. >> >> Please Note, this is tested only for >> >> • GemStone 2.3 >> • Seaside 2.8 >> • Magritte (1) >> >> And Email-support is not working at all. >> Furthermore, Migrating from a “Normal” squeaksource with >> file-based storage requires some administrative effort. Additionally to the restrictions I gave, I will not put much effort into SqueakSource2, but rather: >> >> Nevertheless, I am working on an improved version, >> that shall work with Seaside3.0/Magritte2 on Gemstone 3 (or even 4) >> Email-Support will be back then and I heavily focus on migration. >> However, this code is all untested and I don't expect it to >> be any usable before April, if not May. I just have a very early version sent to a few developers. I will proceed with this SqueakSource3 as soon as possible. It would be nice if someone volunteered to do an “interface lifting” (i.e., UI refreshing) for Squeaksource :) So Long -Tobias

1 0

Re: Enabling cookies causes callback links to incorrectly redirect in Firefox
by Lukas Renggli 13 Mar '11

13 Mar '11

That was a tricky one: Unfortunately the Mozilla engine does prefetching of some "random" links on websites (https://developer.mozilla.org/en/Link_prefetching_FAQ). This aggressive prefixing is a highly controversial topic even in the FireFox community itself, because of all kinds of issues. Now obviously this prefetching is generally something we don't want to happen with Seaside applications as callbacks could unwillingly be triggered. I changed the Seaside code to deny all prefetch requests in WAApplication. This should solve the problem: Name: Seaside-Core-lr.711 Author: lr Time: 7 March 2011, 6:52:15 pm UUID: 57d701cc-b90b-458d-9f7a-cf9a493a9997 Ancestors: Seaside-Core-dkh.710 - added a tester for prefetch requests Name: Seaside-Session-lr.135 Author: lr Time: 7 March 2011, 6:53:50 pm UUID: 07b0af88-64b7-4bcb-8778-d14e448dddd9 Ancestors: Seaside-Session-pmm.134 Lukas -- Lukas Renggli www.lukas-renggli.ch

4 6

[Seaside] Build Process
by Avi Shefi 10 Mar '11

10 Mar '11

Hi there, Having watched the build process for the first time, it looks like there are some complicated steps involved. I have read the MakeRelease document on the Wiki, and I wondered if there's room for further improvements/automation ? If there's one issue that particularly captured my attention, it was the fact that we had to stop further commits to the repository during the build. I'd love to hear your thought about this. Cheers, Avi.

5 15

[ANN] Seaside 3.0.4 release
by Philippe Marschall 05 Mar '11

05 Mar '11

We are pleased to announce the release of Seaside 3.0.4. This is a minor release for Seaside 3.0 that includes performance improvements, small new features and bug fixes. We recommend all users of Seaside 3.0 to update. A changelog is available at [1] Special thanks to Avi Shefi and Dale for making this possible. [1] http://code.google.com/p/seaside/wiki/Seaside304Changelog The Seaside Team

2 2

experimental Pharo 1.2 support
by Philippe Marschall 05 Mar '11

05 Mar '11

Hi Now that 3.0.4 is out I rolled in some changes to support Pharo 1.2. Most of the things can be done with #ifdef (Smalltalk at:) however one thing could not be done this way. I had to move SequenceableCollection >> #sorted: to a package containing only this method (Grease-Pharo11-Core). I'm not entirely sure whether this is really needed. I have a Pharo 1.1 image without this method and it has been running fine for quite some time and all the tests are green. Cheers Philippe

1 0

Seaside 3.0.4...
by Dale Henrichs 04 Mar '11

04 Mar '11

Tomorrow I will pick up the Issue 643 bugfix from Avi and Philippe and verify the fix in GemStone ... Then I will pick up the additional changes that have been made over the last week and then Seaside3.0.4 should be ready to rumba ... Sorry about how long this integration took, but I had several GemStone-related issues that I had to track down... Dale

3 14

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev March 2011