seaside-dev May 2009

seaside-dev@lists.squeakfoundation.org

11 participants
17 discussions

Latest test results
by James Foster 04 Jun '09

04 Jun '09

The latest packages load into Pharo with only the usual WAEnvironmentDefaultHandlersTest errors. James Loaded Seaside-Platform-lr.63.mcz Loaded Seaside-Squeak-Platform-lr.73.mcz Loaded Seaside-Tests-Platform-lr.75.mcz Loaded Seaside-Tests-Squeak-Platform-pmm.18.mcz 175 run, 174 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Core-lr.511.mcz Loaded Seaside-Tests-Core-lr.124.mcz Loaded Seaside-Squeak-Core-lr.78.mcz Loaded Seaside-Tests-Squeak-Core-pmm.22.mcz 513 run, 512 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Canvas-lr.59.mcz Loaded Seaside-Tests-Canvas-jf.26.mcz 589 run, 588 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Session-lr.111.mcz Loaded Seaside-Squeak-Continuation-jf.21.mcz Loaded Seaside-Tests-Session-jf.23.mcz 635 run, 634 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Component-jf.65.mcz Loaded Seaside-Tests-Component-lr.22.mcz 646 run, 645 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-RenderLoop-lr.63.mcz Loaded Seaside-Tests-RenderLoop-lr.8.mcz 646 run, 645 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Tools-Core-jgf.7.mcz 646 run, 645 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Environment-lr.53.mcz Loaded Seaside-Tests-Environment-jf.14.mcz 656 run, 650 passes, 1 expected failures, 0 failures, 5 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testAllTests WAEnvironmentDefaultHandlersTest>>#testDefaultConfig WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate WAEnvironmentDefaultHandlersTest>>#testDefaultTests Loaded Seaside-Tests-Functional-lr.78.mcz Loaded Seaside-Tests-Squeak-Functional-jf.10.mcz 657 run, 653 passes, 1 expected failures, 0 failures, 3 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testDefaultConfig WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate Loaded Seaside-Squeak-Continuation-jf.21.mcz Loaded Seaside-Tests-Squeak-Continuation-lr.8.mcz 675 run, 671 passes, 1 expected failures, 0 failures, 3 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testDefaultConfig WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate Loaded Seaside-Flow-lr.14.mcz Loaded Seaside-Squeak-Flow-lr.9.mcz Loaded Seaside-Tests-Flow-obi.13.mcz 676 run, 672 passes, 1 expected failures, 0 failures, 3 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testDefaultConfig WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate Loaded Seaside-Tools-Web-jf.4.mcz Loaded Seaside-Squeak-Tools-Web-lr.4.mcz Loaded Seaside-Tests-Tools-Web-lr.2.mcz 678 run, 675 passes, 1 expected failures, 0 failures, 2 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate Loaded Seaside-Development-lr.109.mcz Loaded Seaside-Squeak-Development-lr.87.mcz Loaded Seaside-Tests-Development-jf.31.mcz Loaded Seaside-Tests-Squeak-Development-jf.10.mcz 682 run, 679 passes, 1 expected failures, 0 failures, 2 errors, 0 unexpected passes WAEnvironmentDefaultHandlersTest>>#testDefaultCounterDirect WAEnvironmentDefaultHandlersTest>>#testDefaultCounterNavigate Loaded Seaside-Examples-lr.12.mcz 682 run, 681 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Tools-OmniBrowser-lr.6.mcz Loaded Seaside-Squeak-Tools-OmniBrowser-lr.3.mcz 682 run, 681 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded RSS-Core-lr.48.mcz Loaded RSS-Tests-Core-jf.19.mcz Loaded RSS-Examples-jf.17.mcz 691 run, 690 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Javascript-Core-lr.51.mcz Loaded Javascript-Squeak-Core-lr.8.mcz Loaded Javascript-Tests-Core-lr.36.mcz Loaded JQuery-Core-lr.67.mcz Loaded JQuery-Tests-Core-lr.80.mcz Loaded JQuery-UI-lr.34.mcz Loaded JQuery-Tests-UI-lr.48.mcz 935 run, 934 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Scriptaculous-Core-lr.83.mcz Loaded Scriptaculous-Tests-Core-lr.30.mcz Loaded Scriptaculous-Components-lr.81.mcz Loaded Scriptaculous-Tests-Components-lr.21.mcz 978 run, 977 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-HTML5-lr.5.mcz Loaded Seaside-Tests-HTML5-lr.10.mcz 978 run, 977 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-InternetExplorer-lr.4.mcz Loaded Seaside-Tests-InternetExplorer-lr.6.mcz 984 run, 983 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded Seaside-Email-lr.10.mcz Loaded Seaside-Tests-Email-pmm.5.mcz Loaded Seaside-Squeak-Email-pmm.6.mcz 988 run, 987 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes Loaded DynamicBindings-damiencassou.9.mcz Loaded KomServices-gc.19.mcz Loaded KomHttpServer-damiencassou.47.mcz Loaded Seaside-Adaptors-Comanche-lr.40.mcz Loaded Seaside-Tests-Adaptors-Comanche-jf.9.mcz 996 run, 995 passes, 1 expected failures, 0 failures, 0 errors, 0 unexpected passes

5 7

LoadOrder Test for gemstone AND pharo - Seaside Issue 385
by Torsten Bergmann 28 May '09

28 May '09

Hi all, see http://code.google.com/p/seaside/issues/detail?id=385 for details and code is in "LoadOrderTests-tbn.21.mcz" on squeaksource/Seaside29 This is necessary since we want to allow easy testing of latest seaside code in pharo just by evaluating "ScriptLoader loadSeaside29" from within a pharo image. I hope this is OK for gemstone too since for non-pharo it keeps the old comanche packages. Anyone able to confirm this? Thanks Torsten -------- Original-Nachricht -------- > Datum: Wed, 27 May 2009 20:42:41 +0200 > Von: Lukas Renggli <renggli(a)iam.unibe.ch> > An: Torsten Bergmann <astares(a)gmx.de> > CC: renggli(a)gmail.com, damien.cassou(a)gmail.com > Betreff: Re: Seaside29 repository access to fix issue 385 > Hi Torsten, > ... > > > Looks like "LoadOrderTest" is currently more Squeak oriented, but > > with this patch it should easily work also in pharo. > > Keep in mind that this is a script written by the GemStone guys for > testing dependencies between packages and their respective tests. I am > not sure if it is supposed to be used to load Seaside into Squeak/Pharo. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

2 1

Constructing the <head> and <body> tag in Seaside 2.9?
by Conrad Taylor 24 May '09

24 May '09

Hi, how does one construct the <head> and <body> tags in Seaside 2.9 application? Thanks in advance, -Conrad

4 7

export document
by Sebastian Sastre 22 May '09

22 May '09

> self session returnResponse: (WAResponse > document: contents > mimeType: 'application/pdf' > fileName: pdfFile). > this can't be done in 2.9a3 I'm investigating how to do the same in 2.9a3 sebastian

3 4

Re: [Seaside] returning a response in seaside 2.9
by Julian Fitzell 22 May '09

22 May '09

On Wed, May 20, 2009 at 5:28 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > self requestContext response > contentType: WAMimeType textPlain; > nextPutAll: 'Hello World'; > respond We've discussed this before but it kind of doesn't make sense having WAResponse implement #respond, I think, even though it convenient because of cascading. What about: self requestContext respond: [ :response | response contentType: WAMimeType textPlain; nextPutAll: 'Hello World' ] A few more characters ("[ :response | ]") but not many and I think it makes more sense. Obviously #response and #respond would still exist for cases where you don't want to modify the response and respond at the same time. What do you think? Julian

2 4

no "shared configurations" under /seaside/config
by merlyn＠stonehenge.com 21 May '09

21 May '09

According to this: Q: How do I enable or disable the Toolbar? A: This release has the Toolbar enabled by default for all applications. To disable it, open the configuration application (by default at http://localhost:8080/seaside/config ). Under 'Shared Configurations', click on 'Application Defaults'. Under 'Ancestry', find WADevelopmentConfiguration and click the 'X' next to it to remove it. To enable the Toolbar again, simply add WADevelopmentConfiguration again. To enable the Toolbar in a single application, add WADevelopmentConfiguration to that application's configuration screen instead of to 'Application Defaults'. I'm supposed to find "Shared Configurations" under /seaside/config. No such thing. Is this text old? is there better text? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

3 4

Re: [Seaside Commits] Seaside 2.9: Seaside-FileSystem-lr.10.mcz
by Julian Fitzell 21 May '09

21 May '09

This commit seems weird...? On Wed, May 20, 2009 at 11:42 AM, <squeak-dev-noreply(a)lists.squeakfoundation.org> wrote: > Lukas Renggli uploaded a new version of Seaside-FileSystem to project Seaside 2.9: > http://www.squeaksource.com/Seaside29/Seaside-FileSystem-lr.10.mcz > > ==================== Summary ==================== > > Name: Seaside-FileSystem-lr.10 > Author: lr > Time: 20 May 2009, 8:41:57 pm > UUID: 66db219a-4325-4372-9701-baec6d271f76 > Ancestors: Seaside-FileSystem-lr.9 > > - Added WARequestContext>>#respond: and use it whenever possible: > > self requestContext respond: [ :response | > response > contentType: WAMimeType textPlain; > nextPutAll: 'Hello World' ] > > - This change reduces the code size (no temps need to be declared anymore) in most cases and simplifies request handling significantly. Credits go to Julian. > > ==================== Snapshot ==================== > > SystemOrganization addCategory: #'Seaside-FileSystem'! > > WASystemConfiguration subclass: #WAExternalFileLibraryConfiguration > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Seaside-FileSystem'! > > ----- Method: WAExternalFileLibraryConfiguration>>describeOn: (in category 'attributes') ----- > describeOn: config > (config string: #directory) > label: 'Directory'; > comment: 'The base directory to serve files from.'; > default: (SpFilename named: 'xxxDoesNotExists') asAbsoluteFilename directory asString. "#asString on SPFilename" > (config boolean: #listing) > label: 'Allow Listing'; > comment: 'Enable listing of directory entries.'; > default: false! > > ----- Method: WAPackage class>>seasideFileSystem (in category '*seaside-filesystem') ----- > seasideFileSystem > ^ self new > name: 'Seaside-FileSystem'; > description: 'File library that serves files from external directory.'; > addDependency: 'Seaside-Core'; > yourself! > > WAEntryPoint subclass: #WAExternalFileLibrary > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Seaside-FileSystem'! > > ----- Method: WAExternalFileLibrary class>>description (in category 'accessing') ----- > description > ^ 'File Directory'! > > ----- Method: WAExternalFileLibrary>>asAbsoluteUrl:relativeTo: (in category 'private') ----- > asAbsoluteUrl: aFileName relativeTo: aRequest > ^aRequest url copy > addToPath: aFileName; > yourself! > > ----- Method: WAExternalFileLibrary>>contentsOfFile: (in category 'private') ----- > contentsOfFile: aFilename > | stream | > stream := aFilename readStream. > ^[ > stream binary. > stream upToEnd ] > ensure: [ stream close ]! > > ----- Method: WAExternalFileLibrary>>defaultConfiguration (in category 'configuration') ----- > defaultConfiguration > ^ super defaultConfiguration > addParent: WAExternalFileLibraryConfiguration instance; > yourself! > > ----- Method: WAExternalFileLibrary>>directory (in category 'accessing') ----- > directory > | path filename | > path := self preferenceAt: #directory. > filename := SpFilename named: path. > "hack around SPort bugs" > ^(path last = filename separator) > ifTrue: [ SpFilename named: path allButLast ] > ifFalse: [ filename ]! > > ----- Method: WAExternalFileLibrary>>filenameForRequest: (in category 'private') ----- > filenameForRequest: aRequest > | filename basePathUrl | > filename := self directory. > basePathUrl := WAUrl new parsePath: self basePath; yourself. > (basePathUrl relativeTo: aRequest url) do: [ :each | > filename := filename construct: each ]. > ^filename! > > ----- Method: WAExternalFileLibrary>>filesIn:do: (in category 'private') ----- > filesIn: aPath do: aOneArgumentBlock > "this can not be done with SPort" > (WAPlatform current filesIn: aPath) do: [ :each | > aOneArgumentBlock value: (WAPlatform current localNameOf: each) ]! > > ----- Method: WAExternalFileLibrary>>handleFiltered: (in category 'handling') ----- > handleFiltered: aRequestContext > [ self processContext: aRequestContext ] > on: Error > do: [ :error | > aRequestContext responseGenerator > internalError: error; > respond ]! > > ----- Method: WAExternalFileLibrary>>listing (in category 'accessing') ----- > listing > ^ self preferenceAt: #listing! > > ----- Method: WAExternalFileLibrary>>mimetypeForRequest: (in category 'private') ----- > mimetypeForRequest: aRequest > | path | > path := aRequest url path. > ^(path isEmpty or: [ (path last includes: $.) not ]) > ifTrue: [ WAFileLibrary defaultMimeType seasideMimeType ] > ifFalse: [ > | extension | > extension := path last copyAfterLast: $.. > WAFileLibrary mimetypeFor: extension ]! > > ----- Method: WAExternalFileLibrary>>processContext: (in category 'handling') ----- > processContext: aRequestContext > | filename | > filename := self filenameForRequest: aRequestContext request. > (self listing and: [ filename isDirectory ]) > ifTrue: [ self > processDirectory: filename asString "#asString on SPFilename" > context: aRequestContext ] > ifFalse: [ self processFile: filename context: aRequestContext ]! > > ----- Method: WAExternalFileLibrary>>processDirectory:context: (in category 'handling') ----- > processDirectory: aString context: aRequestContext > | contents | > contents := WARenderCanvas builder > fullDocument: true; > rootBlock: [ :html | html title: aRequestContext request url seasideString ]; > render: [ :html | > html heading > level: 1; > with: aRequestContext request url. > html unorderedList: [ > self filesIn: aString do: [ :each | > html listItem: [ > html anchor > url: (self asAbsoluteUrl: each relativeTo: aRequestContext request); > with: each ] ] ] ]. > aRequestContext respond: [ :response | > response > contentType: WAMimeType textHtml; > nextPutAll: contents ]! > > ----- Method: WAExternalFileLibrary>>processFile:context: (in category 'handling') ----- > processFile: aFilename context: aRequestContext > aRequestContext respond: [ :response | > response > document: (self contentsOfFile: aFilename) > mimeType: (self mimetypeForRequest: aRequestContext request) > fileName: (aRequestContext request url path last) ]! > > > _______________________________________________ > commits mailing list > To unsubscribe, email commits-leave(a)lists.seaside.st > http://lists.seaside.st/listinfo/commits >

2 2

2.9 - how to get a stack walkback like 2.8?
by merlyn＠stonehenge.com 21 May '09

21 May '09

2.9a3 doesn't generate a stack walkback by default. I've tried both an install script and a monticello load. What am I doing wrong? I can't develop with 2.9 at all. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

1 1

What is our Mission Statement?
by Lukas Renggli 20 May '09

20 May '09

Seaside Developers, I think we need a clear mission statement on the website to avoid endless discussions like "[Seaside] rails niceties equivalents?". http://producingoss.com/en/getting-started.html#mission-statement In my opinion we should not try to solve all possible problems, but instead focus on specific target that has to be clearly formulated in a mission statement. I am afraid, that if we try to satisfy everybody we become indistinct. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

6 15

What is our Mission Statement?
by Torsten Bergmann 20 May '09

20 May '09

What about "web [programming] with ease - web [programming] with seaside" where programming is optional... or "Seaside - ease in web operation" Bye Torsten -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev May 2009