April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Understanding Athens

by Sean P. DeNigris

Ben Coman wrote > An idea for more general recovery options.... > Using the Pharo command-line processing, have some "recovery" commands > that execute and quit before any UI processing is started. For example... > * list/close open windows > * list/close running processes > * list/revert recent method changes This sounds really cool. I think it would have to be done at the vm level though. IIRC by the time Cami's stuff is run, the UI has already come up... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4682292.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 18, 2013

Re: [Pharo-project] SS lost project description edits done in december 2012

by Igor Stasenko

On 18 April 2013 12:37, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hi! > > I moved a lot of my projects to StHub back in december, and then I edited > the Project descriptions on SS to show that. But these changes have been > lost I now realize? > > Just put it back on Phriak: > > http://www.squeaksource.com/Phriak.html > > Any idea on when/how that happened? > when SS crashing, it "forgets" all metainformation for your project: - description - members etc.. this is one of the reasons why i migrated my active projects to sthub, because i get tired adding members over and over again :) > regards, GÃ¶ran > -- Best regards, Igor Stasenko.

April 18, 2013

Re: [Pharo-project] Understanding Athens

by Igor Stasenko

On 18 April 2013 12:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 18, 2013, at 12:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 18 April 2013 11:52, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >>> On Apr 18, 2013, at 11:24 AM, kilon wrote: >>> >>>> Ok resumed learning of Athens, did look through and experimented with the >>>> steps of the tutorial , I think I understand the basics now. >>>> >>>> Started from a fresh image reinstalled everything and no longer save my >>>> image with Athens Tutorial open so there is no segfault.But the error >>>> remains. >>>> >>>> LogicalFont>>glyphRenderOn >>>> >>>> glyphRendererOn: anAthensBalloonSurface >>>> ^ self realFont glyphRendererOn: anAthensBalloonSurface >>>> >>>> full stack can be found here -> http:// http://pastebin.com/C8itjM2a >>>> <http:// http://pastebin.com/C8itjM2a> >>>> >>>> freetype is enabled in settings , my ears are open for suggestions :) >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4682265.html >>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>> >>> >>> Well, the message is sent to a StrikeFont (the legacy bitmap font, sorta hard to provide a vector-based renderer for), so I guess somewhere, you need to ensure he font used by AthensViewMorph is a LogicalFont whose realFont is an actual TrueTypeFont. >>> >> >> Yes. Athens using freetype fonts. >> LogicalFont-s work in a way that if it can find a corresponding >> freetype font, it will use it, >> otherwise it will fallback to one which comes with image (strike font). >> >> If you want to avoid pitfalls with LogicalFont logic, use direct >> FreeTypeFont instances >> (but don't ask me where how to obtain them ;) ). >> > > We should really clean up Fontsâ¦ > yeah, one of the idea is to put 300kb truetype font into image and say goodbye to strike fonts which take like 1.5Mb > Marcus -- Best regards, Igor Stasenko.

April 18, 2013

Re: [Pharo-project] How to get the AST Node for a Context

by Marcus Denker

On Apr 18, 2013, at 12:54 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > +1, the comments helps to understand, > but this kind of stateful behavior sucks in the first place > > It does, but one step at a time. Marcus

April 18, 2013

Re: [Pharo-project] How to get the AST Node for a Context

by Nicolas Cellier

+1, the comments helps to understand, but this kind of stateful behavior sucks in the first place 2013/4/18 stephane ducasse <stephane.ducasse(a)free.fr> > I should say that I LOVVVVVVVEEEEE the comments in the method. > Yes Yes Yes. > > Stef > > > > > Yes, just the AST with Semantic Analysis information (Scope and Semantic > Variables), plus > > bytecodelevel IR that provides the bridge to the low-level pc (bytecode > mapping) dataâ¦ > > > > e.g. to get the highlight in the debugger, this is now just this in > DebuggerMethodMapOpal: > > > > > > rangeForPC: aPC contextIsActiveContext: contextIsActive > > "return the debug highlight for aPC" > > | pc | > > > > "When on the top of the stack the pc is pointing to right > instruction, but deeper in the stack > > the pc was already advanced one bytecode, so we need to go back > this one bytecode, which > > can consist of multiple bytes. But on IR, we record the *last* > bytecode offset as the offset of the > > IR instruction, which means we can just go back one" > > > > pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. > > ^(methodNode ir instructionForPC: pc) sourceNode > debugHighlightRange > > > > > > > > more helper methods will simplify this even more, e.g. we should have a > method > > on RBMethodNode like #nodeForPC: > > > > > > rangeForPC: aPC contextIsActiveContext: contextIsActive > > "return the debug highlight for aPC" > > | pc | > > > > "When on the top of the stack the pc is pointing to right > instruction, but deeper in the stack > > the pc was already advanced one bytecode, so we need to go back > this one bytecode, which > > can consist of multiple bytes. But on IR, we record the *last* > bytecode offset as the offset of the > > IR instruction, which means we can just go back one" > > > > pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. > > ^(methodNode nodeForPC: pc) debugHighlightRange > > > > > > And this method one then can just implement on MethodContext itself. > > (Caching is handled by ASTCache). > > > > Marcus > > > > > > > > >

April 18, 2013

Re: [Pharo-project] Understanding Athens

by Marcus Denker

On Apr 18, 2013, at 12:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 18 April 2013 11:52, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >> On Apr 18, 2013, at 11:24 AM, kilon wrote: >> >>> Ok resumed learning of Athens, did look through and experimented with the >>> steps of the tutorial , I think I understand the basics now. >>> >>> Started from a fresh image reinstalled everything and no longer save my >>> image with Athens Tutorial open so there is no segfault.But the error >>> remains. >>> >>> LogicalFont>>glyphRenderOn >>> >>> glyphRendererOn: anAthensBalloonSurface >>> ^ self realFont glyphRendererOn: anAthensBalloonSurface >>> >>> full stack can be found here -> http:// http://pastebin.com/C8itjM2a >>> <http:// http://pastebin.com/C8itjM2a> >>> >>> freetype is enabled in settings , my ears are open for suggestions :) >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4682265.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> Well, the message is sent to a StrikeFont (the legacy bitmap font, sorta hard to provide a vector-based renderer for), so I guess somewhere, you need to ensure he font used by AthensViewMorph is a LogicalFont whose realFont is an actual TrueTypeFont. >> > > Yes. Athens using freetype fonts. > LogicalFont-s work in a way that if it can find a corresponding > freetype font, it will use it, > otherwise it will fallback to one which comes with image (strike font). > > If you want to avoid pitfalls with LogicalFont logic, use direct > FreeTypeFont instances > (but don't ask me where how to obtain them ;) ). > We should really clean up Fontsâ¦ Marcus

April 18, 2013

[Pharo-project] SS lost project description edits done in december 2012

by GÃ¶ran Krampe

Hi! I moved a lot of my projects to StHub back in december, and then I edited the Project descriptions on SS to show that. But these changes have been lost I now realize? Just put it back on Phriak: http://www.squeaksource.com/Phriak.html Any idea on when/how that happened? regards, GÃ¶ran

April 18, 2013

Re: [Pharo-project] How to get the AST Node for a Context

by Igor Stasenko

... and people asking , why it has huge impact on our future :) that's why. On 17 April 2013 23:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 17, 2013, at 10:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> >> On Apr 17, 2013, at 10:29 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> I really really like this :) >>> >>> very simple yet powerful! >> >> Yes this will massively simplify the debugger :) >> So we will be able to get a debugger really working without needing an magician to fix >> its bugs. > > Yes, just the AST with Semantic Analysis information (Scope and Semantic Variables), plus > bytecodelevel IR that provides the bridge to the low-level pc (bytecode mapping) dataâ¦ > > e.g. to get the highlight in the debugger, this is now just this in DebuggerMethodMapOpal: > > > rangeForPC: aPC contextIsActiveContext: contextIsActive > "return the debug highlight for aPC" > | pc | > > "When on the top of the stack the pc is pointing to right instruction, but deeper in the stack > the pc was already advanced one bytecode, so we need to go back this one bytecode, which > can consist of multiple bytes. But on IR, we record the *last* bytecode offset as the offset of the > IR instruction, which means we can just go back one" > > pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. > ^(methodNode ir instructionForPC: pc) sourceNode debugHighlightRange > > > > more helper methods will simplify this even more, e.g. we should have a method > on RBMethodNode like #nodeForPC: > > > rangeForPC: aPC contextIsActiveContext: contextIsActive > "return the debug highlight for aPC" > | pc | > > "When on the top of the stack the pc is pointing to right instruction, but deeper in the stack > the pc was already advanced one bytecode, so we need to go back this one bytecode, which > can consist of multiple bytes. But on IR, we record the *last* bytecode offset as the offset of the > IR instruction, which means we can just go back one" > > pc := contextIsActive ifTrue: [aPC] ifFalse: [aPC - 1]. > ^(methodNode nodeForPC: pc) debugHighlightRange > > > And this method one then can just implement on MethodContext itself. > (Caching is handled by ASTCache). > > Marcus > > > -- Best regards, Igor Stasenko.

April 18, 2013

Re: [Pharo-project] the fun theory

by Igor Stasenko

On 18 April 2013 11:21, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > And then you need to save the file, and then you need to reload the map ... > Again save the file, and reload ... > > Each time you reload the program restart at the beginning of course. > > Yeah that would look better in Pharo, basically the same without reload > button but runtime behavior modifications. > yes, plus train would be in separate class :) -- Best regards, Igor Stasenko.

April 18, 2013

Re: [Pharo-project] Understanding Athens

by Igor Stasenko

On 18 April 2013 11:52, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On Apr 18, 2013, at 11:24 AM, kilon wrote: > >> Ok resumed learning of Athens, did look through and experimented with the >> steps of the tutorial , I think I understand the basics now. >> >> Started from a fresh image reinstalled everything and no longer save my >> image with Athens Tutorial open so there is no segfault.But the error >> remains. >> >> LogicalFont>>glyphRenderOn >> >> glyphRendererOn: anAthensBalloonSurface >> ^ self realFont glyphRendererOn: anAthensBalloonSurface >> >> full stack can be found here -> http:// http://pastebin.com/C8itjM2a >> <http:// http://pastebin.com/C8itjM2a> >> >> freetype is enabled in settings , my ears are open for suggestions :) >> >> >> >> -- >> View this message in context: http://forum.world.st/Understanding-Athens-tp4681820p4682265.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > Well, the message is sent to a StrikeFont (the legacy bitmap font, sorta hard to provide a vector-based renderer for), so I guess somewhere, you need to ensure he font used by AthensViewMorph is a LogicalFont whose realFont is an actual TrueTypeFont. > Yes. Athens using freetype fonts. LogicalFont-s work in a way that if it can find a corresponding freetype font, it will use it, otherwise it will fallback to one which comes with image (strike font). If you want to avoid pitfalls with LogicalFont logic, use direct FreeTypeFont instances (but don't ask me where how to obtain them ;) ). > Cheers, > Henry -- Best regards, Igor Stasenko.

April 18, 2013