September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's

by StÃ©phane Ducasse

:) And this is already fixed and integrated :) Thanks you all. Stef On Sep 9, 2011, at 3:22 PM, Tudor Girba wrote: > Henrik provided a better answer than mine: > > On 9 Sep 2011, at 14:44, Henrik Sperre Johansen wrote: > >> Which is why it was changed, after discussion with Lukas. >> It only forks UnhandledErrors now, before delivering the remaining. >> As long as there is no abnormal termination, it will work just as before. >> If any subscribers would abnormally terminate though, the ifCurtailed: kicks in, and (was supposed to) ensure delivers to remaining subscribers. >> >> If something in Seaside relies on such behaviour (like terminating current process in order for subsequent subscribers to not receive the announcement) that will be broken. >> I don't think messing with announcement delivery should be considered a good control flow mechanism though. >> >> What Esteban encountered as an error on some VM's was a pure bug I made in the ifCurtailed: block (by using after: instead of copyAfter:), and had nothing to do with forking. >> Why some VM's considered the delivery abnormally terminated, while others didn't, I have no idea though... >> (The error he got only happens when the ifCurtailed block is invoked). >> >> Cheers, >> Henry > > Cheers, > Doru > > > On 9 Sep 2011, at 15:20, Sebastian Sastre wrote: > >> Isn't the plain events mechanism forkless and essential to the core of the system already? >> >> if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same >> >> >> >> On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote: >> >>> Igor and Stef can provide more details. >>> >>> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. >>> >>> It would be great if Seaside would work with these, and now depend on another framework. >>> >>> Cheers, >>> Doru >>> >>> >>> On 9 Sep 2011, at 06:38, Philippe Marschall wrote: >>> >>>> 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> Hi, >>>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >>>>> (yes, it can be MY problem too... but I don't think so... ;) >>>>> >>>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... >>>> >>>> The announcements in the latest Pharo 1.3 don't work with Seaside >>>> anymore. For some reason they fork them instead of running them in an >>>> exception handler. >>>> >>>> Cheers >>>> Philippe >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> -- >>> www.tudorgirba.com >>> >>> "Yesterday is a fact. >>> Tomorrow is a possibility. >>> Today is a challenge." >>> >>> >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> sebastian >> >> o/ >> >> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > >

Sept. 9, 2011

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's

by Tudor Girba

Henrik provided a better answer than mine: On 9 Sep 2011, at 14:44, Henrik Sperre Johansen wrote: > Which is why it was changed, after discussion with Lukas. > It only forks UnhandledErrors now, before delivering the remaining. > As long as there is no abnormal termination, it will work just as before. > If any subscribers would abnormally terminate though, the ifCurtailed: kicks in, and (was supposed to) ensure delivers to remaining subscribers. > > If something in Seaside relies on such behaviour (like terminating current process in order for subsequent subscribers to not receive the announcement) that will be broken. > I don't think messing with announcement delivery should be considered a good control flow mechanism though. > > What Esteban encountered as an error on some VM's was a pure bug I made in the ifCurtailed: block (by using after: instead of copyAfter:), and had nothing to do with forking. > Why some VM's considered the delivery abnormally terminated, while others didn't, I have no idea though... > (The error he got only happens when the ifCurtailed block is invoked). > > Cheers, > Henry Cheers, Doru On 9 Sep 2011, at 15:20, Sebastian Sastre wrote: > Isn't the plain events mechanism forkless and essential to the core of the system already? > > if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same > > > > On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote: > >> Igor and Stef can provide more details. >> >> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. >> >> It would be great if Seaside would work with these, and now depend on another framework. >> >> Cheers, >> Doru >> >> >> On 9 Sep 2011, at 06:38, Philippe Marschall wrote: >> >>> 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>> Hi, >>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >>>> (yes, it can be MY problem too... but I don't think so... ;) >>>> >>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... >>> >>> The announcements in the latest Pharo 1.3 don't work with Seaside >>> anymore. For some reason they fork them instead of running them in an >>> exception handler. >>> >>> Cheers >>> Philippe >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> -- >> www.tudorgirba.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > sebastian > > o/ > > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Sept. 9, 2011

Re: [Pharo-project] [Seaside] Announcements/Seaside continuations collision in newer cog vm's

by Tudor Girba

Igor and Stef can provide more details. The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work. It would be great if Seaside would work with these, and now depend on another framework. Cheers, Doru On 9 Sep 2011, at 06:38, Philippe Marschall wrote: > 2011/9/8 Esteban Lorenzano <estebanlm(a)gmail.com>: >> Hi, >> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem) >> (yes, it can be MY problem too... but I don't think so... ;) >> >> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)... > > The announcements in the latest Pharo 1.3 don't work with Seaside > anymore. For some reason they fork them instead of running them in an > exception handler. > > Cheers > Philippe > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

Sept. 9, 2011

[Pharo-project] [update 1.3] #13304

by Marcus Denker

13304 ----- Issue 4778: Merge Browser is broken http://code.google.com/p/pharo/issues/detail?id=4778 -- Marcus Denker -- http://marcusdenker.de

Sept. 9, 2011

Re: [Pharo-project] Help

by Lorenzo Schiavina

Thanks Lorenzo ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, September 08, 2011 10:31 PM Subject: Re: [Pharo-project] Help Lorenzo you should ask on the seaside mailing-list Stef On Sep 8, 2011, at 5:58 PM, Lorenzo Schiavina wrote: > Hi, > > I am trying to insert into a JQTab a JQCheckBox to obtain the same format > as the one you can see in JQCheckBox, but I am not able to set CSS in > JQTab to get the same format. > Can anybody help me? > > Grazie > > Lorenzo

Sept. 9, 2011

Re: [Pharo-project] Find & Replace analysis

by StÃ©phane Ducasse

have a look at the basicWidgets chapter and it would be nice to have How to create a combox radio button button tabbed .... Stef On Sep 9, 2011, at 9:40 AM, HwaJong Oh wrote: > Stef, > > I've downloaded TeX files from GitHub and build PDF from tex PBE2.tex. > > what now? > > HwaJong Oh > > -- > View this message in context: http://forum.world.st/Find-Replace-analysis-tp3797664p3801024.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Sept. 9, 2011

Re: [Pharo-project] [Vm-beginners] Fwd: Oops - I put a halt in a startup method

by Mariano Martinez Peck

Sean: it may be difficult/impossible. But....you may want to try invoking the function say printOop() from the XCode console. If you read my post: http://marianopeck.wordpress.com/2011/04/23/how-to-debug-the-vm/ Then instead of doing "(gdb) call printAllStacks()" you can try something like "(gdb) call printOop(526237628)" and that will print something like "an XXX class". Of course, you need to replace 526237628 with the real OOP of your receiver object. Good luck! On Fri, Sep 9, 2011 at 5:35 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > From > http://forum.world.st/Oops-I-put-a-halt-in-a-startup-method-td3800163.html: > My image appears for an instant and then crashes. Is there any way to > recover from this? > > I made some progress, but I'm not sure I'm on the right track... > I built a debug VM and found primitivePerform, which is apparently called > by the following: > FeaturesDB perform: #startUp: with: resuming > > How will I know which call to skip/break on? Maybe there is there a way, > from the VM side, to get the receiver class name as a string? If I knew > that > the receiver was FeaturesDB, that would be the one... > > And then once I have the right call, can I just skip over it? > > Sean > > > -- > View this message in context: > http://forum.world.st/Fwd-Oops-I-put-a-halt-in-a-startup-method-tp3800729p3… > Sent from the Smalltalk VM - Beginners mailing list archive at Nabble.com. > _______________________________________________ > VM-beginners mailing list > VM-beginners(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/vm-beginners > -- Mariano http://marianopeck.wordpress.com

Sept. 9, 2011

Re: [Pharo-project] Pharo and SSL

by Luc Fabresse

Hi LÃ¡szlÃ³, you should have a look at Zodiac. http://www.squeaksource.com/Zodiac and search for it in mailing list archive because I think that Sven sent some explanations. Cheers, #Luc 2011/9/8 Laszlo Zsolt Kiss <lzskiss(a)dublin.ie> > Hello. > I'm developing an application, and I need SSL support from Pharo. > My dream I can access the Pharo app from a https url. > Can I do this with just the pure Pharo image? > (Yes I know some plugin needed.) > But I dont want to use the Apache or other web server > > Thx. > Byte > LÃ¡szlÃ³ Zsolt > >

Sept. 9, 2011

Re: [Pharo-project] Find & Replace analysis

by HwaJong Oh

Stef, I've downloaded TeX files from GitHub and build PDF from tex PBE2.tex. what now? HwaJong Oh -- View this message in context: http://forum.world.st/Find-Replace-analysis-tp3797664p3801024.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 9, 2011

[Pharo-project] Hudson build is back to stable : Pharo 1.3 #259

by marcus.denker＠inria.fr

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/259/>

Sept. 9, 2011