seaside January 2003

seaside@lists.squeakfoundation.org

15 participants
23 discussions

WATransaction & WATransactionStack?
by Stephen Pair 31 Jan '03

31 Jan '03

How are these classes used? In looking at the system, it's not apparent to me that these classes are used at all. Are these a left over from when you were doing more implicit management of the state of WAComponents? - Stephen

2 3

Document root on Seaside 2.x?
by Giovanni Giorgi 31 Jan '03

31 Jan '03

Excuse me, I cannot find the document root property in the configure page of Seaside 2.0 (from http://localhost:9090/seaside/config/ clicking on a "configure" link). How can I set the dir "/seaside/documentroot" as docroot for referencing gifs and so on? Can you provide an example? Thank you! -- [ [ [ JJ ] ] ] | First, they ignore you. Then they laugh | at you. Then they fight you. Then you win http://www.siforge.org | Mahatma Ghandi

1 0

Computation has been terminated
by Derek Brans 31 Jan '03

31 Jan '03

So, I'm getting a little error. The first page of my application loads fine, but when I click on any links I get the error: "Computation has been terminated" Method Context>>cannotReturn Continuation>>oneShotValue [] in XESession(WASession)>>handleRequest:response: Any ideas? Thanks, Derek Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com

2 13

sessionKey is nil
by Derek Brans 31 Jan '03

31 Jan '03

I'm trying to figure out where sessionKey gets set for WASession. Using the RB it would seem that it doesn't get set anywhere (the instance variable 'sessionKey' is never written to except in the setter method --- and the setter method is never called!) I would guess that the WASession's sessionKey should be assigned in WAApplication>>newSessionForRequest: response: I think I'm missing something... Thanks, Derek ps, using Seaside 2.07. useCookies is true. pps, Avi, Jullian, in WAApplication>>newSessionForRequest: response: can we change the code to use the getter for "useCookies" instead of the raw instance variable? I tried overriding the getter method to return true and it took me a while to figure out why it wasn't doing anything. Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com

2 1

Session expired -djb
by Derek Brans 30 Jan '03

30 Jan '03

I'm running into the problem that I can't get a session going. I point my browser to seaside/config and it just keeps trying to redirect me cause it can't find the continuation at 1. It doesn't seem to happen right out of the box. It seems as though seaside gets into this state over time but I'm not sure how. Any insights? Thank you. Derek Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com

1 1

Am doing things properly? -djb
by Derek Brans 30 Jan '03

30 Jan '03

This simple application gives me an error when I try to increment the counter. The count somehow has becomes nil. Have a look at the code, though. I think I'm running 2.14 Thank you, Derek Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com

2 3

Memory leak?
by Stephen Pair 29 Jan '03

29 Jan '03

After several weeks of developing and testing in a Seaside image, the image has grown to ~66MB when saved. Upon further inspection, it appears that there 4758 instances of WAResponse in my image. When you consider the various strings and streams that a WARequest holds, I think this is accounting for the bulk of my image bloat. Any ideas whether this is a legitimate issue, or is there something I should be doing to clean these up? Also, related to this topic, here are a couple of feature requests: 1) The ability to disable web browser backtracking...if disabled and a user hits the back button a couple of times, then hits a link...seaside could inform the user that the link is expired and that they are being redirected to a current view of their session (I prefer this to redirecting to a new session because that would make it too easy for a user to accidentally dump their session and lose anything they were working on). 2) The ability to restrict the backtacking depth (to conserve server resources)...this would allow you to make compromise between usability and server resource consumption...for example, if the backtracking depth is 10, then the user could back up up to 10 pages and use a link on those pages 3) Actually, this is more of a question...how closely is Seaside modeling browser behavior wrt to back tracking? For example, if a user backs up one page, then uses a link on that page, Seaside could discard the orginal page since there is no way of getting back to that page using the browser's back or forward buttons (granted, you could copy and paste the URL, but I think it would be quite reasonable if that page and any links on it were expired). 4) The ability to discard all backtracking information for a given session. This may be simple to accomplish and already implemented...if so, could someone describe the proper way to do this? There are circumstances (especially relating to security) where you don't want someone to be able to backtrack and use old links...the best example is when a user logs out. I suppose could trash the session and begin a new one, but I like have the session map to a web browser/server interaction, not to a particular authorization context. Seaside is really great guys! - Stephen P.S. Implementing security on top of Seaside has been a dream! Seaside basically has a built in capability framework. Consider that when you hit a seaside component, the only thing a user can do is use the links that have been exposed to him/her on that page. These are the "keys" to the capabilities you've granted your user. All you need to add to the equation is a framework (like ACLs) to guard Seaside's keys.

2 2

Borges 0.1.0 Released
by Eric Hodel 28 Jan '03

28 Jan '03

(This) Borges is a partial port of Seaside to Ruby, done mostly by Avi, and picked up my me, as the maintainer. DESCRIPTION Borges is a web application framework that allows linear programming of web applications. Borges runs on Webrick (Apache+DRb will be supported in the near future) and features a simple rendering interface. Those who are interested will likely be greatly helped by the Seaside 2.0 documentation. You can download Borges (and find more info) at: http://segment7.net/ruby-code/borges/borges.html DEPENDENCIES Ruby: http://www.ruby-lang.org/ - tested on 1.6.8 InstallPkg: http://www.ruby-lang.org/raa.html Webrick: http://www.notwork.org/ipr/webrick/ -- Eric Hodel - drbrain(a)segment7.net - http://segment7.net All messages signed with fingerprint: FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04

1 0

A new Seaside Fan and...a problem with SWebMail...
by Giovanni Giorgi 27 Jan '03

27 Jan '03

Hi All! Ciao! I am a very old Squeak fan, and only today I have seen Seaside!! It is fantastic!! I have used JSP,Struts, Java Servlet and a little of Zope...I have also starting developing small app using the SWiki... but Seaside is into another world!! It merges the power of SmallTalk with the easy of use of the Web! It is easy to use too for developer. It seems to me you can use the MVC model in a very natural way! The tutorial is short but very clear and well written. Is seaside free? Only a small-question: I cannot file in SWebMail http://swiki.squeakfoundation.org/sea/47 because it cannot find a IADialog class...how can I fix it? Who can help me?! Thanks! -- [ [ [ JJ ] ] ] | First, they ignore you. Then they laugh | at you. Then they fight you. Then you win http://www.siforge.org | Mahatma Ghandi

3 3

FW: [Seaside] Seaside + SSP
by Stephen Pair 18 Jan '03

18 Jan '03

> True, and that's what I'll be doing as well. The template > only needs to > get parsed when it changes, not on every request, regardless of where > it comes from. The choice of where to store the template is mostly > determined by work flow. I need to be able to collaborate with a > designer, and external templates make that easier. When I'm doing the > design myself, storing them in methods works fine. Where are you storing the parse tree? > The advantage of keeping the template in tree form is that you can > write the dynamic parts of the page in terms of tree transformations > rather than streaming html and text. Having just written most of an > application in this style, I find I'm very pleased with it. > You end up > with a lot less code for the interface, less coupling between the > presentation and the code, and more focus on the dynamic parts of the > interface. If I modified SSP to actually parse the text portions of an SSP method (as I described in another email) then I can accomplish the same transformations because the resulting compiled code is just directly constructing a parse tree. If you hand it an html renderer, it would spit HTML out on a stream (skipping the step of actually building a parse tree), but if you handed it an HTML parse tree builder, it would give you back an HTML parse tree. I could even support the style of template you described (when the method answers a node). I actually need to do both kinds of templating and I want them to be unified in their approach. I need the compiled SSP style templating for non-user editable templates, and I need an externally stored templating system for user generated templates (which of course wouldn't allow the directly embedded smalltalk code). Eventually, it would be nice to support WebDAV to allow an HTML designer to use traditional tools to access and edit the templates stored as methods. That I think would be the best of both world...you can use the traditional design tools, yet keep your sources all managed with the same system (i.e. monticello). Do you have your templating capability in a workable state? I think I'd like to experiment a little and enable your templating system to be compiled and stored directly as a method. Such a method might look something like: ---- renderContentsOn: renderer <html on: renderer> My name is: Foo My name is: <%= self class name %> <% instvar := 'some side effect value' %> ---- Which would generate bytecodes to the effect of: ---- renderContentsOn: renderer renderer renderingOn: self with: [ renderer renderTag: 'p' contents: [ renderer renderText: 'My name is: '. renderer renderTag: 'span' attributes: {'macro'->'className') contents: [ renderer renderText: 'Foo'. ]. ]. renderer renderTag: 'p' contents: [ renderer renderText: 'My name is: '. renderer evaluateAndOutput: [self class name]. ]. renderer evaluate: [instvar := 'some side effect value']. ]. ---- So, the renderer could directly generate HTML, or it could build a parse tree. For externally or user defined code, we would disallow or ignore the evaluate (smalltalk code) nodes (the parser would simply ignore the "<%" tags). The renderer would decide how to handle the "span" tag. For example, it could ignore the contents block, send #className: to some object that has macro methods, and plug that result into its parse tree (or go ahead and tell the node to output). Another renderer might choose to send #className to the receiver (also ignoring the contents) and output the result. - Stephen

4 4

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 2003