Hi all,
till now ShoreComponents used some special technological properties that helped to solve some general problems of Seaside applications. Unfortunatelly this properties cased that it was not easy to use ShoreComponents with standard Seaside applications. It was possible to use Seaside components in applications based on ShoreComponents but it was almost impossible to use components from ShoreComponents package as supplement of other components. So it was not possible to use it for cooperation with Magritte etc.
The third major version of ShoreComponents makes big step in this area and I hope that it will be better and better.
Main properies of the next release: - there's no base component class. Components are now based on standard WAComponent - components doesn't require parent reference. They can be created with classical "new" constructor - dynamic variables are used for navigation in hierarchy of components (for specification of target component etc.) - static files are now provided by standard FileLibrary
This is the first alpha version so it's far from perfect. The main problem are some form processing issues so some components are not working well. Also nested forms problem is not solved now. Only platform independent part of ShoreComponents is converted now.
I hope that you will find it useful and you will find motivation to improve and extend this set of components and use it in your applications.
download: http://www.squeaksource.com/ShoreComponents/
-- Pavel
This looks like really great news! Thanks for doing it I'm sure it will be very useful and worthwhile.
Ron Teitelbaum
-----Original Message----- From: seaside-bounces@lists.squeakfoundation.org [mailto:seaside- bounces@lists.squeakfoundation.org] On Behalf Of Pavel Krivanek Sent: Sunday, October 29, 2006 1:09 PM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: [Seaside] [ANN] ShoreComponents 3 - back on Seaside
Hi all,
till now ShoreComponents used some special technological properties that helped to solve some general problems of Seaside applications. Unfortunatelly this properties cased that it was not easy to use ShoreComponents with standard Seaside applications. It was possible to use Seaside components in applications based on ShoreComponents but it was almost impossible to use components from ShoreComponents package as supplement of other components. So it was not possible to use it for cooperation with Magritte etc.
The third major version of ShoreComponents makes big step in this area and I hope that it will be better and better.
Main properies of the next release:
- there's no base component class. Components are now based on
standard WAComponent
- components doesn't require parent reference. They can be created
with classical "new" constructor
- dynamic variables are used for navigation in hierarchy of components
(for specification of target component etc.)
- static files are now provided by standard FileLibrary
This is the first alpha version so it's far from perfect. The main problem are some form processing issues so some components are not working well. Also nested forms problem is not solved now. Only platform independent part of ShoreComponents is converted now.
I hope that you will find it useful and you will find motivation to improve and extend this set of components and use it in your applications.
download: http://www.squeaksource.com/ShoreComponents/
-- Pavel _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Am I the only one who sometimes see this error "The page cannot be displayed" when using my Seaside application? Refreshing the page usually solves the problem. Would this be a problem with Seaside, or maybe the VW web server?
I am using the latest version of VW and Seaside and IE6.
-Carl Gundel, author of Liberty BASIC http://www.libertybasic.com
----- Original Message ----- From: "Ron Teitelbaum" Ron@USMedRec.com To: "'The Squeak Enterprise Aubergines Server - general discussion.'" seaside@lists.squeakfoundation.org Sent: Sunday, October 29, 2006 9:17 PM Subject: RE: [Seaside] [ANN] ShoreComponents 3 - back on Seaside
This looks like really great news! Thanks for doing it I'm sure it will
be
very useful and worthwhile.
Ron Teitelbaum
-----Original Message----- From: seaside-bounces@lists.squeakfoundation.org [mailto:seaside- bounces@lists.squeakfoundation.org] On Behalf Of Pavel Krivanek Sent: Sunday, October 29, 2006 1:09 PM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: [Seaside] [ANN] ShoreComponents 3 - back on Seaside
Hi all,
till now ShoreComponents used some special technological properties that helped to solve some general problems of Seaside applications. Unfortunatelly this properties cased that it was not easy to use ShoreComponents with standard Seaside applications. It was possible to use Seaside components in applications based on ShoreComponents but it was almost impossible to use components from ShoreComponents package as supplement of other components. So it was not possible to use it for cooperation with Magritte etc.
The third major version of ShoreComponents makes big step in this area and I hope that it will be better and better.
Main properies of the next release:
- there's no base component class. Components are now based on
standard WAComponent
- components doesn't require parent reference. They can be created
with classical "new" constructor
- dynamic variables are used for navigation in hierarchy of components
(for specification of target component etc.)
- static files are now provided by standard FileLibrary
This is the first alpha version so it's far from perfect. The main problem are some form processing issues so some components are not working well. Also nested forms problem is not solved now. Only platform independent part of ShoreComponents is converted now.
I hope that you will find it useful and you will find motivation to improve and extend this set of components and use it in your applications.
download: http://www.squeaksource.com/ShoreComponents/
-- Pavel _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Hi Carl,
Am I the only one who sometimes see this error "The page cannot be displayed" when using my Seaside application? Refreshing the page usually solves the problem. Would this be a problem with Seaside, or maybe the VW web server? I am using the latest version of VW and Seaside and IE6.
I've seen that too and I have no explanation.
In most cases you can get rid of this symptom by unchecking "Show friendly HTTP error messages" in the Advanced tab of the Internet Options.
HTH, Michel.
From: "Michel Bany" michel.bany@gmail.com
Hi Carl,
Am I the only one who sometimes see this error "The page cannot be displayed" when using my Seaside application? Refreshing the page usually solves the problem. Would this be a problem with Seaside, or maybe the VW web server? I am using the latest version of VW and Seaside and IE6.
I've seen that too and I have no explanation.
In most cases you can get rid of this symptom by unchecking "Show friendly HTTP error messages" in the Advanced tab of the Internet Options.
Hi Michel. Doesn't solve the problem here. If this were happening on a less popular browser it might not matter much.
Are you running just the VW web server, or do you also have Apache or something else in front of it?
-Carl Gundel, author of Liberty BASIC http://www.libertybasic.com
On 30 Oct 2006, at 13:53 , Carl Gundel wrote:
From: "Michel Bany" michel.bany@gmail.com
Hi Carl,
Am I the only one who sometimes see this error "The page cannot be displayed" when using my Seaside application? Refreshing the page usually solves the problem. Would this be a problem with Seaside, or maybe the VW web server? I am using the latest version of VW and Seaside and IE6.
I've seen that too and I have no explanation.
In most cases you can get rid of this symptom by unchecking "Show friendly HTTP error messages" in the Advanced tab of the Internet Options.
Hi Michel. Doesn't solve the problem here. If this were happening on a less popular browser it might not matter much.
Are you running just the VW web server, or do you also have Apache or something else in front of it?
Carl, I'm not running anything, I'm only doing the VW port. However I have had customers with the same problem and they could fix it with the trick. As I said, I have no explanation. I would suggest that you use an HTTP sniffer like HTTPLook that would help you spot what makes the page undisplayable by IE. Let me know about your findings, I'm interested. Cheers, Michel.
Hi Michel. Doesn't solve the problem here. If this were happening on a less popular browser it might not matter much.
Are you running just the VW web server, or do you also have Apache or something else in front of it?
Carl, I'm not running anything, I'm only doing the VW port. However I have had customers with the same problem and they could fix it with the trick. As I said, I have no explanation. I would suggest that you use an HTTP sniffer like HTTPLook that would help you spot what makes the page undisplayable by IE. Let me know about your findings, I'm interested.
Thanks. I'll let you know if I discover anything of course. Probably I should post about this problem on the VW list in case it is a known issue with their web server. Perhaps I will try running the server from behind Apache to see if that makes a difference.
This happens reliably on IE6. I don't see this problem at all when using Safari on my Mac or Mozilla on my Linux box, but of course I still need to fix this.
-Carl Gundel, author of Liberty BASIC http://www.libertybasic.com
We've had this problem as well, especially under simulated load (0-byte responses mostly), which I solved by switching to Swazoo (v1.0) from Webtoolkit. I've been meaning to come up with a decent test case for Michel and Alan (he's expressed interest in trying to figure it out), but haven't really had a chance to commit any significant amount of time to it. Still planning on it though...
Hope this helps,
-Boris
I'm very glad to hear that people are paying some attention to this issue. Thanks!
From: "Boris Popov" boris@deepcovelabs.com
We've had this problem as well, especially under simulated load (0-byte responses mostly), which I solved by switching to Swazoo (v1.0) from Webtoolkit. I've been meaning to come up with a decent test case for Michel and Alan (he's expressed interest in trying to figure it out), but haven't really had a chance to commit any significant amount of time to it. Still planning on it though...
Hope this helps,
Of course if you have any hints as to how one could get this to happen reliably in the base installation please share. So far I've had trouble finding a 100% scenario.
Cheers,
-Boris
I'm very glad to hear that people are paying some attention to this issue. Thanks!
Carl,
I believe I found the reason for this issue.
It looks as if MSIE does not like an HTTP header with no space after the colon while WebToolkit does not output any. I see this as a bug in MSIE since RFC 2822 specifies that spaces after the colon are optional (page 46). The same bug exists also in IE7.
I was not curious enough to determine which header exactly was affected, so I created two patches to WebToolkit to make sure that a space is inserted after the colon in all headers.
The patches are available on the public store as part of package WebToolkit/Patches 2.6b1.118.1. You can either load the patches from the package, load the package itself into your image or rebuild a new image by loading SeasideForWebToolkit.
I hope these patches will fix the issue for you.
Michel.
Michel,
Just a couple of notes that may or may not be relevant. First, I'd actually discovered the same issue you did, but in a different context and the changes have been intergrated into the most recent 7.5 build (AR 51302).
<quote vwnc> Attached are two changes to add space after $: in the HTTP headers. I realize that HTTP (1.0/1.1) RFCs allow for no separator between header name and value, but I recently came across two tools that fail to parse headers that do not include the space, specifically Webserver Stress Tool 7 from Paessler and Charles Web Debugging Tool. For instance the stress tool would re-send the cookie without the first character, resulting in an endless loop when wave would keep on creating new sessions every time since cookie name didn't match </quote vwnc>
Unfortunately, I don't think this solved my original problem with IE, which was intermitted failures (easy to simulate by clicking on links really fast, it would eventually just show you an empty page), but you never know.
Hope this helps,
-Boris
I'm very glad to hear that people are paying some attention to this issue. Thanks!
Carl,
I believe I found the reason for this issue.
It looks as if MSIE does not like an HTTP header with no space after the colon while WebToolkit does not output any. I see this as a bug in MSIE since RFC 2822 specifies that spaces after the colon are optional (page 46). The same bug exists also in IE7.
I was not curious enough to determine which header exactly was affected, so I created two patches to WebToolkit to make sure that a space is inserted after the colon in all headers.
The patches are available on the public store as part of package WebToolkit/Patches 2.6b1.118.1. You can either load the patches from the package, load the package itself into your image or rebuild a new image by loading SeasideForWebToolkit.
I hope these patches will fix the issue for you.
I do appreciate it. Thanks.
It has taken me weeks to get around to trying the patches. After loading them from the public Store repository they do not seem to do the trick.
I wonder if I'm doing something wrong.
The following method exists in my image for class MessageHeaders:
sendOver: aStream
self do: [ :header | aStream nextPutAll: header key; nextPutAll: ': '. "A space is needed by IE for some headers" aStream nextPutAll: (self headerEncode: header). aStream crlf. ].
So the fix would appear to be there alright. Any thoughts?
-Carl Gundel, author of Liberty BASIC http://www.libertybasic.com
So the fix would appear to be there alright. Any thoughts?
The second fix is in Smalltalk.VisualWave.Response>>writeCookies:
Crossing fingers,
Yeah, this is in there too. :-/
writeCookies: aStream self cookies isNil ifTrue: [^self]. self cookies do: [:cookie | cookie isNil ifFalse: [aStream nextPutAll: 'Set-Cookie: ' , "A space needed by IE sometimes" "(self headerEncode:" cookie valueString")"; crlf]].
-Carl
Carl,
Another question. Are you using SeasideShortPath ? There is an ugly bug in this parcel. I have a fix for that bug for which I am awaiting feedback. If you are using this parcel you may also want to try my fix out. Let me know. Michel.
On 05 Jan 2007, at 18:32 , Carl Gundel wrote:
So the fix would appear to be there alright. Any thoughts?
The second fix is in Smalltalk.VisualWave.Response>>writeCookies:
Crossing fingers,
Yeah, this is in there too. :-/
writeCookies: aStream self cookies isNil ifTrue: [^self]. self cookies do: [:cookie | cookie isNil ifFalse: [aStream nextPutAll: 'Set-Cookie: ' , "A space needed by IE sometimes" "(self headerEncode:" cookie valueString")"; crlf]].
-Carl
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Another question. Are you using SeasideShortPath ? There is an ugly bug in this parcel. I have a fix for that bug for which I am awaiting feedback. If you are using this parcel you may also want to try my fix out. Let me know.
No, I'm not using that.
-Carl Gundel, author of Liberty BASIC http://www.libertybasic.com
Hi Carl,
Still trying to understand this issue. (I'm assuming this is still an issue for you).
Are you using session cookies ? If you are you may be interested by the very latest version of Seaside on the public store. It contains a fix that solves an issue where the symptom could be similar to yours.
Also, many thanks for your interesting input during James podcast.
Michel.
Hi Michel,
It is not an issue for me at this time because running Seaside behind Apache seems to have solved it for me.
I am not using cookies.
I'll certainly be happy to try the latest version of Seaside as soon as I can, thanks!
I'm glad you liked the podcast. What specific input was helpful?
-Carl http://www.libertybasic.com
----- Original Message ----- From: "Bany, Michel" mbany@cincom.com
Hi Carl,
Still trying to understand this issue. (I'm assuming this is still an issue for you).
Are you using session cookies ? If you are you may be interested by the very latest version of Seaside on the public store. It contains a fix that solves an issue where the symptom could be similar to yours.
Also, many thanks for your interesting input during James podcast.
Michel. _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
I'm glad you liked the podcast. What specific input was helpful?
I liked the way you explained that you were able to program for the web without being a web programer. Also I found interesting the review of all the opportunities that you seem to have for offering programming services to such a large market. Very exciting also, the possibility to generate Seaside UI to Basic applications. Frankly, I wish you all the best. Michel.
After some months of seeing this problem very infrequently, I discover that the problem resurfaces when I try to connect to my application using IE7 version 7.0.6000.16512 running under Vista Home Edition. When I connect using a different version of IE7 from a different machine running XP I do not have the problem at all.
Very strange, and it only seems to happen consistently when using WAImageButtonTag.
-Carl
----- Original Message ----- From: "Bany, Michel" mbany@cincom.com To: "The Squeak Enterprise Aubergines Server - general discussion." seaside@lists.squeakfoundation.org Sent: Tuesday, February 13, 2007 11:51 AM Subject: RE: [Seaside] [VW7.4.1] The page cannot be displayed
Hi Carl,
Still trying to understand this issue. (I'm assuming this is still an issue for you). s. Are you using session cookies ? If you are you may be interested by the very latest version of Seaside on the public store. It contains a fix that solves an issue where the symptom could be similar to yours.
Also, many thanks for your interesting input during James podcast.
Michel. _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
What I mean by using WAImageButtonTag is not just that one or more of these appear on the page, but that I click on one. I notice that the URL for these isn't the same as a URL for regular anchors (which work fine).
URL for an image button:
http://localhost:8008/seaside/go/app?_s=fhkaAShwsut&_k=zskgdjgsd
URL for an anchor is similar, but ends in & and an integer value:
http://localhost:8008/seaside/go/app?_s=fhkaAShwsut&_k=kuhrgcsn&123
Not sure if this is related to the problem, but there it is.
-Carl Gundel http://www.runbasic.com
----- Original Message ----- From: "Carl Gundel" carlg@libertybasic.com To: "The Squeak Enterprise Aubergines Server - general discussion." seaside@lists.squeakfoundation.org Sent: Thursday, August 16, 2007 8:30 PM Subject: Re: [Seaside] [VW7.4.1] The page cannot be displayed
After some months of seeing this problem very infrequently, I discover that the problem resurfaces when I try to connect to my application using IE7 version 7.0.6000.16512 running under Vista Home Edition. When I connect using a different version of IE7 from a different machine running XP I do not have the problem at all.
Very strange, and it only seems to happen consistently when using WAImageButtonTag.
-Carl
----- Original Message ----- From: "Bany, Michel" mbany@cincom.com To: "The Squeak Enterprise Aubergines Server - general discussion." seaside@lists.squeakfoundation.org Sent: Tuesday, February 13, 2007 11:51 AM Subject: RE: [Seaside] [VW7.4.1] The page cannot be displayed
Hi Carl,
Still trying to understand this issue. (I'm assuming this is still an issue for you). s. Are you using session cookies ? If you are you may be interested by the very latest version of Seaside on the public store. It contains a fix that solves an issue where the symptom could be similar to yours.
Also, many thanks for your interesting input during James podcast.
Michel. _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Hi, did you test this against IE 6, Safari, and/or Firefox? If so, is the same thing happening? -Conrad
On 8/16/07, Carl Gundel carlg@libertybasic.com wrote:
What I mean by using WAImageButtonTag is not just that one or more of these appear on the page, but that I click on one. I notice that the URL for these isn't the same as a URL for regular anchors (which work fine).
URL for an image button:
http://localhost:8008/seaside/go/app?_s=fhkaAShwsut&_k=zskgdjgsd
URL for an anchor is similar, but ends in & and an integer value:
http://localhost:8008/seaside/go/app?_s=fhkaAShwsut&_k=kuhrgcsn&123
Not sure if this is related to the problem, but there it is.
-Carl Gundel http://www.runbasic.com
----- Original Message ----- From: "Carl Gundel" carlg@libertybasic.com To: "The Squeak Enterprise Aubergines Server - general discussion." seaside@lists.squeakfoundation.org
Sent: Thursday, August 16, 2007 8:30 PM Subject: Re: [Seaside] [VW7.4.1] The page cannot be displayed
After some months of seeing this problem very infrequently, I discover that the problem resurfaces when I try to connect to my application
using
IE7 version 7.0.6000.16512 running under Vista Home Edition. When I connect using a different version of IE7 from a different machine
running
XP I do not have the problem at all.
Very strange, and it only seems to happen consistently when using WAImageButtonTag.
-Carl
----- Original Message ----- From: "Bany, Michel" mbany@cincom.com To: "The Squeak Enterprise Aubergines Server - general discussion." seaside@lists.squeakfoundation.org Sent: Tuesday, February 13, 2007 11:51 AM Subject: RE: [Seaside] [VW7.4.1] The page cannot be displayed
Hi Carl,
Still trying to understand this issue. (I'm assuming this is still an issue for you). s. Are you using session cookies ? If you are you may be interested by the very latest version of Seaside on the public store. It contains a fix that solves an issue where the symptom could be similar to yours.
Also, many thanks for your interesting input during James podcast.
Michel. _______________________________________________ Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Yup, had the same unexplained behavior occurring, but unhappy to admit that I didn't have time to submit a reproducible case to Michel and Cincom. Instead I moved to running Seaside side of things to Swazoo and things have been working smoothly ever since.
Cheers!
-Boris
seaside@lists.squeakfoundation.org
-
Bany, Michel -
Boris Popov -
Carl Gundel -
Conrad Taylor -
Michel Bany -
Pavel Krivanek -
Ron Teitelbaum