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

Re: [Pharo-project] 1.3 OneCick with Cog VM

by StÃ©phane Ducasse

On Sep 10, 2011, at 9:00 PM, John Toohey wrote: > I saw the screencast where Mariano did something like that. I had just > built the image, when the original VM crash happened, so it wasn't > that much of a deal to rebuild it. > > I would like to see some form of safe-mode boot for Pharo, so that > just the kernel would be loaded. ST images are all about state, and > when production servers go down, it would be nice to be able to start > them up, and rewind the app. For normal apps this is not an issue, but > when forking processes for socket IO or a FFI call, it is possible to > bring it down (or in my case where I think my error handling code > caused an error) , and moving in a backup image is not always enough. I would like to be able to rebuild the kernel at startup. Now I should work on it but I got new responsibilities and they take my time. Stef > > I would like to get involved in such a project, if there was interest for it. > > On Fri, Sep 9, 2011 at 18:41, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> John Toohey wrote: >>> >>> So do I have to rebuild a new image from scratch now? Is there any >>> command line switch that I can use to by pass the loading of my app on >>> start up? >>> >> >> I don't know if it'd be worth it, but if you're talking about a lot of work >> lost, it sounds like you could build a debug VM and bypass the loading code >> from the debugger (like I just had to do). >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/1-3-OneCick-with-Cog-VM-tp3798884p3802970.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > > -- > ~JT >

Sept. 10, 2011

Re: [Pharo-project] 1.3 OneCick with Cog VM

by John Toohey

I saw the screencast where Mariano did something like that. I had just built the image, when the original VM crash happened, so it wasn't that much of a deal to rebuild it. I would like to see some form of safe-mode boot for Pharo, so that just the kernel would be loaded. ST images are all about state, and when production servers go down, it would be nice to be able to start them up, and rewind the app. For normal apps this is not an issue, but when forking processes for socket IO or a FFI call, it is possible to bring it down (or in my case where I think my error handling code caused an error) , and moving in a backup image is not always enough. I would like to get involved in such a project, if there was interest for it. On Fri, Sep 9, 2011 at 18:41, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > John Toohey wrote: >> >> So do I have to rebuild a new image from scratch now? Is there any >> command line switch that I can use to by pass the loading of my app on >> start up? >> > > I don't know if it'd be worth it, but if you're talking about a lot of work > lost, it sounds like you could build a debug VM and bypass the loading code > from the debugger (like I just had to do). > > Sean > > -- > View this message in context: http://forum.world.st/1-3-OneCick-with-Cog-VM-tp3798884p3802970.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- ~JT

Sept. 10, 2011

Re: [Pharo-project] shift of -1@0 when clicking a morph

by Tudor Girba

Just to stress this issue a bit more: The problem is critical for getting Mondrian to work properly with Glamour (be able to get the interaction from the visualization in the surrounding browser), and it is a show stopper for releasing Moose 4.6. Any help would be appreciated. Cheers, Doru On 10 Sep 2011, at 08:40, StÃ©phane Ducasse wrote: > > On Sep 10, 2011, at 2:06 AM, Alexandre Bergel wrote: > >> Hi! >> >> In Pharo 1.3 13287 I am experiencing something very strange. Apparently, when I click a morph the mouseOver: event has a x value reduced by 1. This happens only when I click. Subsequent mouseOver: are fine. This triggers an odd behavior in Mondrian. > > Strange indeed. > >> >> In Pharo 1.4 14112, this strange behavior has disappeared. >> >> I tried to load some more recent packages of Morphic, Graphics, Polymorph... without success (either I get an emergency debugger or the image freezes). >> >> Maybe: http://code.google.com/p/pharo/issues/detail?id=4503 ? But I could not find the Slice. > > No I do not think this is related > > Stef >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Sept. 10, 2011

[Pharo-project] [update 1.4] #14128

by Marcus Denker

14128 ----- Issue 1686: resetTo:1 in newFrom: aCollection http://code.google.com/p/pharo/issues/detail?id=1686 Issue 4781: more poly fixes http://code.google.com/p/pharo/issues/detail?id=4781 -- Marcus Denker -- http://marcusdenker.de

Sept. 10, 2011

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

by Mariano Martinez Peck

WOW. Sean that is super cool. I have to admit I never thought you were gonna be able to di it. This is awesome and I've been there (but never took the time to solve it). Please, do a blog post! On Sat, Sep 10, 2011 at 12:20 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Huge thanks to Igor and Mariano. I recovered the image. Just in case anyone > ever has a similar problem, the solution was: > > 1. Test for selector in CoInterpreter>>commonSend > ... > (messageSelector = #halt) ifFalse: [ "the conditional was added" > self internalFindNewMethod. > self internalExecuteNewMethod ]. > > self fetchNextBytecode. > > 2. Manually edit the condition in gcc3x-cointerp.c: > char* realSelector = GIV(messageSelector) + BaseHeaderSize; > if (strncmp(realSelector, "halt", 4) == 0) > puts("Skipping halt..."); > else { ... > > Although I lost the better part of a day, it's a very powerful feeling to > start building basic VM skills and know that errors that used to be magical > and fatal can now be resolved... > > Cheers, > Sean > > -- > View this message in context: > http://forum.world.st/Oops-I-put-a-halt-in-a-startup-method-tp3800163p38029… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Sept. 10, 2011

[Pharo-project] [COTDC] 84 - FreeTypeCacheLinkedList

by laurent laffont

Today: FreeTypeCacheLinkedList Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

Sept. 10, 2011

Re: [Pharo-project] [COTDC] 83 - MCVersionInspector

by laurent laffont

Thanks again Sean Laurent. On Thu, Sep 8, 2011 at 11:06 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I am a tool that visually represents an MCVersion. > > While I can be opened on anMCVersion, you've probably seen me most often > after saving a package in the Monticello Browser. > > I have buttons to perform common version-related actions - like browsing, > loading, and viewing changes. In my main text area, I display the following > information about my version - name, author, timestamp, UUID, ancestors and > log message. > > -- > View this message in context: > http://forum.world.st/COTDC-83-MCVersionInspector-tp3800071p3800124.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Sept. 10, 2011

Re: [Pharo-project] Immutability and Pharo

by StÃ©phane Ducasse

On Sep 10, 2011, at 9:00 AM, Eliot Miranda wrote: > > > On Fri, Sep 9, 2011 at 8:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > more bits on the object header and we will get it > > the bit already exists, which is how it was implementable in Newspeak. yes of course, but it means that if we use this bit, all the guys doing research and relying on it will not be able to use pharo anymore for their research. And in this case they should either move to another language or stick with an old version. Quite counter productive for us. > Note that JB already provided the code from newspeak. And I would love to have immutability and extra bits for extra experiments. > > Stef > > > On Sep 9, 2011, at 4:58 PM, Torsten Bergmann wrote: > > > ... comments? > > -- > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > > > > > > -- > best, > Eliot >

Sept. 10, 2011

Re: [Pharo-project] Immutability and Pharo

by Eliot Miranda

On Fri, Sep 9, 2011 at 8:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > more bits on the object header and we will get it > the bit already exists, which is how it was implementable in Newspeak. > > Note that JB already provided the code from newspeak. > > Stef > > > On Sep 9, 2011, at 4:58 PM, Torsten Bergmann wrote: > > > ... comments? > > -- > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > > > -- best, Eliot

Sept. 10, 2011

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

by StÃ©phane Ducasse

I'm impressed and I should do the same than you. Jumping into fire. Stef On Sep 10, 2011, at 12:20 AM, Sean P. DeNigris wrote: > Huge thanks to Igor and Mariano. I recovered the image. Just in case anyone > ever has a similar problem, the solution was: > > 1. Test for selector in CoInterpreter>>commonSend > ... > (messageSelector = #halt) ifFalse: [ "the conditional was added" > self internalFindNewMethod. > self internalExecuteNewMethod ]. > > self fetchNextBytecode. > > 2. Manually edit the condition in gcc3x-cointerp.c: > char* realSelector = GIV(messageSelector) + BaseHeaderSize; > if (strncmp(realSelector, "halt", 4) == 0) > puts("Skipping halt..."); > else { ... > > Although I lost the better part of a day, it's a very powerful feeling to > start building basic VM skills and know that errors that used to be magical > and fatal can now be resolved... > > Cheers, > Sean > > -- > View this message in context: http://forum.world.st/Oops-I-put-a-halt-in-a-startup-method-tp3800163p38029… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Sept. 10, 2011