seaside August 2005

seaside@lists.squeakfoundation.org

54 participants
65 discussions

favicon for seaside?
by Michal 15 Aug '05

15 Aug '05

Now that there is a seaside logo, is there a seaside favicon? If you expose seaside directly (ie not behind apache rewrite rules, etc.), seaside gets asked for a favicon on every request cycle (it returns a 404 not found). I have a simple patch for WAKom to make it return an icon - currently a random downloaded icon. It would be nice to have a standard seaside icon however. Michal

1 0

[BUG?] The Third Ghost Request and error swallowing
by Michal 15 Aug '05

15 Aug '05

Hi all - There are some weird interactions between seaside and the squeak http framework - as noted in the comment of #beginConversation. If you download the vanilla seaside 2.5 image from seaside.st and run the seaside/counter application, it turns out that each click on '++' or '--' generates 3 requests, with a problem with the third. To see that there are 3 requests, the easiest is to put a halt at the start of #beginConversation, just before the request is created (do this once the session is already started, otherwise you'll get an initial avalanche of debuggers). A debugging session will reveal that the third request systematically answers false to 'self stream socket dataAvailable' -- there is nothing in that request, no headers, no url, no status, no nothing. (One way to see it is to insert a line like this into #beginConversation and take it from there: [ self stream socket dataAvailable ifFalse: [self halt] "<-- new debug line". [request := self readRequest] on: Error do: [ :ex | continue := false]. Now clicking on a link will generate some false positives where request initially answer false and then true, but the third consistently remains on false.) Note that the third request does NOT occur on a mac if you call it as localhost (ie: http://localhost:9090/seaside/counter), but it DOES occur if you use 127.0.0.1 (ie: http://127.0.0.1:9090/seaside/counter) instead. Apart from this quirk, the ghost was consistently seen on both mac and debian servers, both from safari and firefox/mac browsers, both on local and remote servers. This third "ghost" request triggers errors, obviously. The first error occurs in #initStatusString:, which receives an empty string and answers: ^self error: 'invalid http status line'. (Fixing that creates a cascade of errors down the line). Under normal circumstances, this error gets silently swallowed in #beginConversation, and the whole issue is thus hidden. To see the error for yourself, just stop the silent swallowing. For instance add a #pass: [request := self readRequest] on: Error do: [ :ex | continue := false. ex pass]. If you do that, you will need to wait a long time for the error to pop up, as the socket is trying to read for a fair amount of time before giving up. Although the net effect of all this is invisible to the normal seaside user, it does bite every sometime and seems generally unhealthy. It bit me today while coding some framework-internal stuff in seaside (which I will announce shortly). So: 1. why does a seaside http interchange involve this third "ghost" request? At first sight, that looks like a bug. (I'm actually not sure it is Seaside-specific, as I didn't try with a plain comanche server yet, but if it is, it might also start to explain the comment in #beginConversation that some errors 'only happen when Seaside is also loaded'...) 2. can we stop silently swallowing errors in #beginConversation? That will make it much easier to see the issues and give some incentive to fix them instead. Michal

2 2

Images are broken with Commanche & Squeak 3.8
by Dmitry Dorofeev 14 Aug '05

14 Aug '05

Hi all I have Squeak 3.8 & Seaside 2.5 Images served from the disk by Comanche/6.2 (KomHttpServer 7.0.2) are all broken. I guess it is due to the UTF-8 support ? I am starting it all with: | ma seaside | seaside := WAKomEncoded default. ma := ModuleAssembly core. ma serverRoot: FileDirectory default fullName. ma alias: '/seaside' to: [ma addPlug: [:request | seaside process: request]]. ma documentRoot: FileDirectory default fullName. ma directoryIndex: 'index.html index.htm'. ma serveFiles. (HttpService startOn: 9999 named: 'httpd') plug: ma rootModule It is does not matter if I use WAKom or WAKomEncoded Any idea what is wrong ? Thanks, -Dmitry.

2 1

liveUpdate question
by Bany, Michel 14 Aug '05

14 Aug '05

I am still working on making liveUpdate to update multiple independent areas in the html, something like this : liveCallback: [:item :h | operator := item. self renderValuesOn: h. self renderStatusMessageOn: h. self renderAsNameOn: h] As it was said in ealier posts, this implies using the DOM view from XmlHttpRequest and making sure the response from Seaside is sent with a content-type header set to "text/xml" and that the   entity is used instead of   so that IE gets happy. I published the changes as Seaside2.6a1-mb.57. Note that these changes take advantage of the DOM to execute all the javascripts found in the liveUpdate response if any. So far so good. There is still a difficulty left that I do not know how to solve. This is when the live-updated area includes callback. The url for the callback contains an ampersand that prevents IE from parsing the live response. Any idea ? Michel.

2 1

name attribute is deprecated
by Damien Cassou 13 Aug '05

13 Aug '05

Hi, you probably already know that, but the use of the attribute 'name' is deprecated in XHTML : http://www.w3.org/TR/xhtml1/#h-4.10 http://www.w3.org/TR/xhtml1/#C_8 You should use the attribute 'id' instead. Take care this attribute value should start with a letter and not with a digit as it is the case now (due to 'updateKey := self callbacks registerCallback: callback.' in #valueInputOfType:value:callback:). Thanks for your framework! -- Damien Cassou pour le Software Composition Group a Berne

3 2

Seaside in an Apache virtual server
by Sebastián Sastre 13 Aug '05

13 Aug '05

Hi all, What I have? I'm already have a seaside application runing in a port 3535 and right now it's working with that port opened. I also have a website running with apache2 in domainxxxxx.com showing static content. What I want? I want to navigate the seaside application through port 80 in some domain's subdirectory like: www.domainxxxxx.com/application. What I've done? My question is if I'm configuring right the apache. I've succesully loaded the mod_proxy (in the apache 2 in a linux Suse 9.1) and done this in the domainxxxxx.com virtual server .conf file: <VirtualHost xx.xx.xx.xx:*> ServerAdmin webmaster(a)domainxxxxx.com ServerName www.domainxxxxx.com ProxyPass /applicationName http://localhost:3535 ProxyPassReverse /applicationName http://localhost:3535 DocumentRoot /var/www/html/domainxxxxx.com ... </VirtualHost> What happend? The apache2 restarts the service without claims but when I open in a browser http://domainxxxxx.com/application the result is (404) "object not found". When I open http://www.domainxxxxx.com/application I have a Forbidden (403) message. What I should I do? Perhaps sombody has a clue of what is going on? best regards, Sebastián Sastre <mailto:ssastre@seaswork.com.ar> ssastre(a)seaswork.com.ar Seaswork Special Software Solutions www.seaswork.com.ar <http://www.seaswork.com.ar/> Este mensaje y sus adjuntos son confidenciales y de uso exclusivo para el usuario a quien esta dirigido. Puede contener información amparada por el secreto profesional. Si Ud. no es el destinatario especificado no debe copiar, enviar o utilizar ninguna parte del mismo y/o de sus adjuntos por ningún medio. Las opiniones vertidas son responsabilidad del autor y no son emitidas ni avaladas por SEASWORK a menos que se indique claramente lo contrario y que la identidad y autoridad del autor, para comprometer a nuestra empresa, puedan ser verificados. No se garantiza la integridad de los mensajes enviados por e-mail ni que los mismos sean enviados en termino, o que no contengan errores o virus. El emisor no aceptara responsabilidad por los errores, modificaciones u omisiones que resulten en el mensaje, bajo la hipótesis de que pudo ser modificado.

5 6

VisualAge
by Cees De Groot 13 Aug '05

13 Aug '05

Just doublechecking: as I've just started a project that's about giving an existing application a web interface, is it still correct that Seaside cannot be ported to VisualAge? Any experience with the web stuff that comes with VA? I've been given mostly carte blanche, the whole range from 'VA does everything' to 'export data with SOAP or something and build a PHP front' is permitted, so I'm researching my options here :)

6 6

liveUpdate checkboxes
by Bany, Michel 12 Aug '05

12 Aug '05

Another question : if I am not mistaken, there is no live update possible for checkboxes, is it ? I tried the things below, but it does not always work, any idea ? Michel. checkboxWithValue: aBoolean callback: callbackBlock liveCallback: liveBlock | uri id | id := self ensureId. self checkboxWithValue: aBoolean callback: callbackBlock. uri := self urlForLiveRequest: [:v :h | liveBlock value: v = 'true' value: h]. self script: 'document.getElementById(' , id printString , ').onclick = liveCheck(' , id printString , ',' , uri asString printString , ')'. function liveCheck(id, uri) { function constructUri() { return addParameter(uri, "s", document.getElementById(id).checked); } return liveUpdater(constructUri); }

2 1

Labeled elements in forms
by Damien Cassou 11 Aug '05

11 Aug '05

Hi, I've commited a modification that allow people to attach labels to input elements in forms. Use it this way: html checkboxWithValue: false callback: [] label: 'CheckBox' The generated code look like this: <input name="6" type="hidden" /> <label for="7"> <input id="7" name="7" value="true" type="checkbox" />CheckBox </label> <input name="8" type="hidden" /> - Add methods to manage 'labels' for forms. "When a LABEL element receives focus, it passes the focus on to its associated control." (http://www.w3.org/TR/html401/interact/forms.html#h-17.9). Unfortunately, it does not work in Safari. I will now try to create methods for other input types (I have just done it for checkboxes now, but the changes can easily be used for other elements).) -- Damien Cassou pour le Software Composition Group a Berne

1 1

external Javascript link + javascript code duplicates in page render
by Dmitry Dorofeev 11 Aug '05

11 Aug '05

Hi all, I gonna implement a Component based on Xinha (is not htmlArea) - http://xinha.gogo.co.nz/ It is HTML WYSIWYG editor. I gonna be able to have multiple components of that kind rendered on a page. I implemented #updateRoot: so it looks like updateRoot: aRoot aRoot addScript: 'my JS here....'. aRoot addHeadElement: myElem. ------------------ myElem contains a link to the external JavaScript file. I checked that addScript: will not add duplicate scripts to the <head> part of the document, which is nice in my case. But addHeadElement: will add duplicates, which is not wise. I know there should be a nice way to know if JavaScript link was added during page generation or not. Could anybody give me a hint or workaround please ? Thanks, -Dmitry.

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 August 2005