seaside April 2003

seaside@lists.squeakfoundation.org

23 participants
46 discussions

anchors behaving like buttons?
by Derek Brans 26 Jun '03

26 Jun '03

In Seaside, is there a way to have an anchor tag that will submit a form and perform an action (behaving just like a button)? Thank you, Derek Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com

15 30

inHeadDo:
by Nevin Pratt 13 Jun '03

13 Jun '03

In Seaside 2.21, the renderer has the #inHeadDo: method. For Seaside 2.3, the renderer appears to be significantly changed. Where's the equivalent of #inHeadDo:? Nevin

3 9

Using Dynamic Bindings in Seaside rendering
by Derek Brans 12 May '03

12 May '03

Using Dynamic Bindings you can tell all subcomponents of a component to use that component for different things (like #myMainComponent or #myForm) If you clamp the binding before you render your subcomponents, the bindings seem to propagate all the way down through the component tree, even in the component's callback methods. Here I use it in the render method of an AttributeForm to tell it's subcomponents that it is the attribute form. renderContentsOn: html form: [ #myAttributeForm binding: self. Bindings clamp: [self renderFormContentOn: html]. html submitButtonWithAction: [self submit] text: self submitButtonText] This can help to solve the whole class of problems like containers and top-level components. Derek Brans Nerd on a Wire Web design that's anything but square http://www.nerdonawire.com phone: 604.874.6463 mailto: brans(a)nerdonawire.com

3 6

blank page bug
by Avi Bryant 09 May '03

09 May '03

Ok, so here's the scoop. The problem Nevin and others were reporting with occasional blank pages showing up in 2.3 is not an OS X or VM specific bug - the reason I wasn't seeing it seems to be that my browser was somehow hiding it from me rather than that it didn't exist on my system. The cause of the bug is the implementation of WAProcessMonitor>>timeout. This controls how long one incoming request on a session waits before preempting the previous one in the same session. I had put some tricky code in there to try to avoid waiting for the timeout when resuming a session after debugging, but it seems to have been too tricky, and was sometimes returning 0 seconds when it shouldn't have been, causing requests to be prematurely terminated. At any rate, changing #timeout to simply return the 'timeout' inst var fixes that problem: WAProcessMonitor>>timeout ^ timeout This should be easy for people using 2.3b to change in their images. I was led astray for a long time by another problem, which is that both Safari and IE on OS X frequently fail to connect to the Comanche server at all, leading to "could not display this page" error messages. This only seems to happen when connecting to OS X, from OS X, and only with those browsers (I tried Camino, for example, and it was fine). I have no idea what's going on here - OS X users should simply avoid those browsers until someone figures this out. Note that connecting with those browsers to Seaside running on a linux VM (or possibly even to OS X on another machine) works perfectly, so it shouldn't usually be a problem for deployment, only development. Hopefully this clears things up a bit. Hopefully it also clears the way for a 2.3 release. Has anyone that has been using 2.3b seen any other problems that should be addressed first? Avi

5 8

WATree itemStack returning nil
by Nevin Pratt 29 Apr '03

29 Apr '03

I'm occasionally seeing WATree>>itemStack return nil during runtime. This is resulting in a walkback, although it happens rarely. This is for my wife's site: http://www.bountifulbaby.com It just happened again, and so I know a customer got a walkback in their browser. When I went into the debugger, I could see that this customer had two items in their cart. Hence, this potentially lost us a sale. They hadn't yet completed the portion of "checkout" where they enter their contact info, so I don't know who it was. It doesn't happen very often, but I've seen it before. Nevin

4 13

Seaside not appearing in SqueakMap
by Diego Roig Seigneur 28 Apr '03

28 Apr '03

Hello, I´ve installed and used Seaside without problems in Squeak 3.4, but I´ve installed Squeak 3.5 and couldn´t see Seaside nor Comanche in the list of SqueakMap packages. Instead, I see ComancheNG and SeasideService (for ComancheNG), but both of them seem to be in very experimental status. How can I load plain Comanche and Seaside2 in Squeak 3.5? TIA, Diego Roig Seigneur.

2 1

Mondrian Tables
by diegogomezdeck＠consultar.com 25 Apr '03

25 Apr '03

Hi guys... Attached is Mondrian-Tables (Some objects to render html tables in an easy way). There are a complete set of tests that show (and test ;)) each feature. Also an seaside application is included with some easy-examples. Enjoy it, Diego Gomez Deck

1 0

Handling Errors
by Nevin Pratt 24 Apr '03

24 Apr '03

Avi, I'm guessing that you often subclass WASession in your applications, and that you override #handleError: to not allow the user to 'Debug' the application? Seems onerous to ever give the end user a 'Debug' option with stack walkback in their browser. That should be for development only. Nevin > I'm occasionally seeing WATree>>itemStack return nil during runtime. > This is resulting in a walkback, although it happens rarely. This is > for my wife's site: > > http://www.bountifulbaby.com > > It just happened again, and so I know a customer got a walkback in > their browser. When I went into the debugger, I could see that this > customer had two items in their cart. Hence, this potentially lost us > a sale. They hadn't yet completed the portion of "checkout" where they > enter their contact info, so I don't know who it was. > > It doesn't happen very often, but I've seen it before. > > Nevin

2 1

Web Hit logging with Seaside
by Nevin Pratt 21 Apr '03

21 Apr '03

Anybody got any Seaside web hit logging code they would like to share? I'm about to put my second iteration of my wife's Seaside site into production. One of the things that "broke" when converting to Seaside (on the first iteration) is my old Comanche page hit logging code. Well, I guess the logger didn't "break" per se-- it's just that the standard Seaside URL's are somewhat worthless in the log file. The log file really needs to record the Seaside component being hit instead of the URL. Anyway, logging code isn't hard to write-- it's just a nuisance. So, anybody got any Seaside web hit login code they would like to share? Nevin

3 3

Great use of WATask
by Derek Brans 19 Apr '03

19 Apr '03

A great application of WATask is a Wizard. By wizard, I mean a sequence of components that get called in order. go self call: Step1Component new. self call: Step2Component new. self call: Step3Component new. self call: Step4Component new. Derek Brans Nerd on a Wire Web design that's anything but square http://www.nerdonawire.com phone: 604.874.6463 mailto: brans(a)nerdonawire.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside April 2003