seaside February 2005

seaside@lists.squeakfoundation.org

36 participants
45 discussions

Version 2.5b6 for VW is ready
by Bany, Michel 06 Nov '05

06 Nov '05

I just published Seaside 2.5b6 for VW on the public repository. It is based upon Seaside2.5b6-avi.8.mcz 15-Jan-2005 16:15 i.e. the very latest version of 2.5b6. This port includes all the fixes that were discussed here: - file upload - lost halo icons and missing styles Note: I also fixed Seaside 2.5b5 on the public repository. For the fun, I added the Seaside logo on some of the pages. Bundle to load : either SeasideForWebToolkit or SeasideForSwazoo. Enjoy, Michel.

3 4

Nested form tags
by Bany, Michel 04 Nov '05

04 Nov '05

I came accross some weird situation when using a component that is a composition of other components. A subcomponent may in turn be a composition of some more components. To make things even more complex, some deeply nested subcomponents may call some other component. Some of the subcomponents may contain some input html tag and as such will require to be contained in a form html tag. In such a complex construct it may be difficult to decide exactly what component should have the responsibility to generate the form tag. Also, it happened frequently to me that form tags become nested especially when a subcomponent calls another component that happens to be a dialog. Therefore I am making the following suggestion : Seaside should prevent form tags from being nested. It should discard any form tag that occurs within a previously opened form tag. With this in place, I can design a component that needs a form with a form construct knowing that if my component happens to be used inside a form, then my form construct will be discarded. Otherwise my form construct will be preserved. If my component calls a dialog component, the form generated by the dialog component will be discarded if my component happens to be used from inside a form. Michel.

6 6

How to add GLORP to a Seaside application?
by Martin J.Laubach 23 Mar '05

23 Mar '05

I'm afraid I painted myself in yet another corner with GLORP and Seaside. The problem is that glorp does not support nesting of UnitOfWorks. That, together with the highly dynamic behaviour of Seaside applications, leads to my losing much hair... Consider for example a navigation bar with two links, each leading to an editing pane for some database object. On each I have something like MyEditingPane>>renderContentOn: html session beginUnitOfWork. (self confirm: 'Do you want to save that?') ifTrue: [ s commitUnitOfWork ] ifFalse: [ s rollbackUnitOfWork ] Now when the user changes to the other editor pane while the #confirm: is displayed, *boom*, glorp throws an exception. The only way I see out of that is to use UnitOfWorks only when it can't be preempted by the user. But then, don't I lose all the benefits (like in the example above, being able to roll back easily)? My real example is a bit more complicated, so I can't just move the #beginUnitOfWork after the confirm as it's doing the modifications in a #call'ed subcomponent and returns true/false depending on the user hitting a save or revert button. Wrong approach to that problem? mjl

8 11

handler reuse bug? [2.3]
by Michal 01 Mar '05

01 Mar '05

Hi - one of my seaside applications, still running 2.3, has suddenly started to generate dozens of error messages like the one attached to this message. As you can see #collectExpiredHanlders chokes on a mismatch between the content of keysByHandler and handlersByKey, which should never happen. Furthermore, I have never touched that part of seaside in my code. What I *think* is happening is: (i) a spider is generating a biggish load (there were about 3000 handlers when I VNCed into the server and netstat shows a couple of the usual suspects), (ii) seaside is reusing some expired handlers to cope with the incoming session requests, (iii) #collectExpiredHandlers first builds a collection of expired handlers and then unregisters them one by one, but by the time it sends #unregisterExpiredHandler:, the handler has been reused and its key has changed, hence the lookup in #unregisterExpiredHandler: triggers an error. At this point, this is a guess based on various oddities I am seeing when VNC-ing the image. Is it a plausible guess? Has anyone seen anything like that? thanks, Michal ps. when sending me the error msgs, sometimes #printString on a collection of session objects also fails, generating recursive error msgs, with ever longer stacks. On the above hypothesis this would be due to key being swapped in/out while trying to #printString based on the key.

2 2

WADateSelector - invalid date handling
by Dmitry Dorofeev 28 Feb '05

28 Feb '05

Hi I just trying to use WADateSelector as described here: http://www.cdshaffer.com/david/Seaside/DateComponents/ (Thanks Dave!) But when I select 31 feb, i see message You chose 1915-03-03. For 30 feb i got You chose 1915-03-02. The year is fine though :-) Any idea what goes wrong and where ? Seaside is 2.5b7 Thanks, Dmitry Dorofeev

3 4

Accessing the root component from a child one
by Esteban A. Maringolo 28 Feb '05

28 Feb '05

Hi, It is possible to make a call from a child component to a parent component. I mean, from one child (a kind of pane), make the top (the main page) component call another component. Example: WARootComp \-- Child 1 \-- Child 2 I want that when some action is performed at Child 2, it make WARootComp call to other Component. I could have a link (i.e. instVar) from child to parent, but i want to know if there is a more seaside way of doing this, something like topComponent, root component, or alike. Ala topShell in standard views. Thanks in advance. -- Esteban.

2 1

Updating sub-components: where?
by Martin J.Laubach 27 Feb '05

27 Feb '05

Is there a method that is called before a page is being built? I want to update the visual state of my component depending on some global session state, possibly changing/adding some subcomponents. I'm currently doing that in #children, but (a) that is called twice (I guess once for the redirect, once for the real page), and (b) it probably (most certainly?) is not what was intended for #children. Where to do that? mjl

6 6

Tutorial material
by Vincent Foley 25 Feb '05

25 Feb '05

Hi Seaside peiple, I've been playing with Seaside for last couple of weeks, and a friend of mine complained about the lack of a good and thorough tutorial. So I decided that I should stop waiting for someone to do it and take a shot at it. I've now built a rather useless, unsecure but working Seaside application that I am ready to document. I want to know what you think about the stuff that's in there, if I should add things that aren't included, etc. I have a simple login screen, multiple components, call/answer, styles, etc. Let me know what you think I've attached the fileOut of the category. Let me know what you think. Cheers, Vincent -- Vincent Foley-Bourgon Blog: http://www.livejournal.com/~gnuvince [ 6 * 9 = 42 ] whileTrue: [ World run ]

3 3

Seaside/Squeak/Swazoo - how to get going
by Todd Blanchard 24 Feb '05

24 Feb '05

I've setup seaside with komanche in the past using squeak. But Komanche has become really insane to get installed right. So many pre-requisites. I'd say 9 out of 10 times I leave something out in the install chain and have to start over. So I'm sick of komanche. I see swazoo has been ported - is there an adaptor for seaside setup already? What are the packages I need to install and what is the magic incantation to get the server up and running on a port? Thanks, Todd Blanchard

11 19

Help! "Error: key not found"
by Todd Blanchard 24 Feb '05

24 Feb '05

I get this when trying to configure a new app. I've created my own session class, and main page component. I created a new seaside app from config, and set up the overrides. But when trying to get to the first page I get the above message and nothing else.

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside February 2005