seaside April 2011

seaside@lists.squeakfoundation.org

61 participants
54 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

Re: Anyone building seaside images on a mac with Jenkins?
by Stephan Eggermont 28 Oct '11

28 Oct '11

Thank you Sven. Do you also have a diff for build-oneclick.sh? chmod on 10.6.7 has no --reference. I noticed in the history a 'now also mac works' which has the same line. Stephan

5 5

Re: Anyone building seaside images on a mac with Jenkins?
by Stephan Eggermont 28 Oct '11

28 Oct '11

Lukas wrote: >If anybody knows how to make the build scripts more portable, please >lt me know. I don't have much bash scripting experience. I wrote and >tested the scripts only on Ubuntu Server. In the answers on http://stackoverflow.com/questions/5753687/replacement-for-chmod-reference-… it looks like stat -f can provide the mode more portable. Stephan

2 1

Seaside305 in Squeak 4.2
by Torsten Bergmann 10 Jul '11

10 Jul '11

Original discussion on seaside list (now cc'ing Pharo list too) Phillipe wrote on seaside list: >In general we use the OmniBrowser from [1], but it has issues in Pharo >1.2 as well :-( AFAIK these issues have been addressed and there is a Pharo specific OB version which is now hosted at squeaksource.com/PharoOB.html It is also used to build Pharo 1.2 already. For details ask Guillermo Polito or on Pharo-dev list. Lukas wrote: >I have a nicely working version of OB with RB, Shout and eCompletion >for Pharo 1.2. Just add <http://source.lukas-renggli.ch/pharo12 So you forked again and I wonder why? Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

5 6

JavaScript code from Aida/Web for Seaside too?
by Janko Mivšek 06 Jun '11

06 Jun '11

Dear Seasiders, In a sign of good will and better cooperation I'd like to "donate" recent JavaScript code in Aida 6.2, which in only 3KB includes everything you need for Ajax and WebSocket support for real-time web apps. You can see the code directly on Aida demo site: http://demo.aidaweb.si/scripts-a.js And you can see this code in action on Ajax demo page: http://demo.aidaweb.si/demo.html?view=ajax I hope this way we can together improve such a JavaScript part of our web frameworks in the future. Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

4 3

Should I become a Seasider?
by Ralph Boland 04 Jun '11

04 Jun '11

This post is about making a living as a web developer using Seaside. I am an unemployed software developer in Calgary (1,000,000 people), Alberta, Canada. I have used Squeak for years but I have found no Smalltalk work in Calgary and in fact know of only one small company in Calgary that uses Smalltalk. I know very little about Seaside. My impression is that websites developed using Seaside are somewhat slower than with other web development tools and that Seaside uses more memory (I assume on the server side) than other web development tools. Nevertheless there are web developers using Seaside successfully. Are these impressions correct? What I am wondering is should I learn Seaside and then attempt to sell my web development services in Calgary? My impression is that: 1) No one in Calgary has ever heard of Seaside so selling my services would be difficult. 2) Since I should be able to develop web sites faster using Seaside I should be able to offer my services at a discount and hopefully be able to find business that way. But since no one but myself (at least locally) would be able to maintain the web sites, potential customers are going to be very shy. Are these impressions correct? Lets assume I decide to become a web developer (something I know almost nothing about) using Seaside as my competitive edge. To my knowledge I would be the only Seaside web developer in Calgary. 1) How long (starting basically from scratch) is it going to take before I am competent; or at least competent enough to seek clients? Assume I am a competent Squeak developer. 2) Which version(s) of Smalltalk should I use? I know Squeak and have used Visualworks in the distant past. 3) How screwed will my clients be if my ticker stops unexpectedly. Can Seaside developers from outside Calgary pick up the slack for my hypothetical clients? 4) Is there any areas within the web development would that I should concentrate on or avoid? 5) Is there any additional software/hardware that I would need other than my home computer (running Ubuntu) and Squeak/Seaside? My resources for investments is very limited. Are there other questions that I should have asked? Starting a business is generally a tough deal so please don't butter me up with glowing reviews of Seaside. Regards, Ralph Boland

21 30

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside April 2011