Thanks ! Are you aware of a working application already done with Seaside and Scriptaculous ?

Some newbie questions : what means WA in WACounter ? And is there a possibility to get rid of the unreadable section "?_k=RLuphTHk&_s=IkufVPbXiraGKGSB" on the url - maybe by using a cookie ? I'd like to get a readable url and hide what is not human-understandable... (Why ? In fact, I'm studying the use of the url box as a kind of command line for webpage seen as object "www.foo.net/myappli render: 'hello world'")

Maybe these questions are in the FAQ but didn't find it on the seaside website !

By the way, I tried the 2.6 image version from seaside, and got an error when trying to browse the source code of the counter (section scriptaculous) :

MessageNotUnderstood: SUAllTests>>show:onAnswer:delegation:

* SUAllTests(Object)>>doesNotUnderstand: #show:onAnswer:delegation: ...

"Lukas Renggli" renggli@gmail.com writes:

...

Does someone know if such a techno is available for squeak (maybe seaside ?). I'm especially interested in the "post-it" feature we are using intensively. With netvibes, you have just to drag and drop a post-it on the desk and write on it, all is saved on the fly (no more "save" button as it is the case for wikis). I find this simple feature really cool !

Yes, you can do all kind of fancy AJAX things with Seaside quite easily. Have a look at the functional test-suite at http://scriptaculous.seasidehosting.st.

Lukas

-- Lukas Renggli http://www.lukas-renggli.ch

Thanks ! Are you aware of a working application already done with Seaside and Scriptaculous ?

Yes, DabbleDB <www.dabbledb.com> and SeasideHosting <www.seasidehosting.st> are both using script.aculo.us in production.

"?_k=RLuphTHk&_s=IkufVPbXiraGKGSB" on the url - maybe by using a cookie ? I'd like to get a readable url and hide what is not human-understandable... (Why ? In fact, I'm studying the use of the url box as a kind of command line for webpage seen as object "www.foo.net/myappli render: 'hello world'")

Seaside is different. You can use Seaside to do that kind of things, but that is not the idea behind the framework: Seaside is all about hiding the low-level aspects of URLs, HTTP-Requests, HTTP-Responses, etc. Seaside provides you with tools to easily model flows of pages, to compose and reuse widgets, to build state-full web applications, etc.

Still it is possible to move the session key into a cookie, by setting the configuration option of the application, though most people don't bother about this. Seaside is strong at building highly interactive web applications, not at building static web sites with REST-full URLs.

By the way, I tried the 2.6 image version from seaside, and got an error when trying to browse the source code of the counter (section scriptaculous) :

MessageNotUnderstood: SUAllTests>>show:onAnswer:delegation:

* SUAllTests(Object)>>doesNotUnderstand: #show:onAnswer:delegation:

You need a more recent version of Seaside, try Seaside2.6a3-lr.67

Cheers, Lukas

Those session keys can bother if someone wants to add the www into the favourites and the browser saves the URL with the key. You must delete the key from the URL manually, and this does not have to be obvious for everyone.

No, this is not true. When using the bookmarked URLs your session will probably have expired and you will be automatically redirected to the application entry point. Authors of applications might decide to add additional info to the URL to be able to restore some state in such a case. Pier is an example of such a web-application.

Lukas

Something which prevents me to switch on peer is this story of url format. I dig into the config option to see if I can get rid of it (by setting the session cookie to true), but it does nothing !

For me it works for what this option advertises: it removes the _s parameter (the session id) from the URL, tough it keeps the _k parameter (the continuation id) untouched.

I'm aware that there is probably some good reasons about this story of URL, but could you tell me if the url format can not be changed because it's structural to the seaside framework, or if there is a way to get rid about it (by modifying the code ?).

The problem with the _k parameter is that I cannot be stored in cookies, without loosing the possibility to support the back button. If you think (personally I do not) having a nice URL is more important than supporting the back button you could easily put the _k parameter into cookies as well.

I'd really like to get a human-readable url format.

You could maybe trick that using a single frame and JavaScript.

Cheers, Lukas