seaside August 2003

seaside@lists.squeakfoundation.org

29 participants
31 discussions

What is the reason for a page to expire?
by Markus Fritsche 30 Aug '03

30 Aug '03

Hi! I've done something completely useless, nevertheless I want to get it done completely. I have built a PHP-script/Seaside wiring which works like the WAModLisp-Connector. I made the counter example run, but I'm stuck now. The reason is that the counter gets display properly, but every link I click says that the page is expired. Where should I search? Regards, Markus

2 6

Seaside serving static contents
by Giovanni Giorgi 30 Aug '03

30 Aug '03

Hi all! I am developing a web application with seaside2. it is very easy indeed... thank you for this framework ;)) I'd like to serve static content. For example I'd like to serve static html documentation and so on. I do not want to install another http server. I have tryed the KomHttpServer-6.1 but i get some errors when I use it. There is a simpler way to integrate static content? For example can I build a simple webapp page to get the same behavior? Thank you a lot! -- [ [ [ JJ ] ] ] | Machines certainly can solve problems, | store information, correlate, and play games http://www.siforge.org | -- but not with pleasure. -- Leo Rosten

3 2

Which db with Seaside?
by Giovanni Giorgi 30 Aug '03

30 Aug '03

Hi all! I am developing an application with Seaside. I'd like to know what Squeak database is suggested in your own opinion and experience. I have tried Magma, but I cannot get it working in some special scenarios. For example Magma seems not supporting nested commits, so I cannot do something like: (...into a callback of componentA...) magmaSession commit:[ self call: anotherComponent ]. (...into a callback of anotherComponent...) magmaSession commit:[ ...etc... ]. What are you using? Minnestore? MySql? Ciao ciao! -- [ [ [ JJ ] ] ] | Machines certainly can solve problems, | store information, correlate, and play games http://www.siforge.org | -- but not with pleasure. -- Leo Rosten

5 9

breadcrumbs
by Avi Bryant 27 Aug '03

27 Aug '03

I've just committed a new (Monticello based) snapshot of Seaside at http://beta4.com/mc/seaside/Seaside2-ab.2.mcz . This includes an example of a breadcrumbs trail (of the kind I was calling "nested", ie, following site hierarchy not workflow steps) as part of the WAStore example. To see it in action, go to /seaside/store. To see the implementation, look at WATrail. This works in the following way: you construct it by giving it the root/home component (WATrail on: home). It will display a path of the series of any nested delegates (that is, the component you #call: from home, then the component you call from that component, etc), that respond to #trailName. #trailName should return a string that will be used to identify that item in the breadcrumb trail. When you click on an item in the trail, that component's delegate will be cleared, which means that the user will be brought back to that point. This is a generalization of the #clearDelegate approach to the Home link that I first suggested to Todd. If this is fuzzy to people, try it out. If it's still fuzzy, I'll explain further... ;) Avi

1 0

ValueHolder use?
by Avi Bryant 27 Aug '03

27 Aug '03

I've seen a few places in my Seaside code recently that benefit from widespread use of ValueHolders - that is, rather than passing in objects directly to components, passing in ValueHolders (or StateHolders) containing them. The cases I'm especially aware of are those where one component is making a selection from a list of objects, and another (or many other) components must update based on that selection. For example, consider the Explorer tool. This has a tree of items down the left, and several tabs showing details of those items on the right. This means that any time someone selects an item in the tree, each of the tab panels has to update which item they are detailing. Right now, the tree notifies its parent of the change, and the parent rebuilds the tab panel in response. This works, but seems unnecesarrily complex, and could be much simplified if all of the components involved - tree, inspector, pretty printer, etc - were expecting a ValueHolder instead of a direct object; the tree would simply change the contents of the holder, and everything would update properly. The problem is that it seems like you can't take this approach by half measures - if any one of the tabs didn't accept a ValueHolder, then the parent would still need to be notified of the update (so that it could notify the errant tab in turn), and you would end up with two inconsistent simple systems instead of one complex one. Does anyone with more experience with this pattern (and with UI events in general) want to comment? It seems like, in general, VW makes heavy use of ValueHolders for UI, whereas Squeak makes more use of #changed events; does anyone know why? Would it make sense to begin sending #value or #contents to all model objects in some types of components, as a matter of policy? Avi

1 0

Static sites and spider handling
by Cees de Groot 26 Aug '03

26 Aug '03

Here's my idea on how to handle spiders for static sites: 1. assumption: a site like http://www.tric.nl/ which has largely static pages that are directly reachable; 2. when a client fetches /robots.txt, the user agent is added to the UA database and a special session id based on the user agent string is created; 3. every time the user agent has a value known in the UA database when a session needs to be created, the same session id is used. This ensures that URL's appear static to the spider; 4. when a link is followed with a 'robot session id' but the UA doesn't match, a new session is created - this represents a real user coming in. I want to make robots.txt accessible maybe with a simple comanche module (or is there a way with Seaside to return data without a redirect to a session first?), so that all hits on the file can be handled from the application server image. Does this sound like a reasonable idea?

5 10

RE: [Seaside] How to do the ubiquitous home button?
by Pennell, David 26 Aug '03

26 Aug '03

How would you generalize this for bread crumb trails? -david > -----Original Message----- > From: Avi Bryant [mailto:avi@beta4.com] > Sent: Friday, August 08, 2003 4:27 PM > To: The Squeak Enterprise Aubergines Server - general discussion. > Subject: Re: [Seaside] How to do the ubiquitous home button? > > > > On Fri, 8 Aug 2003 tblanchard(a)mac.com wrote: > > > I've got a page that wants to have a link on every page > back to home. > > The app has the concept of logging in which provides access > to certain > > features but other features don't require logging in. If I didn't > > have to track the that user had logged in I'd just use a > raw url and > > let them get another session. But I have to keep track of who is > > logged in (if anyone). > > > > The better behavior would be to backtrack until the page is > the home > > page (ie - recover to the last home page view). > > > > Suggestions for a general solution? (I could do custom > implementation > > of this button on each page but I'd rather not). > > - Create a frame component, and set it as your entry point. > This should have a 'contents' ivar which holds the home > component. Its > #renderContentOn: should look, minimally, like > > renderContentOn: html > html anchorOn: #home of: self. > html render: contents > > - Add a #home method which looks like this: > > home > contents clearDelegate > > This will clear away the #call: chain and snap you back to > the original component. > > That make any sense? > > _______________________________________________ > Seaside mailing list > Seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/listinfo/seaside >

4 6

RE: [Seaside] Displaying Seaside Components in frames
by Ben Schroeder 21 Aug '03

21 Aug '03

Avi Bryant wrote: > Ah, good point. I hadn't thought of that. > > So, yeah, for now the way you did it is the only easy way. > Maybe there > should be a way to somehow turn off the body tag in > WAHtmlResponse... ? Or something like the way <head> children are handled? Frameset children are also pretty well-structured, so maybe WAHtmlResponse could have an optional frameset element that WAHtmlBuilder could enable and add children to when necessary. If that was implemented, whether to turn off the <body>, or wrap it in a <noframes> for browsers without frames, or just leave it on - I'm not sure. It looks like the IE and Mozilla that I have both ignore <body> if it comes after <frameset>, but those are just two browsers on one OS. Regards, Ben Schroeder

1 0

RE: [Seaside] Displaying Seaside Components in frames
by Ben Schroeder 21 Aug '03

21 Aug '03

Avi Bryant wrote: > An obvious thing that should be done to clean this up is to implement > #frameWithUrl: and #frameWithAction: on HtmlBuilder and HtmlRenderer > respectively; this would then become > > html attributes rows: '10%, 90%'. > html frameset: [ > html frameWithAction: [self call: PrintOrFax new]. > html frameWithUrl: self imageUrl. > ] Hi Avi, Thanks, that looks good to me - much more like the rest of the rendering I've seen in Seaside. There might be a problem: framesets (so it seems) can't be children of <body>, but instead need to be direct children of <html>. (... at least in the version of IE I'm using, but they're that way in the W3C examples.) WAHtmlResponse inserts a Body tag near the beginning of its rendering, a while before it gets to my Component. One thing to do would be to reinitialize the <body> to be a <frameset>, but that seems odd to me - plus I would still have to get the attributes in there. Maybe I could factor WAHtmlResponse around so that I could get one that works with frames, and use a new renderer instance and #returnResponse: with one of those. (It's not a very big deal to me today in any case - we're using frames more because of a printing situation than anything else, and the Generic Response with a little more factoring would be OK in this situation.) Any thoughts? I of course might be missing something that's there... :) Thanks, Ben

2 1

RE: [Seaside] Displaying Seaside Components in frames
by Ben Schroeder 21 Aug '03

21 Aug '03

I wrote: > Hi all, > > We've just started trying Seaside for a project we're doing > here where I work. Thanks, Avi, Julian, and everyone else > for such a neat system. > > At one point in our project, we'd like to display a Seaside > Component in one frame and some image or PDF content in > another, but most of our application is not frames-based. > I'm not sure how to go from the non-frames part to the frames > part while maintaining the state of the program. > > Does anyone have any pointers on how to run a frameset in Seaside? Well, I think I may have come up with a solution. Here it is, both in the hope that it might be useful and in case I've missed something subtle. I responded with a WAGenericResponse that contained my frameset HTML, including URLs to the image and to the next page of my application. The part that I was struggling with was what URL to use for the next page. It ends up that I could use WAHtmlRenderer>>#urlForAction: to do what I needed (which makes sense now that I know). Here's something like my code for creating the response. | response | response _ WAGenericResponse new nextPutAll: '<html><frameset rows="10%, 90%">'; nextPutAll: '<frame src="'; nextPutAll: (html urlForAction: [self call: PrintOrFax new]); nextPutAll: '" />'; nextPutAll: '<frame src="'; nextPutAll: self imageUrl; nextPutAll: '"/>'; nextPutAll: '</frameset></html>'. self session returnResponse: response. Thanks, Ben Schroeder

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 August 2003