Seaside 2.8.3 is the fourth maintenance release for Seaside 2.8. It
includes small fixes and improvements. For more information see the change-log below. You can get it from SqueakMap, Package Universes or Monticello (Seaside2.8a1-lr.590). There you'll also find updated, matching versions for Scriptaculous, Comet, Magritte, Pier and RSRSS. The One-Click image has been updated as well, it is now based on closure enabled Pharo. At your convenience it can be downloaded from <http://www.seaside.st/distributions/Seaside-2.8.4.app.zip>. Changes: - Full block closure support. - Fixes related to multipart form fields. - Support for upload streaming with Kom. - Various community enhancements Scriptaculous and other extra libraries. For a listing of past and current Seaside releases check the summary at <http://code.google.com/p/seaside/wiki/PastReleases>. Cheers, The Seaside Team _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Fri, Jun 5, 2009 at 4:31 PM, Lukas Renggli <[hidden email]> wrote: Seaside 2.8.3 is the fourth maintenance release for Seaside 2.8. It Excellent news!!! Will you also create a new one click Pier image using seaside 2.8.4? Thanks and congratulations for the good work! Mariano
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
>> Seaside 2.8.3 is the fourth maintenance release for Seaside 2.8. It
>> includes small fixes and improvements. For more information see the >> change-log below. Upps, of course I was referring to Seaside 2.8.4. > Excellent news!!! Will you also create a new one click Pier image using > seaside 2.8.4? In fact the Seaside 2.8.4 developer image also contains the latest Pier code. So, if you don't mind the Seaside branding and that the image contains the latest development code of Pier (not a numbered release), feel free to use this image. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Fri, Jun 5, 2009 at 2:44 PM, Lukas Renggli <[hidden email]> wrote:
Ok, I did it but I found 2 problems (fixed): 1) This image doesn't have the MC package XMLSupport (XML-Parser package). So, if you try to use Import/Export Pier widget, you will have a "key not found" in DataStream>>readInstance when it tries to do: newClass := Smalltalk at: aSymbol #XMLDocument asSymbol. After installing that package, it worked. I think this sohuld be added to the standard image or something. 2) In my case, SULibrary was making my app not to render properly. I removed it and then it works perfect. I hope this helps. I will let you know if I have more problems. Cheers, Mariano
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> 1) This image doesn't have the MC package XMLSupport (XML-Parser package).
> So, if you try to use Import/Export Pier widget, you will have a "key not > found" in DataStream>>readInstance when it tries to do: > > newClass := Smalltalk at: aSymbol #XMLDocument asSymbol. > > After installing that package, it worked. > > I think this sohuld be added to the standard image or something. I don't think this is a bug in the image. The Import/Export widget does not depend on XMLDocument. You have to ensure yourself that all the classes required by the model you are trying to import are present in the target image. > 2) In my case, SULibrary was making my app not to render properly. I removed > it and then it works perfect. This is strange, because SULibrary works for other applications and the default Pier installation. Furhtermore I don't see how SULibrary is related to rendering? Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Sun, Jun 7, 2009 at 6:36 AM, Lukas Renggli <[hidden email]> wrote:
Why do you say Import/Export widget doesn't depend on XMLDocument? I am sorry. I don't understand. In my case, when debugging I noticed that I need it, not my app model, but the exporter itself. You have to ensure yourself that all Which Model? I guess you mean my app model.
I think this is related with css styles and the order in which the library are added. Mariano
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
>> > 1) This image doesn't have the MC package XMLSupport (XML-Parser
>> > package). >> > So, if you try to use Import/Export Pier widget, you will have a "key >> > not >> > found" in DataStream>>readInstance when it tries to do: >> > >> > newClass := Smalltalk at: aSymbol #XMLDocument asSymbol. >> > >> > After installing that package, it worked. >> > >> > I think this sohuld be added to the standard image or something. >> >> I don't think this is a bug in the image. The Import/Export widget >> does not depend on XMLDocument. > > Why do you say Import/Export widget doesn't depend on XMLDocument? I am > sorry. I don't understand. In my case, when debugging I noticed that I need > it, not my app model, but the exporter itself. You say that the problem appears in DataStream>>#readInstance, this method is called when you import a Pier model. The method tries to instantiate a class that is referenced from your exported Pier model, but that is missing in the image you import to. Before you import you have to make sure that all the plugins you used in your export are properly loaded. >> > 2) In my case, SULibrary was making my app not to render properly. I >> > removed >> > it and then it works perfect. >> >> This is strange, because SULibrary works for other applications and >> the default Pier installation. Furhtermore I don't see how SULibrary >> is related to rendering? > > I think this is related with css styles and the order in which the library > are added. SULibrary does not contain any styles, just Javascript code. Maybe it is conflicting with some other Javascript code you are using? Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
On Sun, Jun 7, 2009 at 3:29 PM, Lukas Renggli <[hidden email]> wrote:
Ok but then I must know that Import/Export widget depends on an external package like XMLParser? I didn't know that till I debugg it.
wierd. I will try to look more in details and let you know if I have more information. Thanks! Mariano
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> Ok but then I must know that Import/Export widget depends on an external
> package like XMLParser? I didn't know that till I debugg it. No, it is not the Import/Export widget that depends on an external package. It is the serialized file that you upload/import that depends on an external package. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Lukas Renggli
I've updated the Seaside 2.8.4 one-click image with Seaside2.8a1-lr.591.
This version resolves an issue related to closures and walkback rendering. This version should also work in pre-closure images, thanks to <http://code.google.com/p/seaside/issues/detail?id=392>. SqueakMap and Package Universe are up-to-date as well. Also I've updated to the very latest Pharo code, this means the one-click image is fully MIT compliant now. Furthermore, for the sushi lovers, I've added the Sushi Store example application. Cheers, Lukas On Fri, Jun 5, 2009 at 7:31 PM, Lukas Renggli<[hidden email]> wrote: > Seaside 2.8.4 is the fourth maintenance release for Seaside 2.8. It > includes small fixes and improvements. For more information see the > change-log below. > > You can get it from SqueakMap, Package Universes or Monticello > (Seaside2.8a1-lr.590). There you'll also find updated, matching > versions for Scriptaculous, Comet, Magritte, Pier and RSRSS. The > One-Click image has been updated as well, it is now based on closure > enabled Pharo. At your convenience it can be downloaded from > <http://www.seaside.st/distributions/Seaside-2.8.4.app.zip>. > > Changes: > - Full block closure support. > - Fixes related to multipart form fields. > - Support for upload streaming with Kom. > - Various community enhancements Scriptaculous and other extra libraries. > > For a listing of past and current Seaside releases check the summary > at <http://code.google.com/p/seaside/wiki/PastReleases>. > > Cheers, > The Seaside Team > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
I'm writing an A/B testing framework in Seaside. All is going very
well except that I've discovered if a visitor to the site being tested hits the back button all the way back to the initial page then there is no s key in the URL, so Seaside makes a new session. This will cause my visitor click tracking to lose track. It wouldn't be a big problem if I were able to get the visitor's IP address, but I can't because this server will be proxied behind Apache. So, is there any way I can force the initial page view to have the s and k keys? Thanks, -Carl _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Carl Gundel wrote:
> I'm writing an A/B testing framework in Seaside. All is going very > well except that I've discovered if a visitor to the site being tested > hits the back button all the way back to the initial page then there > is no s key in the URL, so Seaside makes a new session. This will > cause my visitor click tracking to lose track. It wouldn't be a big > problem if I were able to get the visitor's IP address, but I can't > because this server will be proxied behind Apache. > > So, is there any way I can force the initial page view to have the s > and k keys? > Michael _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Also, you _can_ find client IP as per,
http://httpd.apache.org/docs/trunk/mod/mod_proxy.html#x-headers and, http://en.wikipedia.org/wiki/X-Forwarded-For and, WASession>>clientIP | req | req := self currentRequest. ^req headerAt: 'x-forwarded-for' ifAbsent: [req nativeRequest remoteAddress]. Hope this helps, -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 http://tinyurl.com/r7uw4 [hidden email] CONFIDENTIALITY NOTICE This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments. Thank you. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Michael Lucas-Smith Sent: Wednesday, June 24, 2009 3:10 PM To: Seaside - general discussion Subject: Re: [Seaside] [2.8]Back button, new sessions and forcing s and kkeys in the initial URL Carl Gundel wrote: > I'm writing an A/B testing framework in Seaside. All is going very > well except that I've discovered if a visitor to the site being tested > hits the back button all the way back to the initial page then there > is no s key in the URL, so Seaside makes a new session. This will > cause my visitor click tracking to lose track. It wouldn't be a big > problem if I were able to get the visitor's IP address, but I can't > because this server will be proxied behind Apache. > > So, is there any way I can force the initial page view to have the s > and k keys? > Make your initial page a WATask which calls your first WAComponent. Michael _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Michael Lucas-Smith-3
On Wed, Jun 24, 2009 at 11:09 PM, Michael Lucas-Smith <[hidden email]> wrote:
In 2.8. I think that redirect is no longer there in 2.9. But you could still use a Task and put "self requestContext redirect" at the beginning.
Julian _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Lukas Renggli
On Jun 24, 2009, at 10:48 AM, Lukas Renggli wrote: > I've updated the Seaside 2.8.4 one-click image with Seaside2.8a1-lr. > 591. > > This version resolves an issue related to closures and walkback > rendering. This version should also work in pre-closure images, thanks > to <http://code.google.com/p/seaside/issues/detail?id=392>. SqueakMap > and Package Universe are up-to-date as well. > > Also I've updated to the very latest Pharo code, this means the > one-click image is fully MIT compliant now. Furthermore, for the sushi > lovers, I've added the Sushi Store example application. yeah cool! Stef _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Michael Lucas-Smith-3
On Jun 24, 2009, at 6:09 PM, Michael Lucas-Smith wrote:
> Carl Gundel wrote: >> I'm writing an A/B testing framework in Seaside. All is going very >> well except that I've discovered if a visitor to the site being >> tested hits the back button all the way back to the initial page >> then there is no s key in the URL, so Seaside makes a new session. >> This will cause my visitor click tracking to lose track. It >> wouldn't be a big problem if I were able to get the visitor's IP >> address, but I can't because this server will be proxied behind >> Apache. >> >> So, is there any way I can force the initial page view to have the >> s and k keys? >> > Make your initial page a WATask which calls your first WAComponent. Thanks. That seemed to do the trick. -Carl _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |