seaside March 2007

seaside@lists.squeakfoundation.org

73 participants
98 discussions

Re: [Seaside] Call For Design for the Seaside web site
by Michael Davies 15 Mar '07

15 Mar '07

Okay, as there seems to be interest in re-working the current look, I'll try to produce a working page based on the ideas in the mockup image. This will be over the weekend, so if anyone has any other feedback, please let me know. Avi, do you have access to the original artwork in a form that the Gimp can manipulate? Apologies for posting out of sequence all the time, but I only follow this group by digest. Thanks Michael

2 1

Re: [Seaside] Call For Design for the Seaside web site
by Michael Davies 14 Mar '07

14 Mar '07

Okay, I got my hands dirty... I looked at the existing logo again and I think it's actually very good, so I had a play with the existing seaside page to see if a few tweaks could start to liven it up. I used kuler to touch up the colours - the seaside logo is now in Mediterranean colours rather than North Sea colours! I used Century Gothic from the logo as the headline font, using colours from the palette that I generated in kuler. I copied Samuel's idea of a bottom-of-page navigation bar, and added some other areas of colour to liven the page up. Now I did all this in a simple image-editing package (Seashore by coincidence), so this image isn't great, but I think it shows that there's things that could be done with the existing look. So what do people think? http://mykdavies.seasidehosting.st/resources/seasidepage.png Cheers, Michael

11 12

Scriptaculous & Port Number
by Chris Cunnington 14 Mar '07

14 Mar '07

Hi, If I don't include the port number, when using Scriptaculous, the JavaScript apps freeze up. Foo.com:8080/seaside/scriptaculous And the Counter works. Foo.com/seaside/scriptaculous And The Counter (and all the Ajax) freezes. This is different than the other (Counter, Multi, Store) Seaside apps that work. They are quite happy with Foo.com/seaside/multi Foo.com/seaside/store Foo.com/seaside/counter I don't like having port numbers in the URL pane. What do I have to configure in the image to make it go away? Chris Cunnington

1 0

REPLServer in SqueakSource
by Sebastian Sastre 14 Mar '07

14 Mar '07

Avi, can you publish REPLService on SqueakSource? I found it more useful than squeak map and I'm automatically loading seaside from SqueakSource wich is a requisite of REPLServer. Until I cant load it from SqueakSource I have to load it manually every time. thanks, Sebastian Sastre

2 2

W3C Launches New HTML Working Group
by Klaus D. Witzel 14 Mar '07

14 Mar '07

W3C rethinks HTML/xhtml and this is perhaps a chance for Seasiders to shape a better programmable document markup. See http://www.w3.org/ and - http://www.w3.org/html/wg/ /Klaus

3 7

Seaside as backend of apache
by Sebastian Sastre 14 Mar '07

14 Mar '07

Hi there, I'm trying to use in linux an apache as front end and seaside images (squeak) as backend for some seaside applications. I have to configure a someDomain.com for them and access the applications as subdirs for instance: someDomain.com/KillerApp1 someDomain.com/KillerApp2 They will need to use SSL and probable load balance but for now I've started simple and I want just someDomain.com/KillerApp1 with http. So.. this is probably more an apache issue but is also a realistic seaside production issue so sooner or later we need to deal with this to produce real value with Seaside. I've set the virtual host for that someDomain.com/KillerApp1 like this ... <VirtualHost someInternalIP:80> ServerName www.someDomain.com ServerAdmin admin(a)someDomain.com DocumentRoot /srv/www/someDomain.com/ ProxyRequests Off ProxyPreserveHost On <Location /> Order deny,allow Allow from all ProxyPass http://localhost:9090/seaside/ ProxyPassReverse http://localhost:9090/seaside/ </Location> # <Proxy *> # Order Deny,Allow # Deny from all # Allow from 192.168.1 # </Proxy> <Directory "/srv/www/someDomain.com/"> AllowOverride None Options None Order allow,deny Allow from all </Directory> </VirtualHost> ... here is the access_log's tail after requesting someDomain.com/KillerApp1 from links internet browser in an external network 87.219.84.98 - - [12/Mar/2007:16:10:03 -0300] "GET /seaside/KillerApp1?_k=LmXMZuwW&_s=kQJrsIPTnYrxlcSh&1 HTTP/1.1" 302 - "-" "Links (2.1pre18; Linux 2.6.16.13-4-default i686; 102x23)" 87.219.84.98 - - [12/Mar/2007:16:10:04 -0300] "GET /seaside/seaside/KillerApp1 HTTP/1.1" 200 2440 "-" "Links (2.1pre18; Linux 2.6.16.13-4-default i686; 102x23)" 87.219.84.98 - - [12/Mar/2007:16:10:05 -0300] "GET /seaside/files/WAStandardFiles/externalAnchors.js HTTP/1.1" 200 2440 "-" "Links (2.1pre18; Linux 2.6.16.13-4-default i686; 102x23)" 87.219.84.98 - - [12/Mar/2007:16:10:05 -0300] "GET /seaside/files/WAStandardFiles/misc.js HTTP/1.1" 200 2440 "-" "Links (2.1pre18; Linux 2.6.16.13-4-default i686; 102x23)" 87.219.84.98 - - [12/Mar/2007:16:10:05 -0300] "GET /seaside/files/WAStandardFiles/shortcuts.js HTTP/1.1" 200 2440 "-" "Links (2.1pre18; Linux 2.6.16.13-4-default i686; 102x23)" In the image transcript I can also see that /seaside/ is concatenating more than once. any clue on what is wrong? Sebastian Sastre

7 6

[Swazoo] upwrapFields fix
by Boris Popov 14 Mar '07

14 Mar '07

Michel, The following is a change to preserve query data when POST happens to be made against a URL that contains some (/app?_k=bdwguGGx&14), unwrapFields: aSwazooRequest | waFields | waFields := aSwazooRequest uri queryData copy. aSwazooRequest isPost ifTrue: [aSwazooRequest postData keysAndValuesDo: [:key :field | | value | field filename isNil ifTrue: [value := field value] ifFalse: [value := self waFileClass new. value fileName: field filename. value contentType: field contentType. value contents: field value]. waFields at: key put: value]]. ^waFields -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 http://tinyurl.com/r7uw4 boris(a)deepcovelabs.com CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you.

2 2

Re: [Seaside] Call For Design for the Seaside web site
by Michael Davies 14 Mar '07

14 Mar '07

Hi Lukas, I know it's easier to critique someone else's work than to be original oneself, so I'd like to start by thank you and Samuel for actually trying these ideas out! I know what to look for in visual design but have little creative ability myself... Here's my comments: I like the star idea - would it be better filled with a sandy yellow so it looks more like a starfish? That would also give us two colours to use as highlight colours on the rest of the page (like python.org, flickr.com, and existing seaside.st). To me, the star looks 'wonky' - does it look better upright? But this raises the question of whether it is intended that the "seaside+star" logo be *the* logo for Seaside? The existing "waves+sun+seaside" logo is pretty nice - is it clear that it's not working for us? If we do want to replace it, it would be useful to think about some of the other usages of a logo before committing to a final design: How will the logo be used as a standalone image (eg on the wikipedia page) - what colors will be used? Just the star, or seaside+star with a transparent background? How will the logo be used with extra text for buttons on other pages? (eg there's useful space at the top left for "powered by" or "made with" etc, and at the bottom right for "2.0" or "inside") - it would be useful to have a couple of samples, using a widely available font so that people can make their own if required. On the page design generally I like the layout and use of the space, though there's a lot of different colours and a few different families of fonts used - I think cutting down on both would give a cleaner look. I'd also be interested to see a mockup of one or two of the detail pages to see how the look translates to the rest of the site - what navigation elements remain, how much of the content is available from each page etc. I hope that this feedback is of use to you, Michael

2 1

The session in the debugger
by Philippe Marschall 13 Mar '07

13 Mar '07

Hi One of the most annoying things about Seaside for me is that you can't access the session in the debugger. Often when debugging code that needs to access some session data I find myself writing code like this: aBuggedMethod "some code" session := self session. self halt. "more code" and then restarting the method. I am sick of it. This just sucks. So recently I meant someone with too much time who would like to make a valuable contribution to Seaside. I told him about this and he said he would do it if I find at least 5 people to whom it is important. Personally I don't care how ugly the solution is as long as Seaside still works. It doesn't have to be a general solutions. It can be a very evil changeset that causes famine, plague, small pocks and shortens life by 10 years. That desperately I want it. If you feel the same way raise your hand now. Cheers Philippe

10 16

Re: [Seaside] Seaside as backend of apache
by Dominic Letz 13 Mar '07

13 Mar '07

Hello, current FastCGI timings: on my machine using apache benchmark WAKom allows me to have around 74 requests per second on the example counter (in deployment mode). Using the FastCGI instead of WAKom it comes to 97 requests per second. I still think there is a much higher speedup possible because there is a very high amount of time (around 35%) spent in the primitive socket calls. 97.1% {1620ms} FCGIProtocolVersion1>>requestLoop 50.1% {836ms} FCGIProtocolVersion1>>answerRequest |49.3% {822ms} WAFCGI(WAKom)>>process: | 45.7% {762ms} WAFCGI(WAKom)>>handleRequest: | 45.5% {759ms} WAApplication>>handleRequest: | 45.2% {754ms} WAApplication(WARegistry)>>handleRequest: | 45.2% {754ms} WAApplication>>handleDefaultRequest: | 43.5% {726ms} WASession(WAExpiringHandler)>>handleRequest: | 43.5% {726ms} WASession>>incomingRequest: | 43.5% {726ms} WASession>>responseForRequest: | 42.3% {706ms} WASession>>performRequest: | 42.3% {706ms} WASession>>start: | 41.9% {699ms} WARenderLoopMain>>start: | 41.4% {691ms} WARenderLoop>>run | 41.4% {691ms} WARender>>go | 41.3% {689ms} WARender>>render | 21.3% {355ms} WASession>>respond: | |17.7% {295ms} WASession>>actionUrlForContinuation: | | 16.2% {270ms} WASession>>actionUrlForKey: | | 15.9% {265ms} WAApplication(WARegistry)>>urlForRequestHandler: | | 14.7% {245ms} WAApplication(WARegistry)>>ensureKeyForHandler: | | 14.7% {245ms} WAApplication(WARegistry)>>registerRequestHandler: | | 11.1% {185ms} WAApplication(WARegistry)>>unregisterExpiredHandlers | | |5.6% {93ms} Dictionary>>add: | | | |3.4% {57ms} Dictionary(Set)>>findElementOrNil: | | | | 3.4% {57ms} Dictionary>>scanFor: | | |3.2% {53ms} WASession(WAExpiringHandler)>>isActive | | | 2.4% {40ms} WASession(WAExpiringHandler)>>timeoutSeconds | | 2.5% {42ms} WAExternalID class>>new: | | 2.5% {42ms} WAExternalID>>initialize | | 2.1% {35ms} Character>>to: | 19.7% {329ms} WARender>>buildResponse | 16.8% {280ms} WACounter(WAPresenter)>>renderWithContext: | |16.7% {279ms} WACounter>>renderContentOn: | | 14.5% {242ms} WARenderCanvas(WAHtmlCanvas)>>heading: | | 14.5% {242ms} WAHeadingTag(WATagBrush)>>with: | | 14.2% {237ms} WAHeadingTag(WATagBrush)>>openTag | | 14.1% {235ms} WAHtmlStreamDocument>>openTag:attributes: | | 14.1% {235ms} WAHtmlStreamDocument>>bodyStream | | 14.1% {235ms} WARenderedHtmlRoot(WAHtmlRoot)>>writeOn: | | 13.2% {220ms} WARenderedHtmlRoot(WAHtmlRoot)>>writeHeadOn: | | 8.5% {142ms} WARenderedHtmlRoot>>writeStyle:on: | | |6.4% {107ms} WARenderingContext>>urlForDocument:mimeType: | | | 6.4% {107ms} WARenderingContext>>urlForDocument:mimeType:fileName: | | | 5.1% {85ms} WAApplication(WARegistry)>>urlForRequestHandler: | | | 4.7% {78ms} WAApplication>>baseUrl | | | 2.3% {38ms} WAApplication(WAEntryPoint)>>baseUrl | | | 2.2% {37ms} WAUrl>>addToPath: | | | 2.2% {37ms} ByteString(String)>>findTokens: | | 4.2% {70ms} WARenderedHtmlRoot>>writeScript:on: | | 3.1% {52ms} WARenderingContext>>urlForDocument:mimeType: | | 3.0% {50ms} WARenderingContext>>urlForDocument:mimeType:fileName: | | 2.1% {35ms} WAApplication(WARegistry)>>urlForRequestHandler: | 2.2% {37ms} WARender>>buildDocRoot 41.8% {697ms} FCGIProtocolVersion1>>readRecord: |41.7% {696ms} FCGIProtocolVersion1>>readAnyRecord | 41.7% {696ms} FCGIProtocolVersion1>>readFrom: | 37.0% {617ms} FCGIHeader>>readFrom: | |36.8% {614ms} SocketStream>>uint8 | | 36.8% {614ms} SocketStream>>next | | 36.2% {604ms} SocketStream>>receiveData | | 35.6% {594ms} Socket>>receiveDataSignallingClosedInto:startingAt: | | 35.4% {590ms} Socket>>waitForData | | 35.4% {590ms} Socket>>waitForDataIfClosed: | 4.2% {70ms} FCGIParamRecord>>readFrom: | 3.7% {62ms} ReadStream class(PositionableStream class)>>on: | 3.7% {62ms} ReadStream(PositionableStream)>>on: | 3.7% {62ms} ReadStream(PositionableStream)>>reset 4.8% {80ms} SocketStream>>flush 4.8% {80ms} Socket>>sendData:count: 4.4% {73ms} primitives

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2007