seaside June 2004

seaside@lists.squeakfoundation.org

30 participants
54 discussions

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

[BUG] WAHtmlRenderer>>submitButtonWithAction:image:
by Lukas Renggli 30 Jun '04

30 Jun '04

Hi Avi, the callback of #submitButtonWithAction:image: is never evaluated. There seems to be a problem parsing the request fields, that look slightly different with images. Sorry, I have no fix ready :( Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org

1 0

[VW][BUG][FIX] WAWalkback>>renderObject:labelled:on:
by Lukas Renggli 29 Jun '04

29 Jun '04

Hi, WAWalkback>>renderObject: anObject labelled: aString on: html | objectString | [objectString := anObject printStringLimitedTo: 100] on: Error do: [objectString := '<font ...']. html tableRowWithLabel: aString column: objectString. should be WAWalkback>>renderObject: anObject labelled: aString on: html | objectString | [objectString := anObject printStringLimitedTo: 100] on: Error do: [:err|objectString := '<font ...']. html tableRowWithLabel: aString column: objectString. else VisualWorks raises "Unhandled exception: This block expects 0 argument(s)". Maybe it would be good practice to add the block-variable in the seaside version as well. One can find the occurrences using: ``@block on: ``@class do: [ ``@stmts ] Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org

1 0

RE: [Seaside] [VW] Custom Server Configuration
by Bany, Michel 29 Jun '04

29 Jun '04

> Hi, > > I would like to make my VisualWorks Seaside web-app manage all the > path-information on its own and to let it appear in the root, without > using any external tool like Apache to rewrite the url: > > http://localhost:8080/?_s=TOAZSOrdyJEZlDnS&_k=hZkCbQvC > > How do I create such a web-server in VisualWorks? VisualWave is so > terribly complicated compared to Commanche or Swzaoo :( Hi Lukas, You may want to try this. Not exactly what you are looking for, but close. Seaside.WADispatcher>>basePath: newPath | base | basePath := newPath. base := (newPath notEmpty and: [newPath last = $/]) ifTrue: [newPath] ifFalse: [newPath, '/']. entryPoints keysAndValuesDo: [:key :component | component basePath: base, key] VisualWave.WebSiteResolver>>fileServletClass ^ Seaside.SeasideServlet Michel.

1 0

no HTML entities for 8bit characters in UTF-8 encoding
by Kamil Kukura 29 Jun '04

29 Jun '04

In order to have UTF-8 encoding working, there must be no expansion to html entities for characters over 128. I mean HtmlCharacters collection in WAAbstractHtmlBuilder. In fact, it is only okay for HTML's default ISO-8859-1 (western europe) enconding. Here is what I have for international texts. I have derived WALocaleComponent from WAComponent which has only #renderClass modified so it uses WALocaleHtmlRenderer. Such renderer has method #textOf: which looks to class' internal dictionary of texts according to given symbol. This dictionary is fed from XML file like: <text id="buttonSend">An Unicode text encoded in UTF-8</text> However, I need one more method because I need handle cases such as: html submitButtonWithText: (html getTextOf: #buttonSend) .. just my contribution to i18n -- Kamil Kukura

5 18

RE: [Seaside] Problems on VW with WebToolkit
by Bany, Michel 28 Jun '04

28 Jun '04

Hi Marco, > but my problem is that everytime I want to access a seaside > app I get an debug > window telling me: "DNU #charsetEncoder" raised in > IM_ApplicationWWWFormUrlEncoded>>decodeDataOder:seperator:. I just gave it a try with VW 7.1 and did not get that. Are you running VisualWorks®, 7.1 of March 19, 2003 ? charsetEncoder is an instance method in IM_ApplicationWWWFormUrlEncoded charsetEncoder charsetEncoder == #uninitialized ifTrue: [self initializeCharsetEncoder]. ^charsetEncoder. Do you have #initializeCharsetEncoder in your image ? Michel.

2 1

components and iframes ?
by Romain Robbes 28 Jun '04

28 Jun '04

Hi all, We are working on an application in which we'd like to have components refreshed independently in the same window. So we wanted to embed these components in iframes, and have some javascript to refresh them periodically. We thus started to do stuff in this way, using seaside's #urlForAction: method to get the src parameter of the iframe tag, but we have a problem, which is that seasides does not generate only the component, but a whole application page when the browser fetches the url. Hence we have an infinite loop of iframes ... So do you think it would involve significant work to allow this behavior ? Thanks in advance, Cyril & Romain

2 1

RE: [Seaside] Problems on VW with WebToolkit
by Bany, Michel 28 Jun '04

28 Jun '04

> I just found on one of my CDs a VW 7. Wanted to run Seaside > on it but I can't download a working configuration. WebToolkit 7.2 is required. When you load Seaside-WebToolKit from the public store you get a warning message telling you that you need 7.2. But you can disregard this warning and continue. I you want to run under 7.1, you will be lacking a few features like uploading files into Seaside. > Is there any trick I've missed? I tried to load some of the > WebToolkit versions, but it was always broken. Broken, in what way ? Here is how you should proceed. 1. Launch a vanilla VW 7.1 2. Load StoreForPostgres 3. Connect to the public store 4. load bundle Seaside-WebToolKit making sure you always select the most recent version numbers (Webtoolkit gets loaded automatically) > Do I really have to download a whole new 7.2? Michel.

2 1

Problems on VW with WebToolkit
by Marco Paga 28 Jun '04

28 Jun '04

Hi. I just found on one of my CDs a VW 7. Wanted to run Seaside on it but I can't download a working configuration. WebToolkit 7.2 is required. Is there any trick I've missed? I tried to load some of the WebToolkit versions, but it was always broken. Do I really have to download a whole new 7.2? Regards Marco

1 0

[VW] Custom Server Configuration
by Lukas Renggli 28 Jun '04

28 Jun '04

Hi, I would like to make my VisualWorks Seaside web-app manage all the path-information on its own and to let it appear in the root, without using any external tool like Apache to rewrite the url: http://localhost:8080/?_s=TOAZSOrdyJEZlDnS&_k=hZkCbQvC How do I create such a web-server in VisualWorks? VisualWave is so terribly complicated compared to Commanche or Swzaoo :( Thanks, Lukas -- Lukas Renggli http://renggli.freezope.org

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside June 2004