seaside March 2003

seaside@lists.squeakfoundation.org

22 participants
28 discussions

anchors behaving like buttons?
by Derek Brans 26 Jun '03

26 Jun '03

In Seaside, is there a way to have an anchor tag that will submit a form and perform an action (behaving just like a button)? 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

15 30

inHeadDo:
by Nevin Pratt 13 Jun '03

13 Jun '03

In Seaside 2.21, the renderer has the #inHeadDo: method. For Seaside 2.3, the renderer appears to be significantly changed. Where's the equivalent of #inHeadDo:? Nevin

3 9

Nearing 2.3
by Avi Bryant 08 Apr '03

08 Apr '03

Hi all, I'm putting up a 2.3a snapshot for evaluation at http://beta4.com/seaside2/downloads/Seaside2-3a.st. I made a number of fairly large changes recently, and I've been feeling antsy that they're only available to the (non-existant?) minority of users that track CVS. This code isn't totally complete, but please do try it out. The changes include: - HtmlRenderer now builds a DOM tree rather than directly printing HTML to a stream. This provides a greater amount of flexibility in various places, without (surprisingly) seeming to impact performance. A more minor change (stolen from Cees) is the ability to use either strings of blocks pretty much anywhere, ie, html bold: 'foo'. html bold: [html text: 'foo']. - The StateHolder mechanism has been generalized so that any object can be registered to have the values of its instance variables backtracked. For example, in WABrowser>>model:, you'll see self session registerObjectForBacktracking: model. This means that the state of the Browser instance will be snapshotted each time it changes, and using the back button in the web-based browser will have correct behavior. Component classes that previously used StateHolders for all (or most) of their instance variables can now simply register themselves for backtracking at #initialize time. Yes, this can eat memory quickly if abused. A "profile memory" link has been added to the toolbar to keep tabs on this. - The fairly complex Container model has been replaced with a much simpler notion of delegated components. Each component has a 'delegate' StateHolder. When a component is asked to #call: another component, it stores that component as its delegate. When the #call: returns, 'delegate' will be cleared. When asked to render itself, a component with an active delegate will forward the render request to the delegate. This means that a component will appear to be replaced, in place, by whichever component it calls. This behavior is roughly equivalent to having each child component created with #containerFor: in 2.2. The "inspect" link now presents a view of the current component tree, showing delegation, so that you can pick which component you want to inspect. This can be useful for understanding the new model. - The codebase has been massively restructured and more cleanly layered. Some semi-coherent notes: The "Base" layer consists of Request, Response, and a completely new URL handling mechanism, the WARegistry. This knows nothing about Sessions, but flexibly manages request handlers that map either to static urls or to unique, generated keys. If a unique key exists in the url but there is no active handler for it, the registry will fall back to the closest static handler. The "Session" layer adds continuations and state backtracking. It knows nothing about Components. The "Component" layer includes the delegation and embedding model. For now, it largely shields user code from the changes to the other layers (#registerAsApplication: still works, for example). It also includes all the development and configuration tools. The "Rendering" layer is mostly orthogonal to all of this; it provides the callback scheme and HtmlRenderer. Known issues: - The Wiki example is currently broken. - The new HtmlRenderer does not yet support pretty-printing. - Usage patterns for Application, Session, and Registry have to be more fully worked out (where does the current notion of preferences go? Is it still appropiate to subclass Session? etc).

4 13

JavaScript anyone?
by Nevin Pratt 02 Apr '03

02 Apr '03

I'd like to know the feeling of the folks on this list concerning the use of JavaScript in web apps. I'm thinking of using a little JavaScript, but am a bit concerned about the folks out in the world who run their browsers without JavaScript being enabled. I would like to have a page with "Next Image" and "Previous Image" buttons that when pressed, shows another photo. However, I don't want the entire page to need to get refreshed. I would like *just* the image to change-- nothing more. The only way I know of to do that is via JavaScript. A specific example of JavaScript code that can do this can be found at: http://www.jsmadeeasy.com/javascripts/Images/Image%20Gallery/list.htm Nevin

8 23

action method cause independent redirect
by Nevin Pratt 31 Mar '03

31 Mar '03

I am using Seaside 2.3b. I have a component that has a button with an action method. That action method needs to be able to redirect the web request to a completely different web site. How do you do that? In case I'm not being clear, I will explain again, but using a Comanche module to illustrate. As you know, any registered Comanche module will execute the #process: method of the module when a web request comes in. The argument to the #process: method is an instance of HttpRequest (you will see that the argument is typically named 'request' if you browse implementers of #process:). Anyway, to redirect the HttpRequest coming into a Comanche module, you would do this from the #process: method of your Comanche module: process: request ^ request redirectTo: 'http://www.anywhere.com/somepath' For the Comanche module, you can also just as easily redirect to a secure port of some web site thus (just by specifying https instead of http): process: request ^ request redirectTo: 'https://www.anywhere.com/somepath' And in reality, this is what I really want to do from the action method of the button for a Seaside component-- redirect the request to a secure port of an arbitrary web URL via an 'https' redirect. How do I do that? Nevin

3 2

CVS logs
by Avi Bryant 29 Mar '03

29 Mar '03

Keith Hodges writes: > Hello all, > I took the plunge of looking at the CVS distribution and thought some > people might like to see that there is loads of info in the cvs log > that is useful. Design intent things are always handy to know. > Keith But mailman complained about the size of the attached log, so his message didn't go through. At any rate, you're probably better to look at the log here instead: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/seaside/aubergines/seaside/S… Avi

1 0

2.3 beta
by Avi Bryant 29 Mar '03

29 Mar '03

Hey all, I've put a 2.3 beta snapshot up at http://beta4.com/seaside2/downloads/Seaside2-3b.st The major changes since the last snapshot include: - the pretty printing feature is back (and no longer breaks <textarea>s) - fixed a backtracking bug - fixed the "debug" link on the walkback page I don't expect there to be much changing between this snapshot and the 2.3 release except in the Examples and Tutorial areas. If you're already using a 2.3 snapshot, or aren't but want to move to the not-so-bleeding edge, please upgrade to this one so we can catch any last kinks. Also, since it seems like half my posts to this list in the last week have been of the form "all you need to do is add method X to HtmlRenderer", here's a request: if anyone has any convenient rendering methods they've added, please post changesets with them in the next few days, so that I can merge them in before releasing. Cheers, Avi

2 1

[Q] two questions...
by Adrian Lienhard 29 Mar '03

29 Mar '03

Hi Seasiders! - I'd like to open a popup window which displays a component. How can I do this (not the javascript part)? WASession>>urlForDocument: seems to be something like I look for. But it doesn't work with a component as the argument. Any suggestions? - I should have more than one entrypoint for an application. For each entrypoint (there are several different domain names) there should be a seperate component rendered. With Apache I could e.g. map to different paths (such as: ...:8080/seaside/app/domain1/ ...app/domain2/ etc). Section keys seem to go into this direction but don't solve the problem. How could this be done? I'm using v2.2 at the moment Thanks for help or ideas Adrian _____________________ Adrian Lienhard www.adrian-lienhard.ch www.netstyle.ch

2 2

Getting more started
by Brian Brown 28 Mar '03

28 Mar '03

Thanks for your response before, Avi.... Ok, I have created my own class for playing with and successfully registered it. I've started playing with the various messages in the Generator (lists, tables, etc.) and now understand how these work together... very slick! =) Now, let's pretend I want to build an app with 3 "pages" from the user perspective, with a menu that is context sensitive (indicating which page you are on). How would I go about architecting this? One component per page and another one for the menu, rendering the menu component from each page component? And assuming I wanted each page to have the same layout, would I create a Class message that has the layout code in it, or would that be another component? (Or am I missing the boat entirely?) Not being too familiar with Squeak isn't helping me much, but I'm learning! Brian

5 6

AW: [Seaside] WAKom not receiving requests
by Christian Daszenies 28 Mar '03

28 Mar '03

> I've had it happen when some other OS process had the port > tied up. In > one particular case, I had two Squeak images running, and the other > Squeak image had the port. Once it happened, quitting the > other image > (if that was *all* I did) didn't seem to help. So, my usual > solution is > to: (1) save image, (2) quit all images, (3) make sure > nothing else is > running that might have the port, and (4) relaunch the single image. At least on unix/linux it's easy to check if some process is listening on a particular port: netstat -an | grep 8001 Windows 2000 understands 'netstat -an' as well - unfortunately there is (usually) no 'grep' available. Might be easyer to check what's going on than quitting all apps. Christian

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside March 2003