seaside February 2011

seaside@lists.squeakfoundation.org

60 participants
76 discussions

Re: Pharo/Seaside UI testing
by Fritz Schenk 02 Feb '11

02 Feb '11

The first one works, the second does not http://www.tonyfleig.com/smallthoughts/blog/seasideautomatedtesting http://www.tonyfleig.com/smallthoughts/blog/seasideautomatedtesting. Notice the '.' period.

1 0

Re: Clear/stop a periodic javascript process using Seaside?
by Paul DeBruicker 02 Feb '11

02 Feb '11

Thanks for the replies and pointers. I went ahead and made this jQuery plugin: http://plugins.jquery.com/project/Registered-Interval and then added it to the jQuery Widget Box on squeaksource.com. It stores the interval ID in the .data() function of a DOM element and then retrieves from the DOM element when you want to clear the interval. In the example I uploaded to SqueakSource there are three counters that update independently of each other at different speeds using setInterval. Each can be started and stopped independently. It does what I want for now. I wanted to have this as I'm using Futures for some stuff and need to poll for results from multiple tabs on the same page and didn't want to do a full page refresh when each tab had results. It seems to work for that purpose. I need to poll for results rather than let the Futures block because I want to port what I've done to Gemstone and Dale's recommendation was to poll for results rather than block. I think the javascript code could be made more reliable and from what I've read it'd be a better idea to use setTimeout recursively rather than setInterval but I haven't gotten my head around that yet. Thanks again Paul

1 0

Re: [Seaside] Clear/stop a periodic javascript process using Seaside?
by Paul DeBruicker 02 Feb '11

02 Feb '11

Thanks Johan. I hadn't considered using an external javascript file. In your example js file I'd have to call unregisterInterval() to clear the interval. If I created multiple intervals on the same page, would the correct one get cleared without passing unregisterInterval the correct value for updateId? My knowledge of JS is less than Smalltalk. I think I can figure out how to store the updateId using the jQuery.data() function on the DOM element that is updating then send the clearInterval with the result of the calculation and have it get the updateId from the DOM element. I think it'd be something like this: function registerAndSetInterval(aLambda, ms, anElement){ var updateId; updateId := setInterval(aLambda, ms); $.data(anElement, "intervalId", updateId); } funtion unregisterInterval(anElement){ var clearId; clearId:= $.data(anElement, "intervalId"); clearInterval(clearId); } But I'd probably want some kind of timeout in the first function so it stops if the connection drops or something goes haywire. Thanks for the heads up on the renderContentOn: method I posted. I had it in the email using replaceWith: and switched to load html: in an attempt to simplify the problem illustration. Paul On 02/01/2011 07:00 AM, seaside-request(a)lists.squeakfoundation.org wrote: > Message: 4 > Date: Tue, 1 Feb 2011 08:34:46 +0100 > From: Johan Brichau<johan(a)inceptive.be> > Subject: Re: [Seaside] Clear/stop a periodic javascript process using > Seaside? > To: Seaside - general discussion<seaside(a)lists.squeakfoundation.org> > Message-ID:<2A77B15A-BD63-4C83-8549-0582F9A3D913(a)inceptive.be> > Content-Type: text/plain; charset=us-ascii > > You can assign the id that is returned by setInterval() to a global variable and call clearInterval() whenever you want to. > > The best thing to do in this case is use an external javascript file where you declare the (global) variable that should keep the reference id (at least) and also the functions that will register the id and cancel the periodic update. You then call these functions from within the Seaside-generated javascripts. Although you can probably make it work without the external javascript file, it's better practice imho. Here's what I would do: > > var updateId; > function registerAndSetInterval(aLambda,ms) { > updateId = setInterval(aLambda,ms); > } > function unregisterInterval(){ > clearInterval(updateId); > } > > Next, I'm a bit puzzled with your Seaside code. Doesn't that create a nested div inside the already existing div every 2 seconds? Since the load block creates another div with the same id, you will run into problems. You also need to use the canvas object that is passed to the html load block instead. Here is what I make of it: > > renderContentOn: html > (html div) > id: 'replace'; > script: (JSStream on: 'registerAndSetInterval') > call: '' > with: ((html jQuery id:'replace') > load html: [ :h | > count := count + 1. > h render: 'count: ' , count greaseString ]) asFunction > with: 2000 > > Calling a javascript function from Seaside-generated javascript is a bit awkward using the #call:with: because it was designed to be sent to a receiver object (such as jQuery instance). But I don't think there's another way to call them from Seaside-generated javascript. > > Hope it works, if not: please let me know;-) > > Johan

3 2

Update select display when selection changed
by Bob N. 01 Feb '11

01 Feb '11

Hello, How do I get the rendered display of a drop-down select list to show an updated selection from another session? Here is the scenario: I have a domain object with an attribute displayed in a drop-down list. Some other session updates the attribute. I refresh my display, but the rendered selection does not change. Using Firebug, the generated html shows the updated selection. This may be basic HTML knowledge, but should the displayed value not update to show the changed 'selected' option? Or is the value intended to be set only on the initial page display and then only by a user action? Here is an example. I have a demo Seaside component with a class variable #testStateListSelection which is selected to 'one' in a Seaside session. If I change the value to 'three' in another Seaside session, the displayed value stays as 'one' in the original session after rendering again, even though the "selected" in the generated HTML shows "three". renderSelectionListOn: html html form: [ html select list: #('one' 'two' 'three' 'four' 'five'); selected: self class testStateListSelection; callback: [:value | self class testStateListSelection: value]. html break. html submitButton callback: [Transcript cr; show: self class testStateListSelection]; with: 'Save'] ...the displayed value shows 'one', even though the HTML is... <select name="1"> <option value="1">one</option> <option value="2">two</option> <option value="3" selected="selected">three</option> <option value="4">four</option> <option value="5">five</option> </select><br> How do I get the drop-down selected value to show 'three'? BTW: all I know about HTML & browser behaviour I've learned from coding Seaside, so I may have a skewed perspective ;-) Thanks for any help, Bob Nemec

3 4

Presentation at FOSDEM
by Stephan Eggermont 01 Feb '11

01 Feb '11

Sunday 2011-2-6 we'll show how we deployed our Seaside application. If you're interested, please join us. Stephan Configuration & Systems Management devroom (room AW1.120) • 15:00 - 15:45: Configuration management for developers (Stephan Eggermont, Willem van den Ende) We created a server environment so a small startup could deploy its web application with all the services it needs. Well, environment is a big word... bootstrapped startups don't have money to manage redundant servers, so we set up just one production server. Still, when disaster strikes, we want to be able to have another server up and running within thirty minutes. For developers laziness is a virtue. Therefore we want to apply DRY (don't repeat yourself) to systems administration. So for this project we considered each time we log in to the production server a 'systems administration smell'. Attend our case study to see how we used a configuration managent system (puppet), application specific scripts and a few practices to keep us sane. See how far we have gotten towards our goal of DRYness and fast recovery, and learn from our mistakes.

2 1

Clear/stop a periodic javascript process using Seaside?
by Paul DeBruicker 01 Feb '11

01 Feb '11

Hi - Using jQuery/AJAX & Seaside 3.0.3 I'm trying to check for the results of a calculation and when its complete update a div and then stop checking without doing a full page refresh. I can do everything but stop the periodic process without doing a refresh If I have an inst var named 'count' and do this: renderContentOn: html (html div) id: 'replace'; script: ((html jQuery id:'replace') load html: [ :h | count := count + 1. (html div) id: 'replace'; with: [ html render: 'count: ' , count greaseString ] ] ; interval: 2 seconds). every two seconds the count is increased and then displayed. If I use replaceWith: I have the same problem. The only thing I know to stop the periodic process is to refresh the page and just render the results I had been waiting on. I would like to use AJAX, rather than refresh so I can do this in several places on a single page. Its my understanding that the setInterval function has an id that can be sent to clearInterval but I don't know how to get the function id through Seaside. Is there a way to get that id and send it to clearInterval or another way to do what I want? Thanks Paul

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside February 2011