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

Re: [Pharo-project] [squeak-dev] new Cog VMs available

by Chris Muller

Woo hoo! Thanks Eliot! Quick question, I see you're using a new naming convention, what does 13.13 mean? On Thu, Apr 4, 2013 at 3:14 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > at http://www.mirandabanda.org/files/Cog/VM/VM.r2714/ > > These fix quite a serious bug with the JIT that would cause crashes in large > images. > > CogVM binaries as per VMMaker.oscog-eem.282/r2714 > > Change application name from Croquet to Squeak and change to green Cog > Squeak > icons. Add accurate version info to the Windows exes (include SCCSID in > properties). > > Add the SSLPlugin on mac and linux (won't link on old mingw; need to > update). > > Cogit: Fix *HORRIBLE* yet ancient bug with the CogObjectRep. > Both CogObjectRepresentationForSqueakV3>>couldBeObject: & > CogObjectRepresentationForSqueakV3>>shouldAnnotateObjectReference: > used signed comparisons for oops and so once the heap size > pushes oops into the upper half of the address space constant > oops in machine code were no longer being updated by the GC. > > StackInterpreter: rewrite the login for printing methods so that > printing the frame of a bad receiver won't seg fault. > > Add primitivePathToUsing which mimics the PointerFinder and can hence be > used > to debug or verify it. > > Remove unnecessary forceInterruptCheck in > NewObjectMemory>>become:with:twoWay:copyHash:. > (heartbeat does this for us). > > Fix bug in assert in NewCoObjectMemory>>restoreHeaderOf:to:. > > Slang: > Fix translation of to:by:do: loops so that the limit is not re-evaluated > on each iteration if it may have side-effects. > > Include the correct AioPlugin (UnixAioPlugin) > > Include SqueakSSLPlugin in the configurations. > > Cogit: > Stop reporting EncounteredUnknownBytecode with an error message. > > Fix slip in ceSICMiss: that didn't link new PIC if an MNU case. > > Add pixel peeker prims to BitBltPlugin. > Minor signature changes to BitBltPlugin & HostWindowPlugin from > SmartSyntaxPluginGenerator bug fix. > > -- > best, > Eliot > > >

April 4, 2013

[Pharo-project] new Cog VMs available

by Eliot Miranda

at http://www.mirandabanda.org/files/Cog/VM/VM.r2714/ These fix quite a serious bug with the JIT that would cause crashes in large images. CogVM binaries as per VMMaker.oscog-eem.282/r2714 Change application name from Croquet to Squeak and change to green Cog Squeak icons. Add accurate version info to the Windows exes (include SCCSID in properties). Add the SSLPlugin on mac and linux (won't link on old mingw; need to update). Cogit: Fix *HORRIBLE* yet ancient bug with the CogObjectRep. Both CogObjectRepresentationForSqueakV3>>couldBeObject: & CogObjectRepresentationForSqueakV3>>shouldAnnotateObjectReference: used signed comparisons for oops and so once the heap size pushes oops into the upper half of the address space constant oops in machine code were no longer being updated by the GC. StackInterpreter: rewrite the login for printing methods so that printing the frame of a bad receiver won't seg fault. Add primitivePathToUsing which mimics the PointerFinder and can hence be used to debug or verify it. Remove unnecessary forceInterruptCheck in NewObjectMemory>>become:with:twoWay:copyHash:. (heartbeat does this for us). Fix bug in assert in NewCoObjectMemory>>restoreHeaderOf:to:. Slang: Fix translation of to:by:do: loops so that the limit is not re-evaluated on each iteration if it may have side-effects. Include the correct AioPlugin (UnixAioPlugin) Include SqueakSSLPlugin in the configurations. Cogit: Stop reporting EncounteredUnknownBytecode with an error message. Fix slip in ceSICMiss: that didn't link new PIC if an MNU case. Add pixel peeker prims to BitBltPlugin. Minor signature changes to BitBltPlugin & HostWindowPlugin from SmartSyntaxPluginGenerator bug fix. -- best, Eliot

April 4, 2013

Re: [Pharo-project] Cycling Through Open Windows Using Key Combination

by Sven Van Caekenberghe

On 04 Apr 2013, at 14:16, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > alt+tab / alt+shift+tab > > Ben Yes, you once told me that already if I remember correctly. But it acts weird (does not always come up, unpredictable timeout, no next-next-next, slow). Actually, the action 'Make next-to-topmost' from the WIndow menu is more or less what I want: cycle *quickly* between my main windows, usually 2. > On Apr 4, 2013, at 2:08 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >> Yes, CTRL-W is close window or close tab in a multidocument window in MS Windows. >> >> Regards, >> >> >> ps: Yes, I said windows lots of times. :) >> >> Esteban A. Maringolo >> >> >> 2013/4/4 Sven Van Caekenberghe <sven(a)stfx.eu> >> >> On 04 Apr 2013, at 12:17, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: >> >> > I did a little hack to get that with CTRL+W. will need to dig out the hack code and can send it over.. >> >> OK, but doesn't that key combination close a window ? >> Anyway, looking forward to it. >> >> > On Thu, Apr 4, 2013 at 3:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > Hi, >> > >> > Is there a key combination to cycle through open windows ? >> > >> > I am using Apple-Tab a lot to cycle between open applications on my Mac, and Apple-~ to cycle between open windows in one application. I would love to be able to do something similar inside Pharo. >> > >> > 9 changes out of 10 somebody already did this, maybe it is even in the image. >> > >> > Thx, >> > >> > Sven >> > >> > >> > -- >> > Sven Van Caekenberghe >> > http://stfx.eu >> > Smalltalk is the Red Pill >> >> >> >

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Sven Van Caekenberghe

On 04 Apr 2013, at 19:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 4, 2013, at 7:52 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> >> On 2013-04-04, at 18:51, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 4 April 2013 17:38, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>> On 2013-04-04, at 16:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>>> On 4 April 2013 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>> really? >>>>>> please, add an issue in the tracker and submit a slice, as everybody else. >>>>>> >>>>> calm down, we're just discussing here. >>>>> I provided code here intentionally for nay-sayers like you to try it >>>>> and to check if it not breaks >>>>> something else (your workflow). >>>> >>>> Igor, not Esteban's workflow.. OUR WORKFLOW! >>>> >>> >>> Sure sure. Now have you tried the code which i sent if it works/breaks for you? >>> >>> Or i should spend like 10 minutes filing the issue before figuring >>> that it is unacceptable? >> >> What the fuck do you think the rest does? >> >>> https://pharo.fogbugz.com/default.asp?10228 >> >> |( well the issue is the main entry point. If the code does not work >> you will be notified VIA the issue => manageed entity >> >> However how you solve this issue right now is by some fuzzy undefined process >> nobody manages. If you think that this change is worth getting into pharo then >> you open an issue and attach the SLICE (no changeset, SLICES). >> >> Then the whole machinery starts, people (INCLUDING YOU) look at the issues. >> Issue get rejected, modified, adapted! >> >> What you show here is IGNORANCE on a higher level. >> YOU IGNORE A WHOLE DAMN DEVELOPMENT PROCESS PEOPLE USE EVERY DAY. > > But I think Igor was proposing exactly that what esteban was already arguing agains? > In that case an issue tracker entry makes not much sense, we first need to discuss what > to do. > > Marcus That is also how I understood it: he posted a quick hack asking for feedback, the next step would be to make an issue and proper slice [ which indeed he has to learn to do like everybody else ] - I must admit that I am also still struggling with the new issue tracker (mainly because of lack of time), I miss the old one that I was used to. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Marcus Denker

On Apr 4, 2013, at 7:52 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-04-04, at 18:51, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 4 April 2013 17:38, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>> On 2013-04-04, at 16:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>>> On 4 April 2013 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> really? >>>>> please, add an issue in the tracker and submit a slice, as everybody else. >>>>> >>>> calm down, we're just discussing here. >>>> I provided code here intentionally for nay-sayers like you to try it >>>> and to check if it not breaks >>>> something else (your workflow). >>> >>> Igor, not Esteban's workflow.. OUR WORKFLOW! >>> >> >> Sure sure. Now have you tried the code which i sent if it works/breaks for you? >> >> Or i should spend like 10 minutes filing the issue before figuring >> that it is unacceptable? > > What the fuck do you think the rest does? > >> https://pharo.fogbugz.com/default.asp?10228 > > |( well the issue is the main entry point. If the code does not work > you will be notified VIA the issue => manageed entity > > However how you solve this issue right now is by some fuzzy undefined process > nobody manages. If you think that this change is worth getting into pharo then > you open an issue and attach the SLICE (no changeset, SLICES). > > Then the whole machinery starts, people (INCLUDING YOU) look at the issues. > Issue get rejected, modified, adapted! > > What you show here is IGNORANCE on a higher level. > YOU IGNORE A WHOLE DAMN DEVELOPMENT PROCESS PEOPLE USE EVERY DAY. But I think Igor was proposing exactly that what esteban was already arguing agains? In that case an issue tracker entry makes not much sense, we first need to discuss what to do. Marcus

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Camillo Bruni

On 2013-04-04, at 18:51, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 4 April 2013 17:38, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> On 2013-04-04, at 16:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 4 April 2013 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> really? >>>> please, add an issue in the tracker and submit a slice, as everybody else. >>>> >>> calm down, we're just discussing here. >>> I provided code here intentionally for nay-sayers like you to try it >>> and to check if it not breaks >>> something else (your workflow). >> >> Igor, not Esteban's workflow.. OUR WORKFLOW! >> > > Sure sure. Now have you tried the code which i sent if it works/breaks for you? > > Or i should spend like 10 minutes filing the issue before figuring > that it is unacceptable? What the fuck do you think the rest does? > https://pharo.fogbugz.com/default.asp?10228 |( well the issue is the main entry point. If the code does not work you will be notified VIA the issue => manageed entity However how you solve this issue right now is by some fuzzy undefined process nobody manages. If you think that this change is worth getting into pharo then you open an issue and attach the SLICE (no changeset, SLICES). Then the whole machinery starts, people (INCLUDING YOU) look at the issues. Issue get rejected, modified, adapted! What you show here is IGNORANCE on a higher level. YOU IGNORE A WHOLE DAMN DEVELOPMENT PROCESS PEOPLE USE EVERY DAY. And you put yourself into the brilliant exception position. Believe me I am not the only one who is upset with that. (but usually the one who complains first). So why do I complain? - I know that you haven't filed a single issue on the new issue tracker - I know that you DO NOT like the new issue tracker - I know that you DO NOT like to use SLICES (even though everybody else does) and.. - I am pretty convinced that you will never file an issue on the new issue tracker Why? I don't know, I really don't. I wish I could understand your point here, but I cannot.

April 4, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Jimmie Houchin

I had already enabled Freetype as instructed in the email. So I went ahead and then changed the StandardFont to FreeSans 9 and did Force all. Still did not work. I saved and quit. Restarted and tried again and it worked. I don't know if FreeSans is the best font choice or not, just simply the one that I tried. Jimmie On 04/04/2013 12:33 PM, phil(a)highoctane.be wrote: > Same error here on OSX. I guess it is because we need to use the > FreeType fonts instead of the default StrikeFonts. > > > 2013/4/4 Jimmie Houchin <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> > > On 04/04/2013 11:34 AM, Igor Stasenko wrote: > > On 4 April 2013 17:38, Jimmie Houchin <jlhouchin(a)gmail.com > <mailto:jlhouchin@gmail.com>> wrote: > > Hello, > > I am on Ubuntu 12.10 32bit. > > ... SNIP ... > I then open the image and proceed with loading the code > and the tutorial. > > I skip page 1 and "doit" on page 2 and I get this error. > > Error: failed to get a symbol address: > cairo_image_surface_create > > As far as I can tell, I have Cairo installed on my system. > I have libcairo2. > > check if path to the library is correct for your OS in > CairoLibraryLoader class. > > Thanks, that was the problem. > > On Ubuntu 12.10, I don't have a libcairo.so, but rather a > libcairo.so.2 in /usr/lib/i386-linux-gnu. > > I created the link /usr/lib/libcairo.so as expected by Pharo, and > it works. > > Now, when I get to screen 30, I enabled FreeType as instructed but > I am getting an error > MNU: StrikeFont>>glyphRenderOn: > > Thanks again. > > Jimmie > >

April 4, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by phil＠highoctane.be

Same error here on OSX. I guess it is because we need to use the FreeType fonts instead of the default StrikeFonts. 2013/4/4 Jimmie Houchin <jlhouchin(a)gmail.com> > On 04/04/2013 11:34 AM, Igor Stasenko wrote: > >> On 4 April 2013 17:38, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> >>> Hello, >>> >>> I am on Ubuntu 12.10 32bit. >>> >>> ... SNIP ... >>> I then open the image and proceed with loading the code and the tutorial. >>> >>> I skip page 1 and "doit" on page 2 and I get this error. >>> >>> Error: failed to get a symbol address: cairo_image_surface_create >>> >>> As far as I can tell, I have Cairo installed on my system. I have >>> libcairo2. >>> >> check if path to the library is correct for your OS in >> CairoLibraryLoader class. >> > Thanks, that was the problem. > > On Ubuntu 12.10, I don't have a libcairo.so, but rather a libcairo.so.2 in > /usr/lib/i386-linux-gnu. > > I created the link /usr/lib/libcairo.so as expected by Pharo, and it works. > > Now, when I get to screen 30, I enabled FreeType as instructed but I am > getting an error > MNU: StrikeFont>>glyphRenderOn: > > Thanks again. > > Jimmie > >

April 4, 2013

Re: [Pharo-project] [FYI] Athens tutorial

by Jimmie Houchin

On 04/04/2013 11:34 AM, Igor Stasenko wrote: > On 4 April 2013 17:38, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: >> Hello, >> >> I am on Ubuntu 12.10 32bit. >> >> ... SNIP ... >> I then open the image and proceed with loading the code and the tutorial. >> >> I skip page 1 and "doit" on page 2 and I get this error. >> >> Error: failed to get a symbol address: cairo_image_surface_create >> >> As far as I can tell, I have Cairo installed on my system. I have libcairo2. > check if path to the library is correct for your OS in > CairoLibraryLoader class. Thanks, that was the problem. On Ubuntu 12.10, I don't have a libcairo.so, but rather a libcairo.so.2 in /usr/lib/i386-linux-gnu. I created the link /usr/lib/libcairo.so as expected by Pharo, and it works. Now, when I get to screen 30, I enabled FreeType as instructed but I am getting an error MNU: StrikeFont>>glyphRenderOn: Thanks again. Jimmie

April 4, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Diego Lont

> On 4 April 2013 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> really? >> please, add an issue in the tracker and submit a slice, as everybody else. >> > calm down, we're just discussing here. > I provided code here intentionally for nay-sayers like you to try it > and to check if it not breaks > something else (your workflow). Esteban, Having a new Browser in Pharo 2.0 is a big change. Everyone needs to get used to it. And I agree it is probably a good thing. But â¦ there are some things that worked better in OB that I don't want to loose. There are a lot of people annoyed by how it works nowâ¦. but I think the mailing list is about exchanging arguments not about deciding. So I do not like that you try to end the discussion by shouting: the defaults will not change. So here I will add a new argument. Your argument about other languages is a valid point, but only holds if Smalltalk is similar as other languages. Why does this "enter" annoys me? Because in some cases it replaces my code by garbage. At least when I type a method invocation that does not exist yet, it replaces it by an existing method. And this is repeatable. So when you go back (using backspace and typing it again, because it also adds before the things I typed) and the press enter again, it does the same replacement. So there is a difference here between smalltalk and other languages. When I do test-driven development (that I do a lot), I first write my test, invoking a lot of methods that do not exist yet. I do not do this in another language, because my environment isn't good enough then.

April 4, 2013