seaside September 2010

seaside@lists.squeakfoundation.org

62 participants
77 discussions

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

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

About Deployment
by Frederic Pluquet 20 Oct '10

20 Oct '10

Hello, I use Seaside for a lot of personal development and I love its rapidity of development! But for real deployment there is a big disadvantage. At my knowledge, I have only two solutions to deploy an application: have an own server (what I do for the moment) or put my image on seasidehosting. So I have a simple idea: it will be really cool if I can develop in Smalltalk with Seaside and I deploy the code in Php/MySql to put it in any common server. I think this idea is not so crazy. I know there is a world between Smalltalk and Php (I know both well) but a way to implement this idea is perhaps the next one. The first step: the classes (and methods) used in Smalltalk must be translated into Php (some papers show that it is possible into Java for example). The second step are about the alive objects. Because in Smalltalk the alive objects are kept in memory (in the image), a possible solution is to create each object in Php and save them in a MySql database to retrieve them through each page. An important point is that Php is a dynamic typed language. The convertion will be so easier than Java. So my question is the next one to the Seaside developers: what are the big obstacles to achieve this goal ? Some questions in my mind: What about continuations ? What about object reflectivity ? Fréd ---- Frédéric Pluquet Université Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet

7 6

How do I do a remote validation for jquery.validator.js with a seaside component?
by Tim Murray 04 Oct '10

04 Oct '10

Hi List. I am implementing server side form validations with the jquery.validation.js plugin. There are examples for doing a remote validation of a username to help to ensure that they stay unique within a site. I am now at the point where I want to write a Seaside "component" that will respond to the jquery.validation remote call . I am not sure how to approach this. >From the internet, a typical example of a php implementation looks like this: <? $email = $_GET['email']; function isValidEmail($email){ return eregi("^[_a-z0-9-]+(\.[_a-z0-9-]+)*(a)[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2, 3})$", $email); } if($email=="") { $errormsg="error1"; } if(!isValidEmail($email) && $email!="") { $errormsg="error2"; } echo $errormsg; ?> I am wondering if I should intercept these on the initialRequest of my applications custom WATask MyWATask>>initialRequest "new user registration ajax lookups" (aRequest url pathString endsWith: '/jquniqueloginlookup') ifTrue:[?????WHAT DO I DO????]. Thanks for your time.

3 2

#seaside value?
by Ken Causey 02 Oct '10

02 Oct '10

I've long noticed that #seaside attracts newbie questions but few useful responses from the experienced. I did a quick survey of the logs for the last 30 days: Questions: 18 Answers: 5 Referrals: 4 By referrals I mean a response that suggests that newbie look elsewhere, this list for example, versus something the newbie considers an actual useful response. I tend to be the source for many of these. Sometimes there was both a referral and a useful answer to the same question, I counted that as an answer and not a referral. This was the totality of traffic on #seaside over the last 30 days, there were no other conversations of any kind. I have to wonder if the #seaside IRC channel actually has any value, for it to have some active users and developers of Seaside are going to have to start hanging out and responding more. Ken

3 2

Anybody get jquery.validate.js working?
by Timothy Murray 02 Oct '10

02 Oct '10

I ran into another "gotcha" with this approach. In the custom event handler example from remember the milk<http://jquery.bassistance.de/validate/demo/milk/> there is a submitHandler: handle that must be commented out or the seaside callbacks assigned to your submit button will not work. $(document).ready(function() { // validate signup form on keyup and submit var validator = $("#signupform").validate({ ....... submitHandler: function() { alert("submitted!"); }, ..... }); Once I commented out that section of the example, the Seaside callbacks worked. <http://jquery.bassistance.de/validate/demo/milk/> Prior to removing it, I had tried replacing the alert("submitted!") with return true; and return false; to no avail.

2 1

Shell script for pharo on ubuntu 10.10 beta
by fritz schenk 02 Oct '10

02 Oct '10

1. by default shell scripts are not executable in ubuntu 10.10 2. the executable bit must be set before the context menu offers 'Open' and executed the script. 3. once the script is set as executable, the script starts, but squeak does not start (part of Pharo.sh) 4. Pharo.sh works fine on ubuntu 9.04 - does not require the executable bit in the script file.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside September 2010