On 26 Feb 2007, at 17:07 , Florian Minjat wrote: > But currently I don't even have the config app. The only thing my > browser is returning is 'Internal Server Error > MessageNotUnderstood: UndefinedObject>>isEmpty'. > I updated from Seaside2.7a1-pmm.157, Scriptaculous-lr.168 and > FileLibrary-mb.18 where everything worked fine. > When you have Seaside 2.7, you should not load FileLibrary. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
> > I updated from Seaside2.7a1-pmm.157, Scriptaculous-lr.168 and
> > FileLibrary-mb.18 where everything worked fine. > > When you have Seaside 2.7, you should not load FileLibrary. Hehe, yes this must be it. FileLibrary has been merged with Seaside 2.7. Cheers, 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 Michel Bany
Michel Bany wrote:
> > On 26 Feb 2007, at 17:07 , Florian Minjat wrote: > >> But currently I don't even have the config app. The only thing my >> browser is returning is 'Internal Server Error MessageNotUnderstood: >> UndefinedObject>>isEmpty'. >> I updated from Seaside2.7a1-pmm.157, Scriptaculous-lr.168 and >> FileLibrary-mb.18 where everything worked fine. >> > > When you have Seaside 2.7, you should not load FileLibrary. This should have been the problem. With a clean installation it works fine. Thanks for the help ! Florian _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Florian Minjat
> >> I tried starting from a blank clean 3.9 image an installed
> >> SeasideInstaller.12. It worked fine. But I couldn't manage to change > >> the url to my application to 'http://localhost:9090/MyApp' by setting > >> #serverPath to ''. > > > > These settings only affect how the resulting page generates absolute > > URLs, it does not and has never affected the lookup. So I don't > > understand your question ... > > Mmm. > I problem is that I need my application to be accessible with an url > like 'http://myaddress/myApp' and not like > 'http://myaddress/seaside/myApp'. Previously I was just doing : > WADispatcher default basePath: ''. > And every seaside application url were shortened as I wanted. > > Now if I try the previous command, I get an error. I tried with the > #serverPath setting of yours, but I understand it is not the right way > to do it. How can I get my small url then ? Aha, now I understand the problem. Evaluate the following code: WADispatcher default setName: '' and everything should work. Thanks to the new implementation of the dispatchers ;-) Cheers, 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
2007/2/26, Lukas Renggli <[hidden email]>:
> > > I updated from Seaside2.7a1-pmm.157, Scriptaculous-lr.168 and > > > FileLibrary-mb.18 where everything worked fine. > > > > When you have Seaside 2.7, you should not load FileLibrary. > > Hehe, yes this must be it. FileLibrary has been merged with Seaside 2.7. Should we delete the FileLibrary versions or move them to an other repository? They have caused problems for at least two people. Philippe > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > 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 |
> Should we delete the FileLibrary versions or move them to an other
> repository? They have caused problems for at least two people. Maybe better delete them, they where a prototype after all that now got included into main stream. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2007/2/26, Lukas Renggli <[hidden email]>:
> > Should we delete the FileLibrary versions or move them to an other > > repository? They have caused problems for at least two people. > > Maybe better delete them, they where a prototype after all that now > got included into main stream. Yeah, make me admin or delete them yourself ;) > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > 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 Philippe Marschall
>> > > Should we delete the FileLibrary versions or move them to an other > repository? They have caused problems for at least two people. > 3 ;) _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Philippe Marschall
> > > Should we delete the FileLibrary versions or move them to an other
> > > repository? They have caused problems for at least two people. > > > > Maybe better delete them, they where a prototype after all that now > > got included into main stream. > > Yeah, make me admin or delete them yourself ;) Well, you can make admin yourself, since you have physical access to the machine, but for now I deleted the versions. Cheers, 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
> -----Mensaje original-----
> De: [hidden email] > [mailto:[hidden email]] En nombre > de Lukas Renggli > Enviado el: Domingo, 25 de Febrero de 2007 12:33 > Para: The Squeak Enterprise Aubergines Server - general discussion. > Asunto: Re: [Seaside] Seaside 2.7 > > > > Even tough its use is very limited, I think it is quite a cool > > > concept. What is missing, I think, is to be able to tell > it go one > > > step forward or backward when developer tells so. I > observed myself > > > to build quite a lot of wizard like applications, but > since WATask > > > does not provide a way (except for the back button) to go > back I had > > > to connect components in different (and ugly) ways. I > think it makes > > > sense to give a bit more power to WATask, right now it doesn't do > > > anything more than what you can already do within a callback. > > > > What about making a reusable component wich renders the sub > component > > you preconfigure on it and let also programatic > configuration of the > > actions for it's buttons wich can be typically the same as > any wizard? > > Yes, this is what I did so far, however it gets incredible > ugly (or even stops to work at all) when you want something > more sophisticated, such as conditional display/configuration > of certain steps and/or multiple display (loops) of the same > steps. This is the use-case where you can't beat a task with > its natural control flow ;-) That's right I know what you mean. Now comes to my mind... what about modeling that conditionals steps in a state-machine and delegating all to it? Double dispatch could be useful to tell what to render. Regards, Sebastian > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > 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 |
> That's right I know what you mean. Now comes to my mind... what about
> modeling that conditionals steps in a state-machine and delegating all to > it? Double dispatch could be useful to tell what to render. Certainly, that is a possibility and that is what all the frameworks without continuations do. The idea of Seaside (and other continuation based frameworks) was to naturally define control flow within a method. I wouldn't want to destroy that elegance. Cheers, 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
Thanks a lot !
It works perfectly well now :). Florian Lukas Renggli wrote: >> >> I tried starting from a blank clean 3.9 image an installed >> >> SeasideInstaller.12. It worked fine. But I couldn't manage to change >> >> the url to my application to 'http://localhost:9090/MyApp' by setting >> >> #serverPath to ''. >> > >> > These settings only affect how the resulting page generates absolute >> > URLs, it does not and has never affected the lookup. So I don't >> > understand your question ... >> >> Mmm. >> I problem is that I need my application to be accessible with an url >> like 'http://myaddress/myApp' and not like >> 'http://myaddress/seaside/myApp'. Previously I was just doing : >> WADispatcher default basePath: ''. >> And every seaside application url were shortened as I wanted. >> >> Now if I try the previous command, I get an error. I tried with the >> #serverPath setting of yours, but I understand it is not the right way >> to do it. How can I get my small url then ? > > Aha, now I understand the problem. Evaluate the following code: > > WADispatcher default setName: '' > > and everything should work. Thanks to the new implementation of the > dispatchers ;-) > > Cheers, > Lukas > Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Avi Bryant-2
Avi Bryant wrote:
> > FWIW, I'd be interested in also: > - Getting rid of WADecoration, it has probably the highest complexity > to utility ratio of anything in the framework I use decorations sparingly but in the cases where I use them I'd be hard pressed to find a replacement. I suppose that, if you remove them, you'll have to come up with another mechanism for delegation and said mechanism might be exploitable for the purposes for which I currently use decorations (binding dynamic variables during callback and rendering, adding visual decorations to components, ip-based session protection and maybe a few others). Anyway, I'd miss them if they were gone. David _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Koji Yokokawa
Hi,
2007/2/25, Koji Yokokawa <[hidden email]>: > I have some minor changes to fix troubles about UTF8 and WideString. > (I don't have tests but I checked in Japanese) > Unfortunately, these patches are only for Squeak. Since Seaside should be easily ported to VW (or even Dolphin?), I think there need to be more indirections. (Especially the patches for WAUrl). But definitely it is the first great step. I hope Seaside can be run correctly in M17N environment. Cheers, -- [:masashi | ^umezawa] _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2007/2/27, Masashi UMEZAWA <[hidden email]>:
> Hi, > > 2007/2/25, Koji Yokokawa <[hidden email]>: > > I have some minor changes to fix troubles about UTF8 and WideString. > > (I don't have tests but I checked in Japanese) > > > > Unfortunately, these patches are only for Squeak. Since Seaside should > be easily ported to VW (or even Dolphin?), I think there need to be > more indirections. (Especially the patches for WAUrl). Not so much. We already send #escapeForHTTP in WAUrl so sending it at a second place won't break anything that is not already broken. It won't do utf-8 encoding in Squeak 3.8 but fixes functionality and breaks done. The sever adapters are platform specific anyway (they are located in 'Seaside-Platform' too) so this is no problem as well. It added the patches in a slightly changed form (there was a bug when copying urls) to Seaside 2.8. One thing to always remember it that some people do not want WideStrings and prefer ByteStrings in utf-8 instead. Cheers Philippe > But definitely it is the first great step. I hope Seaside can be run > correctly in M17N environment. > > Cheers, > -- > [:masashi | ^umezawa] > _______________________________________________ > 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 |
On Tue, 27 Feb 2007 15:36:19 +0100 "Philippe Marschall" <[hidden email]> wrote: > 2007/2/27, Masashi UMEZAWA <[hidden email]>: > > Hi, > > > > 2007/2/25, Koji Yokokawa <[hidden email]>: > > > I have some minor changes to fix troubles about UTF8 and WideString. > > > (I don't have tests but I checked in Japanese) > > > > > > > Unfortunately, these patches are only for Squeak. Since Seaside should > > be easily ported to VW (or even Dolphin?), I think there need to be > > more indirections. (Especially the patches for WAUrl). > > Not so much. We already send #escapeForHTTP in WAUrl so sending it at > a second place won't break anything that is not already broken. It > won't do utf-8 encoding in Squeak 3.8 but fixes functionality and > breaks done. And, that WAUrl patch for Squeak3.8 is a temporary work-around to avoid exception. I think String>>escapedForHTTP should convert the WideString to utf-8 at the sametime, like the implementation in Squak3.9. > The sever adapters are platform specific anyway (they are located in > 'Seaside-Platform' too) so this is no problem as well. > > It added the patches in a slightly changed form (there was a bug when > copying urls) to Seaside 2.8. Thanks. > One thing to always remember it that some people do not want > WideStrings and prefer ByteStrings in utf-8 instead. Well, but some users will post wide-strings easily, they don't care about the developer's intention. Then some application will be crushed. I noticed that Pier is broken by a post in Japanese. Koji -- ! Koji Yokokawa <[hidden email]> http://www.yengawa.com/ ^self new! _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2007/2/28, Koji Yokokawa <[hidden email]>:
> > On Tue, 27 Feb 2007 15:36:19 +0100 > "Philippe Marschall" <[hidden email]> wrote: > > > 2007/2/27, Masashi UMEZAWA <[hidden email]>: > > > Hi, > > > > > > 2007/2/25, Koji Yokokawa <[hidden email]>: > > > > I have some minor changes to fix troubles about UTF8 and WideString. > > > > (I don't have tests but I checked in Japanese) > > > > > > > > > > Unfortunately, these patches are only for Squeak. Since Seaside should > > > be easily ported to VW (or even Dolphin?), I think there need to be > > > more indirections. (Especially the patches for WAUrl). > > > > Not so much. We already send #escapeForHTTP in WAUrl so sending it at > > a second place won't break anything that is not already broken. It > > won't do utf-8 encoding in Squeak 3.8 but fixes functionality and > > breaks done. > > And, that WAUrl patch for Squeak3.8 is a temporary work-around to avoid > exception. I think String>>escapedForHTTP should convert the WideString > to utf-8 at the sametime, like the implementation in Squak3.9. > > > The sever adapters are platform specific anyway (they are located in > > 'Seaside-Platform' too) so this is no problem as well. > > > > It added the patches in a slightly changed form (there was a bug when > > copying urls) to Seaside 2.8. > > Thanks. > > > One thing to always remember it that some people do not want > > WideStrings and prefer ByteStrings in utf-8 instead. > > Well, but some users will post wide-strings easily, they don't care > about the developer's intention. Then some application will be crushed. > I noticed that Pier is broken by a post in Japanese. Then this is a bug in your Pier setup. Pier see below how Pier supports posts in Korean http://www.lukas-renggli.ch/blog/studenckifestwal?command=PRViewCommand&view=PBPostHtmlView This setup uses WAKom and therefore ByteStrings. ByteStrings don't mean you can't support non-latin1 languages. Philippe > Koji > > -- ! > Koji Yokokawa <[hidden email]> > http://www.yengawa.com/ > ^self new! > > _______________________________________________ > 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 |
On Wed, 28 Feb 2007 09:17:01 +0100 "Philippe Marschall" <[hidden email]> wrote: > 2007/2/28, Koji Yokokawa <[hidden email]>: > > > > On Tue, 27 Feb 2007 15:36:19 +0100 > > "Philippe Marschall" <[hidden email]> wrote: > > > > > 2007/2/27, Masashi UMEZAWA <[hidden email]>: > > > > Hi, > > > > > > > > 2007/2/25, Koji Yokokawa <[hidden email]>: > > > > > I have some minor changes to fix troubles about UTF8 and WideString. > > > > > (I don't have tests but I checked in Japanese) > > > > > > > > > > > > > Unfortunately, these patches are only for Squeak. Since Seaside should > > > > be easily ported to VW (or even Dolphin?), I think there need to be > > > > more indirections. (Especially the patches for WAUrl). > > > > > > Not so much. We already send #escapeForHTTP in WAUrl so sending it at > > > a second place won't break anything that is not already broken. It > > > won't do utf-8 encoding in Squeak 3.8 but fixes functionality and > > > breaks done. > > > > And, that WAUrl patch for Squeak3.8 is a temporary work-around to avoid > > exception. I think String>>escapedForHTTP should convert the WideString > > to utf-8 at the sametime, like the implementation in Squak3.9. > > > > > The sever adapters are platform specific anyway (they are located in > > > 'Seaside-Platform' too) so this is no problem as well. > > > > > > It added the patches in a slightly changed form (there was a bug when > > > copying urls) to Seaside 2.8. > > > > Thanks. > > > > > One thing to always remember it that some people do not want > > > WideStrings and prefer ByteStrings in utf-8 instead. > > > > Well, but some users will post wide-strings easily, they don't care > > about the developer's intention. Then some application will be crushed. > > I noticed that Pier is broken by a post in Japanese. > > Then this is a bug in your Pier setup. Pier see below how Pier > supports posts in Korean > http://www.lukas-renggli.ch/blog/studenckifestwal?command=PRViewCommand&view=PBPostHtmlView > > This setup uses WAKom and therefore ByteStrings. ByteStrings don't > mean you can't support non-latin1 languages. Good! Sorry, it's my misunderstanding. Pier is NOT broken by Japanese text too. I agree it's enough to display it in a web-browser. However, it is not the point I'm afraid. I mean the non-latin1 text is broken as a WideString in Squeak. The text cannot be saw and handled crrectly in the Squeak side, not in the web-browsers. So that, you cannot edit, even search, the text from Squeak. And, I think, it will be cause of many bugs. -- ! Koji Yokokawa <[hidden email]> http://www.yengawa.com/ ^self new! _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2007/2/28, Koji Yokokawa <[hidden email]>:
> > On Wed, 28 Feb 2007 09:17:01 +0100 > "Philippe Marschall" <[hidden email]> wrote: > > > 2007/2/28, Koji Yokokawa <[hidden email]>: > > > > > > On Tue, 27 Feb 2007 15:36:19 +0100 > > > "Philippe Marschall" <[hidden email]> wrote: > > > > > > > 2007/2/27, Masashi UMEZAWA <[hidden email]>: > > > > > Hi, > > > > > > > > > > 2007/2/25, Koji Yokokawa <[hidden email]>: > > > > > > I have some minor changes to fix troubles about UTF8 and WideString. > > > > > > (I don't have tests but I checked in Japanese) > > > > > > > > > > > > > > > > Unfortunately, these patches are only for Squeak. Since Seaside should > > > > > be easily ported to VW (or even Dolphin?), I think there need to be > > > > > more indirections. (Especially the patches for WAUrl). > > > > > > > > Not so much. We already send #escapeForHTTP in WAUrl so sending it at > > > > a second place won't break anything that is not already broken. It > > > > won't do utf-8 encoding in Squeak 3.8 but fixes functionality and > > > > breaks done. > > > > > > And, that WAUrl patch for Squeak3.8 is a temporary work-around to avoid > > > exception. I think String>>escapedForHTTP should convert the WideString > > > to utf-8 at the sametime, like the implementation in Squak3.9. > > > > > > > The sever adapters are platform specific anyway (they are located in > > > > 'Seaside-Platform' too) so this is no problem as well. > > > > > > > > It added the patches in a slightly changed form (there was a bug when > > > > copying urls) to Seaside 2.8. > > > > > > Thanks. > > > > > > > One thing to always remember it that some people do not want > > > > WideStrings and prefer ByteStrings in utf-8 instead. > > > > > > Well, but some users will post wide-strings easily, they don't care > > > about the developer's intention. Then some application will be crushed. > > > I noticed that Pier is broken by a post in Japanese. > > > > Then this is a bug in your Pier setup. Pier see below how Pier > > supports posts in Korean > > http://www.lukas-renggli.ch/blog/studenckifestwal?command=PRViewCommand&view=PBPostHtmlView > > > > This setup uses WAKom and therefore ByteStrings. ByteStrings don't > > mean you can't support non-latin1 languages. > > Good! > Sorry, it's my misunderstanding. Pier is NOT broken by Japanese text too. > > I agree it's enough to display it in a web-browser. > However, it is not the point I'm afraid. I mean the non-latin1 text is > broken as a WideString in Squeak. The text cannot be saw and handled > crrectly in the Squeak side, not in the web-browsers. That's true. But Pier is (mostly) a web application. It (in general) doesn't display morphs and stuff so this is less of an issue. Even if it did display morphs it whould probably be a pain to getting all the characters displayed correctly. I can tell you it is a pain to paste non-latin1 (some times even non-ascii) text into Squeak. > So that, you > cannot edit, even search, the text from Squeak. And, I think, it will be > cause of many bugs. Kinda depends what you are doing. Most web applications I have seen just consume strings and ouput them again unchanged. You only have to pay attention when you are creating substrings (the first n characters). Naive text searching might return a few false positives. Sure, if you are building a suffix tree or boyer moore text search and stuff then you really have to pay attention. But if you use a relational database (the main case where it is interesting to just have uft-8 strings), and set the encoding correctly everything works just fine. Philippe > > -- ! > Koji Yokokawa <[hidden email]> > http://www.yengawa.com/ > ^self new! > > _______________________________________________ > 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 |
Free forum by Nabble | Edit this page |