seaside-dev March 2013

seaside-dev@lists.squeakfoundation.org

13 participants
13 discussions

Seaside Configuration in 2.0
by phil＠highoctane.be 02 Apr '13

02 Apr '13

Same story for me. Is there now a config (like we could load from the Configurations tool of Pharo2.0? All the ones in there do now work.) What works was what I found in the mailing list and on Lukas Renggli scripts: "Basic" Gofer new squeaksource: 'Seaside31'; package: 'Grease-Core'; package: 'Grease-Pharo20-Core'; package: 'Grease-Tests-Core'; package: 'Grease-Tests-Pharo20-Core'; package: 'Seaside-Core'; package: 'Seaside-Pharo20-Core'; package: 'Seaside-Tests-Core'; package: 'Seaside-Tests-UTF8'; package: 'Seaside-Tests-Pharo20-Core'; package: 'Seaside-Canvas'; package: 'Seaside-Pharo-Canvas'; package: 'Seaside-Tests-Canvas'; package: 'Seaside-Session'; package: 'Seaside-Tests-Session'; package: 'Seaside-Component'; package: 'Seaside-Tests-Component'; package: 'Seaside-RenderLoop'; package: 'Seaside-Tests-RenderLoop'; package: 'Seaside-Tools-Core'; package: 'Seaside-Widgets'; package: 'Seaside-Environment'; package: 'Seaside-Pharo-Environment'; package: 'Seaside-Tests-Environment'; load. "Traditional" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Tests-Functional'; package: 'Seaside-Tests-Pharo-Functional'; package: 'Seaside-Pharo-Continuation'; package: 'Seaside-Tests-Pharo-Continuation'; package: 'Seaside-Flow'; package: 'Seaside-Pharo-Flow'; package: 'Seaside-Tests-Flow'; package: 'Seaside-Tools-Web'; package: 'Seaside-Pharo20-Tools-Web'; package: 'Seaside-Tests-Tools-Web'; package: 'Seaside-Development'; package: 'Seaside-Pharo-Development'; package: 'Seaside-Tests-Development'; package: 'Seaside-Tests-Pharo-Development'; package: 'Seaside-Examples'; package: 'Seaside-Tests-Examples'; load. "RSS" Gofer new squeaksource: 'Seaside31'; package: 'RSS-Core'; package: 'RSS-Tests-Core'; package: 'RSS-Examples'; load. "Javascript" Gofer new squeaksource: 'Seaside31'; package: 'Javascript-Core'; package: 'Seaside-JSON-Core'; package: 'Seaside-Pharo-JSON-Core'; package: 'Javascript-Pharo20-Core'; package: 'Javascript-Tests-Core'; package: 'Javascript-Tests-Pharo-Core'; package: 'Seaside-Tests-JSON'; package: 'JQuery-Core'; package: 'JQuery-Tests-Core'; package: 'JQuery-JSON'; package: 'JQuery-Tests-JSON'; package: 'JQuery-UI'; package: 'JQuery-Tests-UI'; package: 'Prototype-Core'; package: 'Prototype-Tests-Core'; package: 'Scriptaculous-Core'; package: 'Scriptaculous-Tests-Core'; package: 'Scriptaculous-Components'; package: 'Scriptaculous-Tests-Components'; package: 'Comet-Core'; package: 'Comet-Examples'; package: 'Comet-Pharo-Core'; package: 'Comet-Tests-Core'; load. "Other Packages" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Welcome'; package: 'Seaside-Pharo-Welcome'; package: 'Seaside-Tests-Welcome'; package: 'Seaside-HTML5'; package: 'Seaside-Tests-HTML5'; package: 'Seaside-InternetExplorer'; package: 'Seaside-Tests-InternetExplorer'; package: 'Seaside-Email'; package: 'Seaside-Tests-Email'; package: 'Seaside-Pharo-Email'; package: 'Seaside-Tests-Pharo-Email'; load. "REST" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-REST-Core'; package: 'Seaside-Pharo-REST-Core'; package: 'Seaside-Tests-REST-Core'; load. "This does not yet load an adaptor. You can go find ZnZincServerAdaptor in the Zinc repository, like this (updating all Zn):" Gofer new url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'Zinc-HTTP'; package: 'Zinc-Tests'; package: 'Zinc-FileSystem'; package: 'Zinc-Seaside'; load. "And finally," ZnZincStaticServerAdaptor startOn: 8081. ZnZincStaticServerAdaptor stop. "The method String>>includesSubString: has been deprecated. Bad spelled, the good one is #includesSubstring: Select Proceed to continue, or close this window to cancel the operation."

7 22

Kaliningrad>>documentForFile: MNU
by phil＠highoctane.be 31 Mar '13

31 Mar '13

When doing http://localhost:8088/Kaliningrad/js/amber.js I do get: MessageNotUnderstood: KOAmberJSFileLibrary>>documentForFile: Kaliningrad is loaded in my image. What is documentForFile: doing? Where can I find a version of that? Googled already. Selector isn't in my image. TIA Phil

1 0

Seaside image and startup time
by phil＠highoctane.be 31 Mar '13

31 Mar '13

Hello, I've loaded 3.1 in Pharo 2.0 and use a ZnAdaptor. I loaded SmalltalkHub packages and other dependencies I've found for making it work. Now, when starting the image, it takes a long time for me to get the display filled wit the windows etc. What could this be linked to? I have removed the Kalingrad entry to be sure that the other Seaside stuff worked. (WADispatcher allInstances first handlers) removeKey: 'Kaliningrad'. And indeed all worked fine. But still the load time is long (Core 2 Duo Mac OSX Lion 8GB RAM). I am going to dig into StartupLists etc. Thanks! Phil

1 0

semantics of WACookie >> #path
by Philippe Marschall 30 Mar '13

30 Mar '13

Hi I'm currently looking into issue 749 [1] which turned out to be an interesting encoding issue. While going through all the senders of #pathString I noted that the current semantics of WACookie >> #path(:) aren't really well defined. Looking at the code they currently seem to be: * unescaped when setting a cookie on the server * the http header value (likely escaped) when sent from the client to the server This isn't as bad as it sounds since Opera was the only sane implementation that would send the path back to the server (so that the server can delete a cookie) and they're dumping their code base for Chrome (or Chromium). But it's still an issue when we want to support session cookies for non-ASCII paths. So the question is should the path be escaped or not? Traditionally we try to offer high level objects to the user that are directly useful without having to do some parsing or decoding first. However a string isn't actually that high level, a SequenceableCollection would be. As far as I can see our options are: * make it an unescaped string * make it an escaped string * make in an escaped SequenceableCollection Also, do we do the same on 3.0 and 3.1? [1] http://code.google.com/p/seaside/issues/detail?id=749 Cheers Philippe

1 0

Please add this MCZ to the Seaside Repository
by Tobias Pape 24 Mar '13

24 Mar '13

Dear Seaside developers, please add the attached mcz to the Seaside Repository, so that it can be used in a Metacello Configuration. This version essentially is the former WASqueakServerAdaptorBrowser before it was made Pharo-WorldMenu compatible. I resurrected the former version as it contains the code necessary to register the Seaside Control Panel in Squeak. Best -Tobias

2 4

Seaside3.0.x on Pharo2.0 ?
by Johan Brichau 24 Mar '13

24 Mar '13

Hi everyone, I'm busy loading and fixing stuff for Seaside3.0.7.1 on Pharo2.x Since I'm mostly doing rather simple stuff to make it work, I wonder if really nobody else has already done this. So... is there a more specific reason that this has not happened yet? I would really want to have Seaside3.0.x on Pharo2.0 as well, not just Seaside3.1. Johan ps: I'm perfectly happy doing this, unless I'm repeating someone else's work ;-)

4 4

Initial Request Failure on Retry
by Ken Treis 24 Mar '13

24 Mar '13

We have build something using the Seaside-Rest add-on, and everything works beautifully in GemStone until a transaction conflict triggers a retry -- at which point we get a 404 rather than the expected response. We tracked the issue down to the WAPathConsumer, which keeps track of the path (destructively) as the request is being resolved. Its state isn't being reset before the request is retried, so subsequent requests are effectively tried against a different path. We've fixed in our home-grown Zinc streaming adaptor by adding the following line just before we retry: > aRequestContext consumer initializeWith: aRequestContext request url path copy This is admittedly a dreadful encapsulation violation. Ideally, maybe we'd implement something like #reset on WARequestContext. There is some other internal state (like `handlers`) that should probably be reset too, though I think in practice the use of #ensure: in #push:during: empties out the handlers collection before handling is retried. Alternately, we could perhaps make WAPathConsumer non-destructive and implement #reset there. It already acts a bit like a stream, so a #reset method would not be too out of place there. Thoughts? -- Ken Treis Miriam Technologies, Inc.

3 4

Seaside on Squeak
by Tobias Pape 24 Mar '13

24 Mar '13

Dear Seaside developers I plan to make Seaside 3.0.x available for the stable Squeak 4.4 and also Squeak Trunk. I would like to adapt the Metacello configuration for that, please tell me whether I should * modifiy the existing release (3.0.7), * create a new point release (3.0.7.2), * or make it a new release (3.0.8) Other than that, I made Seaside 3.1 load in Squeak 4.4. The respective configurations for Grease and Seaside can be found at > http://netshed.de/seaside/ConfigurationOfGrease-topa.191.mcz > http://netshed.de/seaside/ConfigurationOfSeaside30-topa.415.mcz Feel free to review and integrate them with your development process. Best -Tobias

5 7

Fwd: [Seaside Issues] Issue 749 in seaside: Zinc - Wrong handling of urls encoded in UTF8
by Julian Fitzell 13 Mar '13

13 Mar '13

Sven, Not sure if you will have seen this. From the description it looks like this might be a Zinc issue. Do you have somewhere to track bugs? Julian ---------- Forwarded message ---------- From: <seaside(a)googlecode.com> Date: Mon, Mar 11, 2013 at 10:01 PM Subject: [Seaside Issues] Issue 749 in seaside: Zinc - Wrong handling of urls encoded in UTF8 To: issues(a)lists.seaside.st Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 749 by j...(a)struz.cz: Zinc - Wrong handling of urls encoded in UTF8 http://code.google.com/p/**seaside/issues/detail?id=749<http://code.google.com/p/seaside/issues/detail?id=749> What steps will reproduce the problem? - enter an url in UTF8 (non-ASCII) What is the expected output? What do you see instead? triggers "SubscriptOutOfBounds", or "Error: Improper store into indexable object" (near ZnZincServerAdaptor) What version of the product are you using? On what operating system? Pharo 1.4, Seaside 3.0.7 Please provide any additional information below. Live BUG example: http://book.seaside.st/book/%**C3%A1%C4%8D<http://book.seaside.st/book/%C3%A1%C4%8D> Seaside on localhost: http://localhost:8080/%C3%A1%**C4%8D <http://localhost:8080/%C3%A1%C4%8D> http://localhost:8080/browser/**%C3%A1%C4%8D<http://localhost:8080/browser/%C3%A1%C4%8D> -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/**hosting/settings<https://code.google.com/hosting/settings> ______________________________**_________________ issues mailing list To unsubscribe, email issues-leave(a)lists.seaside.st http://lists.seaside.st/**listinfo/issues<http://lists.seaside.st/listinfo/issues>

2 1

get value from the link. or request parameter
by sarath raj 11 Mar '13

11 Mar '13

I would like to get the value from the parameter . How it is posible in seaside . Suppose i have http://localhost:9090/testingApp?a=sarathraj99@gmail.com how can i request the value from the link , like requestParameter("a") in java . -- Sarath Raj

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev March 2013