November 2014 - Pharo-dev - lists.pharo.org

How to import an icon inside Pharo

by kilon alios

Hey guys any idea how to import a icon inside pharo and how to use it ? I have seen that pharo uses a sort of string representation of the icon image . Anyone has experience with this ?

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by kilon alios

to be fair the pharo windows in general are tiny. I can imagine them being ok on 1-2 decades old monitors but for modern monitors they are just too small. I think it makes sense to display only the name of the repository instead of its web location . I would like now that pharo offers good support for git, separate icons for diffirent kinds of repos. Actually talking about icons I think I will start a new thread on it.

Nov. 24, 2014

Re: [Pharo-dev] contributing to Pharo testing effort

by Ben Coman

sheridan(a)sheridan-mahoney.com wrote: > Hi there, > I am interested in helping out with writing tests in Pharo, and was > wondering where would be a good place to start. I am familiar with > Smalltalk from working at GemStone Systems in their QA department some > years ago, but am somewhat new to Pharo. Any advice would be very > appreciated. > > Best regards, > Sheridan Mahoney > > I can't direct you to a particular area, but (not that I've used it) maybe you can try out Hapao to see if it helps you pick where the gaps are. http://www.pharocasts.com/2011/04/test-coverage-with-hapao.html http://hapao.dcc.uchile.cl/ http://objectprofile.com/Hapao.html cheers -ben P.S. I wonder if it would be practical to generate some Hapao reports on each Pharo build as a CI job - to be available as a ready reference for such questions?

Nov. 24, 2014

Re: [Pharo-dev] changing MC repository url display

by Thierry Goubier

Hi Esteban, this is a good change, go on. And thanks for taking care of it! Thierry 2014-11-24 14:09 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > So I have this problem... each time I open a MC browser I see something like > this: > > > And as you can see... most important part of the repositories (the NAME) is > hidded because window is small. > Of course, I can enlarge the screen to see the names, but that made me > think the way the information is presented is not good (because the place, > sthub, ss, ss3 or whatever) is less important than the repository name. > So I would like to change that to something like: > > Pharo/Pharo40 (smalltalkhub.com) > Pharo/Pharo40Inbox (smalltalkhub.com) > Moose/Glamour (smalltalkhub.com) > ./mc (filetree) > VMMaker (source.squeak.org) > ... etc... > > since this is a small change that has a huge visual impact, I would like > to discuss it before. > So, what do you think? > > Esteban > >

Nov. 24, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Tudor Girba

Exciting :) Doru On Mon, Nov 24, 2014 at 2:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > Aliaksei Syrel wrote: > >> Hi Ben, >> >> Thanks :) >> >> Here I opened issue <https://pharo.fogbugz.com/f/ >> cases/14521/Pressing-shift-ctrl-command-options-capslock- >> doesn-t-trigger-corresponding-Event-on-Mac> >> >> I didn't do it before, because Stef wrote, that it's somehow known bug >> and they will try to move to OSWindow in the future. >> > > Cool. I dug in mostly as a chance to explore the VM (my second excursion > into that world.) Its much more interesting poking around when there is a > goal. I was just lucky a potential fix became apparent - but we're yet to > see what it might break. > > cheers -ben > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 24, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Ben Coman

Aliaksei Syrel wrote: > Hi Ben, > > Thanks :) > > Here I opened issue > <https://pharo.fogbugz.com/f/cases/14521/Pressing-shift-ctrl-command-options…> > > I didn't do it before, because Stef wrote, that it's somehow known bug > and they will try to move to OSWindow in the future. Cool. I dug in mostly as a chance to explore the VM (my second excursion into that world.) Its much more interesting poking around when there is a goal. I was just lucky a potential fix became apparent - but we're yet to see what it might break. cheers -ben

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by Ben Coman

Tudor Girba wrote: > Hi, > > Sorry for not replying earlier. Thanks Nicolai for picking this one up. > I missed the initial mail. > > The initialExtent does not make sense for presentation, and anyway, you > would not want to change an inspector when you are inside a flow. If I > understand correctly, Clement would want that when he spawns an > inspector window on a new object, to set the window size to something else. > > The idea of having a gtInitialWindowExtent is intriguing, but it won't > really work. The problem is that an object can have associated > presentations in several external packages, so defining the initial > extent in one of them might not work for the other ones. > > But, I was more thinking of a different mechanism that remembers the > size of the inspector every time you change it, and have the next window > take that size into account. > I am even considering having this size cached by the class of the > object (not sure yet if that makes sense). As I was reading, I was thinking to myself that remembering last size per class would make a lot of sense. Could there be a button in Preferences to save initialExtents to file, so these carry over to new images? cheers -ben

Nov. 24, 2014

changing MC repository url display

by Esteban Lorenzano

Hi, So I have this problemâ¦ each time I open a MC browser I see something like this: And as you can seeâ¦ most important part of the repositories (the NAME) is hidded because window is small. Of course, I can enlarge the screen to see the names, but that made me think the way the information is presented is not good (because the place, sthub, ss, ss3 or whatever) is less important than the repository name. So I would like to change that to something like: Pharo/Pharo40 (smalltalkhub.com <http://smalltalkhub.com/>) Pharo/Pharo40Inbox (smalltalkhub.com <http://smalltalkhub.com/>) Moose/Glamour (smalltalkhub.com <http://smalltalkhub.com/>) ./mc (filetree) VMMaker (source.squeak.org <http://source.squeak.org/>) â¦ etcâ¦ since this is a small change that has a huge visual impact, I would like to discuss it before. So, what do you think? Esteban

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by Tudor Girba

Hi, Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail. The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when he spawns an inspector window on a new object, to set the window size to something else. The idea of having a gtInitialWindowExtent is intriguing, but it won't really work. The problem is that an object can have associated presentations in several external packages, so defining the initial extent in one of them might not work for the other ones. But, I was more thinking of a different mechanism that remembers the size of the inspector every time you change it, and have the next window take that size into account. I am even considering having this size cached by the class of the object (not sure yet if that makes sense). What do you think? Cheers, Doru On Mon, Nov 24, 2014 at 12:57 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-11-12 15:14 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > >> Hello, >> >> I would like for specific objects to change the default window size of >> the glamour inspector (Basically a bigger window will be opened by default >> for these objects). This is because I extended my inspectors to provide >> roassal visualization that are quite large. >> >> How can I do it ? >> >> For example I would like something like that: >> >> MyObject>>#gtInitialWindowExtent >> < gtInitialWindowExtent > >> ^ 800@1000 >> >> Clement >> >> > > I think this is not doable. > You can change the method with the inspector pragma to be called with the > context (inspector instance) > > gtInspectorItemsIn: composite inContext: aGTInspector > <gtInspectorPresentationOrder: 30> > > instead of > > gtInspectorItemsIn: composite > <gtInspectorPresentationOrder: 30> > > this way you have access to the glamour inspector. Unfortunately it does > not have any > window extent property. > > Maybe we can move the initialExtent property from GLMBrowser up to > GLMPresentation? > That way it would be accessible and usable for this aGTInspector argument. > > > > Nicolai > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 24, 2014

Re: [Pharo-dev] editing the default window size of glamour inspector

by Nicolai Hess

2014-11-12 15:14 GMT+01:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > Hello, > > I would like for specific objects to change the default window size of the > glamour inspector (Basically a bigger window will be opened by default for > these objects). This is because I extended my inspectors to provide roassal > visualization that are quite large. > > How can I do it ? > > For example I would like something like that: > > MyObject>>#gtInitialWindowExtent > < gtInitialWindowExtent > > ^ 800@1000 > > Clement > > I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance) gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30> instead of gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30> this way you have access to the glamour inspector. Unfortunately it does not have any window extent property. Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument. Nicolai

Nov. 24, 2014