seaside November 2010

seaside@lists.squeakfoundation.org

59 participants
62 discussions

Handling expired Session in Seaside 3.0
by Udo Schneider 13 Apr '12

13 Apr '12

All, if this is just an RTFM question I'm happy to read on my own ... however I'm searching for a solution to handle expired sessions in Seaside 3.0. My goal is to either display a specific component when a request for an expired session is recieved or to be able to find out if a request was for an expired session in my initial component. Any pointers? CU, Udo

4 8

Static serving of jQuery and related files - reg.
by muthu kutti 14 Nov '11

14 Nov '11

Hi All! I would like to move jQuery and related files out of the image have them served directly by Nginx. How do I go about doing that? Thanks in advance. Muthu

6 6

send email with seaside
by Simon De Baets 09 Nov '11

09 Nov '11

Hello, I build a website with seaside3 / pharo. I want to send email to the users of my website but i don't know how can i do this. So how can i send an email with seaside? Thanks, Simon

5 4

Repainting during AJAX callbacks
by C. David Shaffer 26 May '11

26 May '11

Before I get too far let me say that I don't know, yet, whether this is an unnecessary hack or a worthwhile framework. I'm using it now and like it but I'd be happy to replace it with something better is people can tell me what that better thing is :-). Here's the problem: During an AJAX callback (request, update or script) sometimes a component unrelated to the one making the callback needs to be repainted. Normally this happens as the result of an announcement. While announcements serve to decouple the components they also prevent the source of the announcement from knowing to cause this other component to paint. Basically this motivates using Comet but I don't like Comet and find that I don't need Comet's level of "server push" for any of my applications. What I need is simply the way tack a little extra javascript on the end of AJAX calls... My solution: Repaintable in the Cincom Public Store Repository. (This package uses JQuery.) It is a very simple framework so easily abandoned if it is the wrong thing to do :-) Here's how it works: Components subclass RPRepaintable (or you merge RPRepaintable's methods into your component hierarchy if that isn't possible). You must also use RPSession or a subclass as your session class for your application. When a component wants to append javascript onto the end of the current response to an AJAX request it: self repaint: 'some-jquery-selector' using: [:h | "h is a canvas"] The block with be invoked with a canvas. Paint on it was you normally would. Its contents will be loaded by jQuery into the element(s) indentified by 'some-jquery-selector' (normally an element id). To simplify things, if the component wants to be able to completely repaint itself it can implement the following trio of methods: renderContentOn: html html div id: self contentId; with: [self paintOn: html] contentId ^'some-unique-id' paintOn: html html text: 'Put your normal renderContentOn: stuff here' Then, such a component just has to send itself #repaint to repaint its contents. So, suppose you receive an announcement and you want to repaint yourself. Just do "self repaint". Its that simple. It works whether the original AJAX request was "script" or "html" type. Sending #repaint (#repaint:using) during a full-page repaint (normal HTTP request) does nothing...your component will be painted during the render phase anyway so normally this is not a problem. An example is provided in the Public Store Repository (Repaintable-example). Some notes: 1) All AJAX requests must either be dataType 'script' or 'html'. This means that cases when you don't render anything like: html div onClick: ((html jQuery: #foo) ajax callback: [self foo]) will have to modified to html div onClick: ((html jQuery: #foo) ajax dataType: 'script'; callback: [self foo]) I think that this this is the result of a bug in Repaintable but I can't tell. In practice 99% of my AJAX requests are either html: or script: requests anyway. In those cases you don't need to send dataType:. 2) If you are using AJAX for purposes other than sending back HTML or javascript you might end up with cruft being appended to your responses :-) as components try to repaint themselves. This isn't a problem for me but it might be for those of you using JSON to transfer data etc. This could be fixed if it becomes a problem for anyone. So, garbage or pure genius (I know the answer already as it took me three attempts to spell genius)? David

5 8

lightboxes in Seaside 3.0/VWNC 7.7
by Dr. Johannes Brauer 13 Mar '11

13 Mar '11

Hi, I am using a Seaside application developed with Seaside 2.8 and VWNC 7.6. Now I am trying to move to VWNC 7.7/Seaside 3.0. Nearly all seems to work fine with 7.7/3.0 except for my dialogs implemented as lightboxes. In 7.6/2.9 activating a lightbox makes the window behind the lightbox grey and the lightbox itself appears with yellow background. In 7.7/3.0 activating a lightbox makes the window behind the lightbox grey (okay) but the window is zoomed in (why?). The lightbox has transparent background (why?) making the content unreadable in front of the zoomed main window. What can I do so that my appl. behaves in the same way in VWNC 7.7/ Seaside 3.0 as before? Johannes Staatlich anerkannte private Fachhochschule NORDAKADEMIE Gemeinnützige Aktiengesellschaft Köllner Chaussee 11 25337 Elmshorn Vorstand: Prof. Dr. Georg Plate (Vorsitzender), Dipl.-Ing. Jörg Meier (stellv. Vorstand) Vorsitzender des Aufsichtsrats: Dr. h.c. Hans-Heinrich Bruns Sitz: Elmshorn, Amtsgericht Elmshorn, HRB 1682

1 1

Can't get debug link - please help
by Каменев А.Н. 23 Jan '11

23 Jan '11

Hello! Pharo 1.0 and Seaside 3.0 1) WAComponent subclass: #StTestComponent 2) renderContentOn: html html text: self getText. 3) getText nil test. ^'Hello world !!!'. 4) WAAdmin register: StTestComponent asApplicationAt: 'test'. 5) Tools/Seaside Control Panel add adaptor: WAComancheAdaptor start on 8080 (set Debug mode) 6) http://localhost:8080/test MessageNotUnderstood: receiver of "test" is nil Your request could not be completed. An exception occurred. 7) Page does not contain link to debug !!!( what am I doing wrong ? With best regards Alexey Kamenew

3 4

Possible Pharo1.0 problem. No error indication while parsing and no debugging triigered on error.
by Fritz Schenk 22 Jan '11

22 Jan '11

Running with Seaside 3.0 on Pharo 1.0 Simple rendering method with error <witherror> renderContentOn: html html heading: count. html anchor callback: [ self increase]; with: '++' "<<<<< error here - missing period" html space. html anchor callback: [self decrease]; with: '--' </witherror> The error is not indicated while 'accept'ing or prettyprinting. Missing '.' after first with clause. when I access the page I get the error: <error> MessageNotUnderstood: ByteString>>html </error> the page continues in 'Loading...' state, but there is no debugger in the environment. Please help.

5 8

News from seaBreeze
by Georg Heeg 31 Dec '10

31 Dec '10

Dear seaBreeze Friends, You might have thought by yourselves: No news from seaBreeze in a long time, is it dead? It is not. Internally we are using a version based upon VisualWorks 7.7.1 and Seaside 3.0 product release. Currently we are developing a new interesting feature for seaBreeze: Internationalization and Localization. Today we had the great break-through: The first multi-lingual seaBreeze application was up and running on my machine today. We are working together with a master course in software localization at Anhalt University. So please be patient to see progress in the not too far future. If you are interested in a prerelease version, please do not hesitate to contact me. Georg Heeg Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812 Tel. +49-3496-214328, Fax +49-3496-214712

2 3

Image not release the memory in a Seaside session
by Andrés Garagiola 01 Dec '10

01 Dec '10

Hi list, I have a problem with a Seaside session memory consumption. In my system there are a seaside session that should run for a long time (many days or months), this session is running a page that have JQuery code. This JQuery reload certain parts of the website by 5 seconds intervals. While time is progress then the vm memory is increase and it never release this memory. In two days the memory increase of 40 MB to 530 MB. I investigate the problem and found that the callbacks are adding in this code: store: aCallback | key | key := self advanceKey. callbacks at: (aCallback convertKey: key) put: aCallback. aCallback setKey: key callbacks: callbacks. ^ key But the old callbacks never are clear, then the GC never collect this objects. After a time the image have thousands callbacks that never will be collect. Anyone knows what can by the solution? Thanks you very much. Regards Andres

3 2

FileStream
by alexandre bp 30 Nov '10

30 Nov '10

Hi, I'm having trouble with the FileStream.... I have tried several things: filename := 'test'. aStream := StandardFileStream new. 1) aStream := FileStream newFileNamed:filename. 2) aStream := filename asFilename writeStream. 1) this solution worked one time but when I tried to create other files with other names (whatever the name) I get an exception: FileExistsException 2) doesn't work at all. I get an exception as well: MessageNotUnderstood: ByteString>>asFilename. I don't know what to do.... I don't understand why I have the exception FileExistsException even thought the name I give to filename is different... Thx for your help alex

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside November 2010