seaside January 2011

seaside@lists.squeakfoundation.org

57 participants
49 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

Seasidehosting not working ?
by Hilaire Fernandes 14 Jan '12

14 Jan '12

I still have probleme to make working seaside hosting. I took a fresh image from the last pier one-click distribution (no save operation from the image), upload it to cyclades.seasidehosting.st, but still the image can't be runned. Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

10 13

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

install Seaside30 without OB?
by Esteban Lorenzano 30 Mar '11

30 Mar '11

Hi, I want to install Seaside 3.0.3 into a production image, and I want to get rid of OmniBrowser... which groups should I specify to obtain this? Cheers, Esteban

10 19

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

Seaside authentication/login/user account package
by Tony Fleig 16 Feb '11

16 Feb '11

Hello all, I have just published the TFLogin package at http://www.squeaksource.com/TFLogin. This package provides basic user authentication, registration, and account management for Seaside. Features include: . User login component with username and password text fields, forgot username, forgot password, register, and login buttons. . User registration component with optional reCaptcha spambot protection. . Edit account settings component allows user to change username, password, email address and application-specific properties. . Optional email confirmation for registration and account changes. Email content is provided by the host application. Examples are included. . Multi-part HTML/plain text email. . Configurable confirmation email timeouts and cookie retention periods. . Forgot username and forgot password support. . Options to allow empty passwords, remember username in cookie, and automatic login on return to the website. . Add additional user-related objects to the account edit form. . An application properties dictionary is provided that allows you to store and retrieve additional objects along with the user account information. . All settings are available in the Seaside configuration page. . Test/demo application included. . TFLogin Guide document included (see the Wiki tab.) Persistence is provided by a storage adaptor that can be replaced with the persistence mechanism of your choice. The default provided is a reasonably scalable file-based system using ReferenceStreams. Each user's information is saved in a separate versioned file. Tested with Seaside 3.0.3 and Pharo 1.1.1. Email does NOT work with prior versions of Seaside. See the Squeaksource project Wiki tab for the complete TFLogin Guide document. I have integrated this successfully with one of my own existing web apps and of course the test app included in the package works fine. This is *not* a lot of testing and this is definitely version 1.0 or less, so I expect bugs a-plenty will be found. I am still refactoring the code, but that should not change the functionality or the public API. All feedback is welcome. Regards, TF

7 18

According to Lukas Renggli the following pattern is used to 'say it smalltalk' for jQuery
by Fritz Schenk 02 Feb '11

02 Feb '11

"Basically Query action " Note: this is from hist presentation at ESUG. Fits the following code perfectly: <code> onClick: ((html jQuery: #count) load html: [ :h | h render: (count := count - 1) ]); </code> However, what pattern fits the following": <code> html submitButton onClick: (html jQuery ajax script: [ :s | s << (s jQuery: #logger) html: DateAndTime now ]); with: 'Replace'. </code> There appear that there are two messages starting with 'jQuery' '#jQuery' and '#jQuery:'; but what is the Query and what is the action in the last example? It would be nice to have some paragraphs describing the architecture of the jQuery implementation in Seaside. Merely to point to the superb jQuery documentation is not sufficient for me. Thanks

2 4

Keep-alive timer for Seaside app
by Tony Fleig 02 Feb '11

02 Feb '11

Hi, I want to keep my Seaside app's session from expiring as long as the user's browser page is open, even if the user does not interact with the page. I came up with the following method and it seems to work when rendered in the page. My questions are: Is there better way to do this? Is there an easier way to get the cacheTimeout value? Do I really need two JSScript instances to create the interval timer? I couldn't find a better solution. renderKeepAlive: html | script cacheTimeout | cacheTimeout := self session application cache expiryPolicy configuration at: #cacheTimeout. script := JSScript new add: (JSScript new add: (html jQuery ajax callback: [ Transcript cr; show: 'keepalive'])); interval: (cacheTimeout - 60) seconds asDuration. html document addLoadScript: script.

6 9

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside January 2011