February 2015 - Pharo-users

i feel dumb / Pharo3 > OrderedCollection >> do:

by Cameron Sanders

I must be making some silly error here that i cannot see clearly. Why does the following leave anything in the list 'a'? Run it in a workspace. With or without the shallowCopy, i am left with a list with half of the elements in it. Always half. This version of Pharo3 (21.0) was downloaded last week. I am running on a Mac. Thanks in advance. ... Maybe I just need more coffee. -Cam | a | a := { #a. #b. #c. #d. } asOrderedCollection. a shallowCopy do: [ :item | (a includes: item) ifTrue: [ a remove: item ]]. a size

Feb. 18, 2015

Re: [Pharo-users] What happens to saved inspectors?

by Blondeau Vincent

Hello Peter, If your are on Moose, you are using the Glamour inspector. Can you describe more precisely the kind of items you are inspecting? Do you inspect external resources? Or use Semaphores, forks, network? I am remembering a bug on Roassal. It used external ressources that was desallocated at image shutdown. On image relaunch, the external ressources was still pointed by a cache and the yellow cross on red appears. By the way, behind the cross, it should be a text, can you see it? I know that these kind of issues are very difficult to reproduce but if you can do it on a fresh image, it will be easier for us to help you ;) I cross-posted to the Moose mailing list where people are more aware of this kind of issues. Vincent De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la part de PBKResearch EnvoyÃ© : mercredi 18 fÃ©vrier 2015 17:32 Ã : 'Any question about pharo is welcome' Objet : Re: [Pharo-users] What happens to saved inspectors? ClÃ©ment I am not sure, but I think Moose uses the Glamour inspector. You get exactly the same inspector whether you select âInspectâ or âExploreâ from the world menu. As you click on an item in the current display, a new inspector pane opens to the right showing detail of the selected item, with tabs to select the form of display â the first one is always âRawâ but the others are dependent on the kind of item being displayed, e.g. if inspecting an XML document there is always a âTreeâ option. I think that sounds like Glamour, doesnât it? The main heading on the title bar is static, i.e. it always shows the item you originally inspected. When there are multiple inspector panes open, each one has its own title below the main window title, showing the item that was clicked to open it. In this case, the title of the first inspector pane, which is the same as the main window title, is also replaced by the red error display, but the titles of the other inspector panes are OK. Hope this helps. If any more detail would be helpful, let me know. Thanks Peter Kenny From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of ClÃ©ment Bera Sent: 18 February 2015 11:37 To: Any question about pharo is welcome Subject: Re: [Pharo-users] What happens to saved inspectors? Hey, Inspectors are different between Moose and Pharo 3. Can you precise, are you using the Glamour inspector, the EyeInspector or the old Morphic inspector ? I have never seen that in Pharo. Are your titles dynamic (I mean, when the object changes, can your title change ?) ? 2015-02-18 11:35 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>>: Hello I am using Moose 5, which is essentially Pharo 3, downloaded late December 2014. I have a development project which mainly consists of a collection of workspaces and inspectors (I really do intend to turn it into a properly structured set of classes one day!). I have noticed that, whenever I save an image with some inspectors open and then reopen the image, the title bars of the inspectors have become red rectangles with a cross superimposed. Often I can work out what the title should be and carry on, but in many cases all I can do is close down the inspector and reopen it. Is this a known problem, and is there any way to work round it? Thanks for any help Peter Kenny ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Ben Coman

btw, I'd really like to get the following three fixes into Pharo 4 before the code freeze. * 16 steps to get through #halt Status: Ready to review (https://pharo.fogbugz.com/default.asp?12970) * Delay refactoring (part 2b) - clean out newCodeEnabled wrappers Status: Ready to review (should be easy, https://pharo.fogbugz.com/default.asp?14942) * Change Delay from milliseconds to microseconds ( http://pharo.fogbugz.com/default.asp?14353) Status: This was reviewed and went for integration a while ago, but needs to be rebased on the build following cleanup of newCodeEnabled (issue 14042). cheers -ben On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 18 Feb 2015, at 16:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > one less :) > but really, the problem is that those issues are mistaking issuesâ¦ For > OSWindow integration they are understanding three things: > > 1) the integration of OSWindow mechanism as a way to control the system > window. > 2) the replacement of current input event mechanism with a new, > image-level one, more complete and modern. > 3) the replacement of current BitBlt system window with one based on SDL2 > and vectorial graphics (Athens-based). > > As you might imagineâ¦ steps 2 and 3 are really needed, but far from easy. > The only step that we could mark as âdoneâ right now is the first oneâ¦ > steps 2 and 3 are âmore or lessâ workedâ¦ there are prototypes but still not > realistic estimation of what amount of time will take to actually do itâ¦ It > is âthoughtâ to be done in Pharo5â¦ weâll see. > > And the problem on integrating some of those changes is that are > âone-way-shotsââ¦ once done, we cannot go back. > I will mark some of those issues as âon holdâ with a clarification. > > > done > > > cheers, > Esteban > > On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> it depends on your definition of âstatusâ :) >> > > :) > That is easy to define: > definition of "status" = fogbugz status > -> OSWindow 6 open issues > > > > > > >> first version is integrated >> latest vm includes also SDL2 plugin. >> >> but is there as *preview*, which means a lot of work still needs to be >> done. >> >> cheers, >> Esteban >> >> >> On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> What is the state of OSWindow integration? >> This release or later? >> >> >> >> 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Hi, >>> >>> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 >>> after February 28, and we will work on stabilisation and bug fixedâ¦ we are >>> aiming to release in April 1st. >>> This version will not be spur-based, that will come with the summer >>> release. >>> >>> Cheers, >>> Esteban >>> >> >> >> > > >

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Ben Coman

So how are externally managed ConfigurationOf packages going to be handled in this period? Last year I felt (maybe unjustified) that more than bug fixes slipped in when an external package like Spec was synchronised in the code freeze period. Do developers of an external package like for Spotter and Playground have to halt their feature development branch, so that bug fixes can be incorporated separately? cheers -ben On Thu, Feb 19, 2015 at 12:21 AM, Ben Coman <btc(a)openinworld.com> wrote: > So the in Fogbugz we need probably milestone tags for Pharo 4.1 and Pharo > 5.0 so we can push issues to them. > cheers -ben > > On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> On 18 Feb 2015, at 16:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> one less :) >> but really, the problem is that those issues are mistaking issuesâ¦ For >> OSWindow integration they are understanding three things: >> >> 1) the integration of OSWindow mechanism as a way to control the system >> window. >> 2) the replacement of current input event mechanism with a new, >> image-level one, more complete and modern. >> 3) the replacement of current BitBlt system window with one based on SDL2 >> and vectorial graphics (Athens-based). >> >> As you might imagineâ¦ steps 2 and 3 are really needed, but far from easy. >> The only step that we could mark as âdoneâ right now is the first oneâ¦ >> steps 2 and 3 are âmore or lessâ workedâ¦ there are prototypes but still not >> realistic estimation of what amount of time will take to actually do itâ¦ It >> is âthoughtâ to be done in Pharo5â¦ weâll see. >> >> And the problem on integrating some of those changes is that are >> âone-way-shotsââ¦ once done, we cannot go back. >> I will mark some of those issues as âon holdâ with a clarification. >> >> >> done >> >> >> cheers, >> Esteban >> >> On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> >> >> 2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> it depends on your definition of âstatusâ :) >>> >> >> :) >> That is easy to define: >> definition of "status" = fogbugz status >> -> OSWindow 6 open issues >> >> >> >> >> >> >>> first version is integrated >>> latest vm includes also SDL2 plugin. >>> >>> but is there as *preview*, which means a lot of work still needs to be >>> done. >>> >>> cheers, >>> Esteban >>> >>> >>> On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> What is the state of OSWindow integration? >>> This release or later? >>> >>> >>> >>> 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> Hi, >>>> >>>> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 >>>> after February 28, and we will work on stabilisation and bug fixedâ¦ we are >>>> aiming to release in April 1st. >>>> This version will not be spur-based, that will come with the summer >>>> release. >>>> >>>> Cheers, >>>> Esteban >>>> >>> >>> >>> >> >> >> >

Feb. 18, 2015

Re: [Pharo-users] What happens to saved inspectors?

by PBKResearch

ClÃ©ment I am not sure, but I think Moose uses the Glamour inspector. You get exactly the same inspector whether you select âInspectâ or âExploreâ from the world menu. As you click on an item in the current display, a new inspector pane opens to the right showing detail of the selected item, with tabs to select the form of display â the first one is always âRawâ but the others are dependent on the kind of item being displayed, e.g. if inspecting an XML document there is always a âTreeâ option. I think that sounds like Glamour, doesnât it? The main heading on the title bar is static, i.e. it always shows the item you originally inspected. When there are multiple inspector panes open, each one has its own title below the main window title, showing the item that was clicked to open it. In this case, the title of the first inspector pane, which is the same as the main window title, is also replaced by the red error display, but the titles of the other inspector panes are OK. Hope this helps. If any more detail would be helpful, let me know. Thanks Peter Kenny From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of ClÃ©ment Bera Sent: 18 February 2015 11:37 To: Any question about pharo is welcome Subject: Re: [Pharo-users] What happens to saved inspectors? Hey, Inspectors are different between Moose and Pharo 3. Can you precise, are you using the Glamour inspector, the EyeInspector or the old Morphic inspector ? I have never seen that in Pharo. Are your titles dynamic (I mean, when the object changes, can your title change ?) ? 2015-02-18 11:35 GMT+01:00 PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> >: Hello I am using Moose 5, which is essentially Pharo 3, downloaded late December 2014. I have a development project which mainly consists of a collection of workspaces and inspectors (I really do intend to turn it into a properly structured set of classes one day!). I have noticed that, whenever I save an image with some inspectors open and then reopen the image, the title bars of the inspectors have become red rectangles with a cross superimposed. Often I can work out what the title should be and carry on, but in many cases all I can do is close down the inspector and reopen it. Is this a known problem, and is there any way to work round it? Thanks for any help Peter Kenny

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Ben Coman

So the in Fogbugz we need probably milestone tags for Pharo 4.1 and Pharo 5.0 so we can push issues to them. cheers -ben On Wed, Feb 18, 2015 at 11:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 18 Feb 2015, at 16:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > one less :) > but really, the problem is that those issues are mistaking issuesâ¦ For > OSWindow integration they are understanding three things: > > 1) the integration of OSWindow mechanism as a way to control the system > window. > 2) the replacement of current input event mechanism with a new, > image-level one, more complete and modern. > 3) the replacement of current BitBlt system window with one based on SDL2 > and vectorial graphics (Athens-based). > > As you might imagineâ¦ steps 2 and 3 are really needed, but far from easy. > The only step that we could mark as âdoneâ right now is the first oneâ¦ > steps 2 and 3 are âmore or lessâ workedâ¦ there are prototypes but still not > realistic estimation of what amount of time will take to actually do itâ¦ It > is âthoughtâ to be done in Pharo5â¦ weâll see. > > And the problem on integrating some of those changes is that are > âone-way-shotsââ¦ once done, we cannot go back. > I will mark some of those issues as âon holdâ with a clarification. > > > done > > > cheers, > Esteban > > On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> it depends on your definition of âstatusâ :) >> > > :) > That is easy to define: > definition of "status" = fogbugz status > -> OSWindow 6 open issues > > > > > > >> first version is integrated >> latest vm includes also SDL2 plugin. >> >> but is there as *preview*, which means a lot of work still needs to be >> done. >> >> cheers, >> Esteban >> >> >> On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> What is the state of OSWindow integration? >> This release or later? >> >> >> >> 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Hi, >>> >>> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 >>> after February 28, and we will work on stabilisation and bug fixedâ¦ we are >>> aiming to release in April 1st. >>> This version will not be spur-based, that will come with the summer >>> release. >>> >>> Cheers, >>> Esteban >>> >> >> >> > > >

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Esteban Lorenzano

> On 18 Feb 2015, at 16:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > one less :) > but really, the problem is that those issues are mistaking issuesâ¦ For OSWindow integration they are understanding three things: > > 1) the integration of OSWindow mechanism as a way to control the system window. > 2) the replacement of current input event mechanism with a new, image-level one, more complete and modern. > 3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based). > > As you might imagineâ¦ steps 2 and 3 are really needed, but far from easy. > The only step that we could mark as âdoneâ right now is the first oneâ¦ steps 2 and 3 are âmore or lessâ workedâ¦ there are prototypes but still not realistic estimation of what amount of time will take to actually do itâ¦ It is âthoughtâ to be done in Pharo5â¦ weâll see. > > And the problem on integrating some of those changes is that are âone-way-shotsââ¦ once done, we cannot go back. > I will mark some of those issues as âon holdâ with a clarification. done > > cheers, > Esteban > >> On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> >> 2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> it depends on your definition of âstatusâ :) >> >> :) >> That is easy to define: >> definition of "status" = fogbugz status >> -> OSWindow 6 open issues >> >> >> >> >> >> first version is integrated >> latest vm includes also SDL2 plugin. >> >> but is there as *preview*, which means a lot of work still needs to be done. >> >> cheers, >> Esteban >> >> >>> On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >>> >>> What is the state of OSWindow integration? >>> This release or later? >>> >>> >>> >>> 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >>> Hi, >>> >>> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixedâ¦ we are aiming to release in April 1st. >>> This version will not be spur-based, that will come with the summer release. >>> >>> Cheers, >>> Esteban >>> >> >> >

Feb. 18, 2015

Re: [Pharo-users] Issues with code formatting

by sergio_101

found it! thanks!.. i dunno why i couldn't find it before... thanks again! On Tue Feb 17 2015 at 4:05:48 PM Nicolai Hess <nicolaihess(a)web.de> wrote: > 2015-02-17 21:53 GMT+01:00 sergio_101 <sergio.rrd(a)gmail.com>: > >> i am using pharo 3.. i don't see many options under pretty printing.. >> especially when dealing with cascading... hmmm... >> > > > Settings browser -> Refactoring Engine -> Configurable Formatter > > > >> >> On Tue Feb 17 2015 at 10:35:58 AM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> Hi, >>> >>> what version are you using? I see it in the settings under Code Browsing >>> > Pretty Printing. >>> >>> Peter >>> >>> On Tue, Feb 17, 2015 at 3:17 PM, sergio_101 <sergio.rrd(a)gmail.com> >>> wrote: >>> >>>> my pretty print is acting much differently than it used to. it seems to >>>> be breaking every statement into a separate line. at some point, i remember >>>> being able to adjust this via some system settings, but i am not finding >>>> that anymore. is this called something different now, or am i just not >>>> understanding how it works? >>>> >>>> thanks! >>>> >>> >>>

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Esteban Lorenzano

one less :) but really, the problem is that those issues are mistaking issuesâ¦ For OSWindow integration they are understanding three things: 1) the integration of OSWindow mechanism as a way to control the system window. 2) the replacement of current input event mechanism with a new, image-level one, more complete and modern. 3) the replacement of current BitBlt system window with one based on SDL2 and vectorial graphics (Athens-based). As you might imagineâ¦ steps 2 and 3 are really needed, but far from easy. The only step that we could mark as âdoneâ right now is the first oneâ¦ steps 2 and 3 are âmore or lessâ workedâ¦ there are prototypes but still not realistic estimation of what amount of time will take to actually do itâ¦ It is âthoughtâ to be done in Pharo5â¦ weâll see. And the problem on integrating some of those changes is that are âone-way-shotsââ¦ once done, we cannot go back. I will mark some of those issues as âon holdâ with a clarification. cheers, Esteban > On 18 Feb 2015, at 16:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > it depends on your definition of âstatusâ :) > > :) > That is easy to define: > definition of "status" = fogbugz status > -> OSWindow 6 open issues > > > > > > first version is integrated > latest vm includes also SDL2 plugin. > > but is there as *preview*, which means a lot of work still needs to be done. > > cheers, > Esteban > > >> On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> What is the state of OSWindow integration? >> This release or later? >> >> >> >> 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> Hi, >> >> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 after February 28, and we will work on stabilisation and bug fixedâ¦ we are aiming to release in April 1st. >> This version will not be spur-based, that will come with the summer release. >> >> Cheers, >> Esteban >> > >

Feb. 18, 2015

Re: [Pharo-users] [ANN] Pharo4 code freeze will be 28/Feb, release target 1/Apr

by Nicolai Hess

2015-02-18 15:46 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > it depends on your definition of âstatusâ :) > :) That is easy to define: definition of "status" = fogbugz status -> OSWindow 6 open issues > first version is integrated > latest vm includes also SDL2 plugin. > > but is there as *preview*, which means a lot of work still needs to be > done. > > cheers, > Esteban > > > On 18 Feb 2015, at 14:12, Nicolai Hess <nicolaihess(a)web.de> wrote: > > What is the state of OSWindow integration? > This release or later? > > > > 2015-02-18 13:28 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hi, >> >> Soâ¦ Iâm announcing that we will not introduce any new change to Pharo4 >> after February 28, and we will work on stabilisation and bug fixedâ¦ we are >> aiming to release in April 1st. >> This version will not be spur-based, that will come with the summer >> release. >> >> Cheers, >> Esteban >> > > >

Feb. 18, 2015