seaside-dev May 2011

seaside-dev@lists.squeakfoundation.org

12 participants
17 discussions

Set vs. IdentitySet in WAFileLibrary>>#filenames
by Paolo Bonzini 22 Jun '11

22 Jun '11

Hi, Gwenael Casaccio recently found the following assumption in Seaside while working on an unrelated change to GNU Smalltalk. In WAFileLibrary>>#filenames, you are building strings from selectors: ^self fileSelectors collect: [:each | self asFilename: each] This however is assuming that #fileSelectors (and hence Behavior>>#selectors) returns an Array or a Set. Gwen would like to change Behavior>>#selectors return an IdentitySet. In this case #filenames would return an IdentitySet of strings, which is pretty much unusable. The possible solution is to send #asArray or #asSet before #collect:. Does this seem okay? Can you make the change so that when I finally upgrade to 3.0.x I will not see this issue? Thanks! Paolo

3 4

state of 3.0.5
by Philippe Marschall 09 Jun '11

09 Jun '11

Hi guys Here's the current state of 3.0.5: I saved the images from Jenkins and uploaded them to the web site. The change log has also been updated [1]. Everything but the Metacello configuration seems to work fine. If I load the Metacello configuration into a Pharo 1.2 it tries to load a version of OB that does not work in Pharo 1.2. [1] http://code.google.com/p/seaside/wiki/Seaside305Changelog Cheers Philippe

3 10

Re: [Seaside Commits] Seaside 3.0: JQuery-UI-NickAger.76.mcz
by Lukas Renggli 31 May '11

31 May '11

Thanks for catching that :-) On 31 May 2011 19:04, <squeak-dev-noreply(a)lists.squeakfoundation.org> wrote: > Nick Ager uploaded a new version of JQuery-UI to project Seaside 3.0: > http://www.squeaksource.com/Seaside30/JQuery-UI-NickAger.76.mcz > > ==================== Summary ==================== > > Name: JQuery-UI-NickAger.76 > Author: NickAger > Time: 31 May 2011, 4:04:22 pm > UUID: 83968f99-67e5-4617-ad53-01f76b22657b > Ancestors: JQuery-UI-lr.75 > > changed JQAutocomplete use of #onComplete: to #onSuccess: as JQGetJson no longer supports #onComplete: > > > _______________________________________________ > commits mailing list > To unsubscribe, email commits-leave(a)lists.seaside.st > http://lists.seaside.st/listinfo/commits > -- Lukas Renggli www.lukas-renggli.ch

1 0

#isolate: gone for ever?
by Hernan Wilkinson 27 May '11

27 May '11

Hi all, I just notice that #isolate: is not in the current version of Seaside. I searched the list and found some mails saying it was removed temporarily... but now I see it is not in the seaside book neither. What is the status about it? Is it gone forever? why? is there something to replace it? Thanks! Hernan. -- *Hernán Wilkinson Agile Software Development, Teaching & Coaching Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>*

3 2

registering WADocumentHandlers in WAApplication
by Dale Henrichs 26 May '11

26 May '11

I'm doing some load testing of SqueakSource3 in GemStone and I have discovered that fairly often (nearly every request), a WADocumentHandler for an empty string is stored into the cache of an application. The way that the WACache is setup, you get a unique key generated each time the empty string is stored, however, the object to key map entry (in keysByObject) for the empty string is stomped on ... I guess this doesn't affect Seaside in Pharo, but in GemStone this causes a commit conflict ... Here's a chunk of the stack: 2 WARegistry >> register: @15 line 3 [GsMethod OOP 558534657] 3 WARenderContext >> urlForDocument:mimeType:fileName: @10 line 9 [GsMethod OOP 521811457] 4 WAContentElement >> document:mimeType:fileName: @3 line 2 [GsMethod OOP 145453569] 5 WAContentElement >> document:mimeType: @2 line 2 [GsMethod OOP 145452801] 6 WAContentElement >> document: @3 line 2 [GsMethod OOP 145453825] 7 ComplexBlock in WAHtmlRoot >> writeStylesOn: @9 line 6 [GsMethod OOP 148753921] 8 ComplexBlock in Set >> do: @4 line 11 [GsMethod OOP 9659649] 9 ComplexBlock in KeyValueDictionary >> keysDo: @3 line 7 [GsMethod OOP 2280705] 10 KeyValueDictionary >> keysAndValuesDo: @25 line 21 [GsMethod OOP 2283265] 11 KeyValueDictionary >> keysDo: @4 line 6 [GsMethod OOP 2280705] 12 Set >> do: @5 line 11 [GsMethod OOP 9659649] 13 WAHtmlRoot >> writeStylesOn: @12 line 3 [GsMethod OOP 148753921] 14 WAHtmlRoot >> writeHeadOn: @6 line 6 [GsMethod OOP 148748545] 15 WAHtmlRoot >> openOn: @3 line 4 [GsMethod OOP 148756225] 16 WADocument >> open: @3 line 4 [GsMethod OOP 146206721] 17 WARenderPhaseContinuation >> processRendering: @25 line 28 [GsMethod OOP 180412673] When I'm hitting the system real hard, the commit conflicts can severely impact performance ... over an empty string:) I am tempted to change the #store: algorithm in WACache to first do a lookup in the keysByObject map to see if there is an existing key and if so, reuse the key... At this point in time, I haven't looked at the impact on the aging algorithms with respect to the WADocumentHandler nor have I looked at whether there really does need to be a unique WADocumentHandler or not ... Perhaps there's an official way to do this in which case, perhaps WARenderContext >> urlForDocument:mimeType:fileName: should be changed... I'll do some experiments tomorrow to see if things break or not. Either way, though I think that the current behavior is probably a bug ... Dale

3 5

ESUG SummerTalk - Fuel, binary object serializer
by Martin Dias 24 May '11

24 May '11

Hi folks. I am really happy to announce that ESUG is sponsoring me for Fuel development through the ESUG SummerTalk. I am Martin Dias, a student at Buenos Aires, Argentina. The idea behind this SummerTalk is to implement Fuel, a binary, fast and general-purpose object graph serializer in Pharo<http://www.pharo-project.org/>. It is based on VisualWorks' Parcels ideas. Actually, the project has already started since several months. Tristan Bourgois and I started with the project while doing an internship with RMoD, INRIA <http://rmod.lille.inria.fr/web/pier>. Since a couple of months, Mariano Martinez Peck <http://marianopeck.wordpress.com/> joined the team, and now he is the official mentor in the SummerTalk. ESUG website for SummertTalk: http://www.esug.org/wiki/pier/Promotion/SummerTalk/SummerTalk2011 The website with all the necessary information is here: http://rmod.lille.inria.fr/web/pier/software/Fuel It even includes slides explaining the algorithm. In addition, a paper is in progress. For the moment, Fuel already provides the following features: - Fast pickle format. It is much faster to materialize than to serialize. - Correctly support class reshape (when the class of serialized objects has changed). - Serialize ANY kind of object. For the moment there is no object to our knowledge that we cannot serialize and materialize. - Be able to completely serialize classes and traits (not just a global name). - Support cycles and avoid duplicates in the graph. - Integration to Moose <http://www.moosetechnology.org/> with an extension to export and import their models. - Detection of globals: for example if you serialize Transcript, it is not duplicated and instead managed as a global reference. - Solve common problems like Set rehash. - Buffered writing: we use a buffered write stream for the serialization part (thanks Sven!). - No need of special support from the VM. - Try to have a good object oriented design. - Well tested (about 120 tests, for the moment). - Large set of benchmarks (even benchmarks for Moose extension). And of course, there are a lot features for the future. You can see some of them in the website and some in the issue tracker: http://code.google.com/p/fuel/issues/list We really appreciate all kind of feedback and comments. If you want to try it, check in the website how to do it. It is extremely easy. Once again, I want to thank a lot to ESUG for sponsoring the project. I plan to create a "news" section in the website with some RSS. I will keep you informed. Best regards, Martin

1 0

Seaside 3.0.5 configurations and OB in Pharo 1.2
by Philippe Marschall 22 May '11

22 May '11

Hi The ConfigurationOfSeaside30 in the Seaside30 repository seem to load a version of OB that does not work in Pharo 1.2. The one that works for me is from [1]. [1] http://source.lukas-renggli.ch/omnibrowser/ Cheers Philippe

2 1

Seaside-Benchmark
by Philippe Marschall 22 May '11

22 May '11

Hi There's a new package in the addions repository [1] called 'Seaside-Benchmark'. It contains a few classes to help benchmarking Seaside applications. There are two request handlers, one intended to stress the server and server adatpor, one intended to exercise the Seaside rendering code. In addition there's a session class giving predictable continuation keys so the URLs for exercising a counter with session cookies look like this: http://127.0.0.1/counter http://127.0.0.1/counter?_k=1&1 http://127.0.0.1/counter?_k=3&1 … [1] http://www.squeaksource.com/Seaside30Addons Cheers Philippe

1 0

Seaside-Gettext
by Johan Brichau 22 May '11

22 May '11

Hi, I am using Seaside-GetText and noticed that the 'pot' template exporter was not picking up the strings to which #seasideTranslated is sent. This message is handy for translating attributes, while the #translate: message is targeting the inner text of a markup node. For example: html jQuery this editable ... submit: 'ok' seasideTranslated; cancel: 'cancel' seasideTranslated; ... So, I went ahead and added support to the appropriate method (see code below). Is there any change of seeing this in the distributed package? And if I can help to do that, let me know. cheers, Johan ---- translatedArguments "self new translatedArguments" | searcher currentClass result innerMatchHandler matchHandler1 matchHandler2 | currentClass := WAValueHolder with: nil. result := GROrderedMultiMap new. innerMatchHandler := [ :node :literal | | key | key := MethodReference class: currentClass contents selector: node methodNode selector. result at: key add: literal value ]. matchHandler1 := [ :node :answer | | firstArgument | firstArgument := node arguments first. firstArgument isLiteral ifTrue: [innerMatchHandler value: node value: firstArgument]]. matchHandler2 := [ :node :answer | node receiver isLiteral ifTrue: [innerMatchHandler value: node value: node receiver]]. searcher := RBParseTreeSearcher new matches: '`@object translate: `#string' do: matchHandler1; matches: '`@object translate: `#string to: `@arg' do: matchHandler1; matches: '`#string seasideTranslated' do: matchHandler2; matches: '`#string seasideTranslatedTo: `@arg' do: matchHandler2; yourself. BrowserEnvironment new classesAndSelectorsDo: [ :class :selector | (searcher canMatchMethod: class >> selector) ifTrue: [ | tree | (tree := class parseTreeFor: selector) notNil ifTrue: [ currentClass contents: class. searcher executeTree: tree ] ] ]. ^ Array streamContents: [ :stream | result keysDo: [ :key | stream nextPut: key -> (result allAt: key) ] ]

2 3

Problem with continuations/flow.
by Tobias Pape 19 May '11

19 May '11

Hi. Calling the following: testCC self inform: 'A'. self wait: [ :cc | self inform: 'B: ', ( self session actionUrlForContinuation: cc). self answer]. self inform: 'C'. self answer. allways results in an error: Error: This block accepts 1 argument, but was called with 0 arguments. In WASession>>handleFiltered: handleFiltered: aRequestContext | key continuation | key := aRequestContext request fields at: self actionField ifAbsent: [ ^ self start ]. continuation := continuations at: key ifAbsent: [ ^ self unknownRequest ]. continuation value at the last line. Continuation is outerContext: GRPharoPlatform>>seasideSuspendFlowDo: startpc: 54 numArgs: 1 So Long, -Tobias

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev May 2011