- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Inserting halts using pragmas?

by Fernando olivero

I see, thanks Lukas for the info. My wish for the new editor i'm developing is to able to insert halts, into the code just as any other IDE. By selecting the statement and indicating by some means to insert a halt ( called breakpoint in non-proccess reified languages). Would be nice to get that code, if not i'll implement my own debugging wrapper. Fernando On Apr 12, 2010, at 11:11 AM, Lukas Renggli wrote: >> Hi, can we inserts halt's into methods without modifying source code, using pragmas maybe? > > This has nothing to do with pragmas. Pragmas do not change execution > behavior of a compiled method. Also pragmas are in the source code, so > you cannot add them without changing the source. > > There was some work on annotations by Marcus, this goes more into the > direction you are looking for. > > What I would do is to replace a compiled method with a custom object > that implements #run:with:in: and that opens a debugger at the right > place. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 12, 2010

Re: [Pharo-project] Inserting halts using pragmas?

by StÃ©phane Ducasse

There was a break on enter code somewhere. Does anybody remember? I remember some code of igor to do that. Would be good to resurrect that. Stef On Apr 12, 2010, at 10:27 AM, Fernando olivero wrote: > Hi, can we inserts halt's into methods without modifying source code, using pragmas maybe? > > Has there been work on this? > > Thanks, > Fernando > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 12, 2010

[Pharo-project] [ANN] Pharo Windows VM 4.0.2

by Torsten Bergmann

There is a new 4.0.2 Pharo VM for Windows available (see [1]) based on the same Squeak VM release. If you want to build it yourself just use [2]. There was no official announcement from Andreas on 4.0.2 on vm-dev list but according to the logs ([3]) sound recording should work again with this release. Note that the 4.0x VM's redirect the window close event to the image (see discussion in [4]) Therefore this 4.0.2 VM is mainly useful for people who base their work on Pharo 1.1. Core Alpha (as of today image nr #11312) since the Pharo 1.1 image already includes the support to handle the window close event directly from within the image. When you want to use Pharo core 1.0 (currently image #10517) with this VM you have to use SHIFT+ALT+F4 to close the image. Therefor it is better to use 3.11.8 VM (see 5) with the 1.0 images. Bye T. [1] https://gforge.inria.fr/frs/download.php/26814/PharoVM-Win32-4.0.2-bin.zip [2] https://gforge.inria.fr/frs/download.php/26815/PharoVM-Win32-4.0.2-src.zip [3] http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-April/148560.ht… [4] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-April/024677.html [5] https://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 12, 2010

Re: [Pharo-project] news about 1.0

by Henrik Johansen

On Apr 11, 2010, at 11:26 03PM, StÃ©phane Ducasse wrote: > Hi guys > > mariano, marcus and adrian got some push to get 1.0 out. I was just on cc: > I think that we made a mistake not to roll that publicly via the mailing-list (we will do that for 1.1). > Now this is holidays time here, mariano is going to get married and adrian just moved so no > internet connection. > Tomorrow I will sync with marcus to know if I can help to get this 1.0 version out. > If I remember the mails I saw, marcus was looking for the > BitBltPluging binaries for the one click image on other platforms than mac os. > > Stef Hum, aren't they usually built as internal? In that case, the only reason for including plugin binaries would be if there's been bug fixes to it since the vm was shipped... Which would probably mean you're providing a too old VM in the first place. IIRC, On Windows, 3.11.8 / 4.0.2 would both include updated plugins, the main difference being 4.0.2 providing support for old image segment loading, but requiring in-image handling of quit events. Not sure about linux, since I don't use it. Seems to be in a state of updating at the moment, with 5-6 commits over the weekend, so might be worth waiting for. Cheers, Henry

April 12, 2010

Re: [Pharo-project] Inserting halts using pragmas?

by Peter Hugosson-Miller

On Mon, Apr 12, 2010 at 11:11 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Hi, can we inserts halt's into methods without modifying source code, > using pragmas maybe? > > This has nothing to do with pragmas. Pragmas do not change execution > behavior of a compiled method. Also pragmas are in the source code, so > you cannot add them without changing the source. > > There was some work on annotations by Marcus, this goes more into the > direction you are looking for. > > What I would do is to replace a compiled method with a custom object > that implements #run:with:in: and that opens a debugger at the right > place. > Yes, that's more or less how VisualAge does it. See DbgBreakpointedMethod, a variable Subclass of CompiledMethod. -- Cheers, Peter > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 12, 2010

Re: [Pharo-project] Inserting halts using pragmas?

by Lukas Renggli

> Hi, Â can we inserts halt's into methods without modifying source code, using pragmas maybe? This has nothing to do with pragmas. Pragmas do not change execution behavior of a compiled method. Also pragmas are in the source code, so you cannot add them without changing the source. There was some work on annotations by Marcus, this goes more into the direction you are looking for. What I would do is to replace a compiled method with a custom object that implements #run:with:in: and that opens a debugger at the right place. Lukas -- Lukas Renggli www.lukas-renggli.ch

April 12, 2010

[Pharo-project] Inserting halts using pragmas?

by Fernando olivero

Hi, can we inserts halt's into methods without modifying source code, using pragmas maybe? Has there been work on this? Thanks, Fernando

April 12, 2010

Re: [Pharo-project] fixing underscores in a trivial manner thanks to SmalllintChecker and Lukas!

by StÃ©phane Ducasse

done. It is pier so everybody can edit it :) Stef On Apr 12, 2010, at 9:32 AM, Lukas Renggli wrote: > Gofer new > squeaksource: 'rb'; > version: 'AST-Core-lr.67'; > version: 'Refactoring-Core-lr.122'; > load.

April 12, 2010

Re: [Pharo-project] Canvas transform bug when rendering text?

by David Harvey

Henrik, all, thanks for your help with this. I've been away from the codeface for a while and haven't yet tried all of the fixes. I did get things rendering well by caching the form canvas and redrawing that when required (just as the HandMorph does - as I said, the rendering while dragging is always OK). Relevant code below: >>>> drawOn: aCanvas super drawOn: aCanvas. cachedCanvas isNil ifTrue: [ cachedCanvas := (aCanvas allocateForm: self bounds extent) getCanvas. self drawContentsOn: cachedCanvas. ]. aCanvas translucentImage: cachedCanvas form at: self bounds origin. <<<< Best David ------------------ David Harvey www.teamsandtechnology.com www.cateams.com @david_harvey On 7 April 2010 12:45, David Harvey <david(a)teamsandtechnology.com> wrote: > Hi list, > > I'm writing a little charting morph, and while playing with rotating text > for axis labels came across something which I've noted in Morphs text > handling a couple of times. > > If I apply a transform in a drawing operation, rotated text _appears_ to be > drawn twice, slightly offset, giving a scrappy bold look. It seems only to > do this when drawing on a form canvas that's backed onto the display: if you > pick and drag the morph, the text is rendered beautifully. > > The test morph attached isolates the problem. The transcript logging is an > attempt to see what might be happening: looking at the output it appears > that there are circumstances in which the during: block is invoked twice. > > Any thoughts? > > David > > ------------------ > David Harvey > www.teamsandtechnology.com > www.cateams.com > @david_harvey >

April 12, 2010

Re: [Pharo-project] fixing underscores in a trivial manner thanks to SmalllintChecker and Lukas!

by Lukas Renggli

It would be good to hardcode the version numbers and to tell that a Pharo 1.0 image has to be used: Gofer new squeaksource: 'rb'; version: 'AST-Core-lr.67'; version: 'Refactoring-Core-lr.122'; load. Pharo 1.1 won't be able to load underscore assignments anymore. Lukas On 12 April 2010 09:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > http://book.pharo-project.org/book/TipsAndTricks/FixingUnderscores/ > > :) > > > On Apr 12, 2010, at 12:51 AM, Fernando olivero wrote: > >> Hi all, i just wanted to re post the fix underscore code Lukas posted a while ago. >> >> I've just imported Connectors package into pharo, (i'm trying to get a minimal version working ), and stumbled upon the problem of the underscores.. >> but now thanks to SmallInt rules it was easy and fast to overcome this problem! >> >> Thanks!!!! >> >> Fernando >> >> >> pd: From previous mail from lukas. >> >> >> 1. Load the code: >> >> Â Gofer new >> Â Â Â squeaksource: 'rb'; >> Â Â Â package: 'AST-Core'; >> Â Â Â package: 'Refactoring-Core'; >> Â Â Â load. >> >> 2. Select the code (packages) you want to fix: >> >> Â environment := BrowserEnvironment new >> Â Â Â forPackageNames: #('Connectors-Base' 'Connectors-Lines and Curves'). >> >> 3. Create the transformation rule: >> >> Â rule := RBUnderscoreAssignmentRule new. >> >> 4. Perform the search: >> >> Â SmalllintChecker runRule: rule onEnvironment: environment. >> >> 5. Perform the transformation: >> >> Â change := CompositeRefactoryChange new. >> Â change changes: rule changes. >> Â change execute >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

April 12, 2010