seaside April 2008

seaside@lists.squeakfoundation.org

79 participants
89 discussions

Re: Guiding the Albatross to the VW-Seaside? [was: [Seaside]Seasidefor VisualWorks]
by Boris Popov 24 Jun '08

24 Jun '08

I would hope so seeing as that's where majority of development is happening right now and cincom focus will first be on better integration and only then on seaside itself if I understand correctly. Cheers! -Boris (Sent from a BlackBerry) ----- Original Message ----- From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org> To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> Sent: Wed Jun 20 22:37:01 2007 Subject: Re: Guiding the Albatross to the VW-Seaside? [was: [Seaside]Seasidefor VisualWorks] So the current development model with development happening in Squeak and versions for other dialects being "generated" from there will stay? Philippe 2007/6/21, Michael Lucas-Smith <mlucas-smith(a)cincom.com>: > Yes, that's very high on the list of laws for this project. We're not > forking Seaside. > > Michael > > Ron Teitelbaum wrote: > > Hi Michael, > > > > I'd like to see Cincom maintain squeak compatibility. > > > > Ron Teitelbaum > > > > > >> -----Original Message----- > >> From: seaside-bounces(a)lists.squeakfoundation.org [mailto:seaside- > >> bounces(a)lists.squeakfoundation.org] On Behalf Of Michael Lucas-Smith > >> Sent: Wednesday, June 20, 2007 5:15 PM > >> To: Seaside - general discussion > >> Subject: Re: Guiding the Albatross to the VW-Seaside? [was: [Seaside] > >> Seasidefor VisualWorks] > >> > >> > >> > >>> Some UI testing tool like Watir (Ruby, see [1][2]) or Albatross (Squeak, > >>> see [3][4])on VW would be nice. > >>> I am aware of the Seaside Testing Tool from David Shaffer[5], but a > >>> framework capable of replaying JS scripts and showing the stuff > >>> > >> happening > >> > >>> in some browser would be nice - both for the test driven developers and > >>> their customers. > >>> > >>> Maybe guiding the Albatross to the VW-Seaside would be an option? > >>> > >>> > >> This is nice. When we did web testing before I moved to Cincom we > >> utilised the known properties of the server side code instead of > >> bouncing back to the web browser itself. Mostly because of: > >> a) Speed of running the tests > >> b) Ease of writing the tests > >> > >> In the end we wanted to do testing like this - so I whole heartedly > >> support this idea. It's going on to the project backlog. Thanks for > >> bringing it to my attention. > >> > >> Cheers, > >> Michael > >> > >> _______________________________________________ > >> Seaside mailing list > >> Seaside(a)lists.squeakfoundation.org > >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >> > > > > _______________________________________________ > > Seaside mailing list > > Seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > _______________________________________________ > Seaside mailing list > Seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ Seaside mailing list Seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

4 3

REServe and IOSPersistent project
by Thomas Kowark 14 May '08

14 May '08

Dear all, I've already posted this on the squeak-dev list, but since this is an issue for seaside developers, too, I thought posting it here could improve my chances of finding an answer. I am evaluating some object-relational mappers for Squeak and especially Seaside applications. In addition to the obvious choice GLORP I stumbled upon the REServe/IOSPersistent project. It seemed very promising to me, since it reduces the configuration effort to a very small amount. However, last updates have been commited in october 2006. Does anybody know what happend to those projects and why the automated mapping idea has not been introduced in other mappers as well? Best, Thomas -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

2 1

WAPresenter>>processCallbackStream: aCallbackStream
by Edward Stow 06 May '08

06 May '08

Hi, While working my way through the Seaside internals I came across: WAPresenter>>processCallbackStream: aCallbackStream aCallbackStream processCallbacksWithOwner: self. self processChildCallbacks: aCallbackStream. aCallbackStream processCallbacksWithOwner: self Is their a reason for calling #processCallbacksWithOwner: twice? Thanks -- Edward Stow

4 6

#render: or #call: components.
by Edward Stow 03 May '08

03 May '08

Hi, I have an application that has a body section, the body section can be rendered with two or more components. For example: TemplateComponent - HeaderComponent - BodyComponent - one of BodyOne | BodyTwo | etc components. - FooterComponent This question may be exposing my ignorance .... but I see two ways to 'paint' my page with components in response to user interaction with my application. 1. #render: During the renderContentOn phase arrange for the component (BodyOne | BodyTwo) to be #render:ed. 2. #call: During the action phase arrange for the component (BodyOne | BodyTwo) to be called from the current body component. The #call:ed component does not #answer. What would be best practice? Should #call: only be used for components that you expect to #answer like a DatePicker, ColorChooser etc? Thanks -- Edward Stow

6 11

It is time for a Seaside IRC channel?
by Sebastian Sastre 01 May '08

01 May '08

Hi there, It's only me who feels the need of an IRC for seaside of its own? I think email is a vehicle of comunication that some times is just too formal. I feel we need the casual talk among seasiders, what do you say? Sebastian Sastre

8 19

Seaside memory consumption?
by Andreas Raab 30 Apr '08

30 Apr '08

Hi - I'm contemplating to use Seaside and Magritte to mock up an administrative interface for internal use but for various reasons this may have to run inside an image that does actual production work. Because the work can at times be memory intensive, I'm interested in learning more about memory consumption of Seaside and Magritte. Are there any guidelines for "reasonable" working sets of memory for Seaside (depending on load)? What about memory consumption of Seaside apps that run for several months without restart (session cleanup etc)? Thanks for any insights, - Andreas

6 13

Scaling Seaside
by Richard Eng 30 Apr '08

30 Apr '08

Just out of curiosity, if I should need to scale my Seaside app beyond my one Linux box, exactly how do I do that? I am currently using Apache to load-balance over several Squeak VMs: <Proxy balancer://seaside_cluster> BalancerMember http://localhost:9090/seaside/go route=GSN9090 BalancerMember http://localhost:9091/seaside/go route=GSN9091 BalancerMember http://localhost:9092/seaside/go route=GSN9092 BalancerMember http://localhost:9093/seaside/go route=GSN9093 ... Do I add a second Linux box that runs additional Squeak VMs (but does not run Apache)? Say, the second Linux box is at IP 192.168.1.110. Then do I edit the above to: <Proxy balancer://seaside_cluster> BalancerMember http://localhost:9090/seaside/go route=GSN9090 BalancerMember http://localhost:9091/seaside/go route=GSN9091 BalancerMember http://localhost:9092/seaside/go route=GSN9092 BalancerMember http://localhost:9093/seaside/go route=GSN9093 ... BalancerMember http://192.168.1.110:9200/seaside/go route=GSN9200 BalancerMember http://192.168.1.110:9201/seaside/go route=GSN9201 BalancerMember http://192.168.1.110:9202/seaside/go route=GSN9202 ... ? Is it really that simple and straightforward? Thanks, Richard

3 2

depricated api
by Karsten 28 Apr '08

28 Apr '08

Hi there, today I tried to specifiy the target of an anchor and ran into the #depricatedApi again. I like the idea of how depricatedApi works in terms of you see which methods you call that you shouldn't call as they're depricated, but there's one small piece of information missing: what should I use instead? Wouldn't it make more sense to add an argument to this message with some sort of hint telling the developer what to do instead? The only alternative to me seems to use the same code that's inside the #target: method in my own application but without the depricatedApi call. That's absolutely not what I'd like to do though, maybe someone else has a better idea. Kind Regards Karsten -- Karsten Kusche - Dipl.Inf. - karsten(a)heeg.de Georg Heeg eK - Köthen Handelsregister: Amtsgericht Dortmund A 12812

2 2

Re: [Seaside] Autologout implementation
by Boris Popov 28 Apr '08

28 Apr '08

I think he wanted the app to go back to the home page automatically when auto expiring. In which case you can just add a refresh periodical with lifetime just a tad longer than a session timeout. Cheers! -Boris (via BlackBerry) ----- Original Message ----- From: seaside-bounces(a)lists.squeakfoundation.org <seaside-bounces(a)lists.squeakfoundation.org> To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> Sent: Sun Apr 27 11:40:45 2008 Subject: Re: [Seaside] Autologout implementation 2008/4/27, Stefan Schmiedl <s(a)xss.de>: > How would you implement automatic logout after a given period of > inactivity? Set the session timeout to this value. Cheers Philippe > The app is running in a workshop, where a bunch of people use the same > machine to access their scheduled tasks and other stuff. They will often > leave "their" last page on the screen, so the goal donor requested an > automated reload of the starting page. > > I did this for another app (in IOWA on Ruby) by meta-refreshing to the > "/logout" page, which in turn expired the session and redirected to the > starting page. > > Below is what I came up with in Seaside. This decoration is > autmatically added to the pages if the users are in the autologout > category. > > Has anybody a better idea for this? > > Thanks, > s. > > > Smalltalk.HS defineClass: #AutoLogoutDecoration > superclass: #{Seaside.WADecoration} > indexedType: #none > private: false > instanceVariableNames: 'delay ' > classInstanceVariableNames: '' > imports: '' > category: ''! > > "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! > > > !HS.AutoLogoutDecoration class methodsFor: 'instance creation'! > > delay: seconds > > ^(self new) delay: seconds; > yourself! ! > > "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! > > > !HS.AutoLogoutDecoration methodsFor: 'updating'! > > updateRoot: root > > root redirectTo: self urlForExpiry asString > delay: self delay! > > urlForExpiry > > Continuation currentDo: [:cc | ^self session actionUrlForContinuation: cc]. > (self session) expire; > redirect! ! > > !HS.AutoLogoutDecoration methodsFor: 'accessing'! > > delay > ^delay! > > delay: anObject > delay := anObject! ! > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

3 2

running code asynchronously
by rjk 27 Apr '08

27 Apr '08

Dear Seasiders, I'm cooking up some seaside/code recipes as an exercise and hopefully for (web)publication some day, i have the following question; Q. How do i run code asynchronously (inside the request/response cycle) ? A. My answer at this point is the following using a [block] fork. construct as described in Smalltalk by example from alex sharp: 01 renderContentOn: html 02 html paragraph: Time now asTimeStamp. 03 [Transcript cr; show: 'waiting for 10 seconds...'. 04 (Delay forSeconds: 10) wait. 05 Transcript cr; show: 'done!...'] fork. 06 html paragraph: Time now asTimeStamp. Could somebody confirm this? and give additional comments if this is not the true seaside way? Thanks in advance! Redmar Kerkhoff

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 April 2008