February 2015 - Pharo-users

Re: [Pharo-users] Installing GToolkit

by Marcus Denker

> On 03 Feb 2015, at 20:50, Craig <craig(a)hivemind.net> wrote: > > Anybody got any ideas if and when GToolkit will be available on Pharo 4? > We are shipping with it since some time before christmas. -> Workspace defaults to the âPlaygroundâ -> inspector/explorer are using GTInspector (but one can use the old ones instead if needed) -> GT Spotter is there, too (shift-Enter to get to it) GT Debugger is not yet in Pharo4. Partly because is used to be for Pharo3, without the Context Cleanup, partly because the UI needs some iteration (it is hard to understand the icons right now). > Just Asking > > Craig > > > From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org <mailto:pharo-users-bounces@lists.pharo.org>] On Behalf Of Tudor Girba > Sent: 05 October 2014 08:19 AM > To: Any question about pharo is welcome > Subject: Re: [Pharo-users] Installing GToolkit > > Hi Evan, > > The instructions are a bit wrong. It should be "activateWithoutSaving" instead of "activate". > > The GTImageSetupCommandLineHandler does more default settings. Just take a look at the activateWithoutSaving method and pick what you want, or use the script that Phil suggested only to install the tools. > > But, what do you mean when you say that the Playground is not working? > > Cheers, > Doru > On Sat, Oct 4, 2014 at 8:07 PM, Evan Donahue <emdonahu(a)gmail.com <mailto:emdonahu@gmail.com>> wrote: > Hello,

Feb. 3, 2015

Re: [Pharo-users] Installing GToolkit

by Craig

Anybody got any ideas if and when GToolkit will be available on Pharo 4? Just Asking Craig From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Tudor Girba Sent: 05 October 2014 08:19 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Installing GToolkit Hi Evan, The instructions are a bit wrong. It should be "activateWithoutSaving" instead of "activate". The GTImageSetupCommandLineHandler does more default settings. Just take a look at the activateWithoutSaving method and pick what you want, or use the script that Phil suggested only to install the tools. But, what do you mean when you say that the Playground is not working? Cheers, Doru On Sat, Oct 4, 2014 at 8:07 PM, Evan Donahue <emdonahu(a)gmail.com> wrote: Hello,

Feb. 3, 2015

Re: [Pharo-users] Monticello review web application

by stepharo

What I would love is to bind it with epicea. The users can comment the files. What is cool with Epicea is that a change has semantics and a before and after state. Finally often you do a change (composed of different modifications) and that you do not want to see all the modifications one by one but Ok I split this method into one in the superclass and one in the superclass. Side note: The more I think the more I think that epicea entity commenting entiy should be held in a separate file ( but I should discuss with Martin). Now I was in the process to propose to students to build an in image tools for support the code review. But having a server is much better. Like that people can share comment. Where you tool takes its input? Stef > Hello, > > I had some spare time and I built a prototype web application for comparing > Monticello versions. I developed it using Seaside and Monticello version > diff implementation in Pharo. It was super easy to reuse the classes which > are responsible for downloading, comparing and generating diffs of > Monticello packages. Once again I see how extraordinary it is to have such > open system as Pharo. > > I made this web app for my work with students as often I need to compare > their versions of packages across different projects/repositories. For > instance, the package is uploaded to PillarHub-Inbox and I want to compare > and discuss changes against the main repository. > > Having this in mind I created a small web app called "Monticello Seaside > Review" (didn't get any better). > > You may find an example review here: > > http://review.pharocloud.com/msr/review/ehx82xz90kpnm56u9exkrul5q/4 > > You may also log in to this instance and play with it as it is not really > used so no problem if it crash for some reason :) > > The sources of the project can be found here: > http://smalltalkhub.com/#!/~mikefilonov/MonticelloSeasideReview > > I would be happy of someone finds the project useful and contributes some > ideas. > > Thank you, > Mike > > > > -- > View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 3, 2015

Re: [Pharo-users] Monticello review web application

by stepharo

Excellent We were discussing with alberto and martin about a tool to support code review :) Le 3/2/15 18:41, mikefilonov a Ã©crit : > Hello, > > I had some spare time and I built a prototype web application for comparing > Monticello versions. I developed it using Seaside and Monticello version > diff implementation in Pharo. It was super easy to reuse the classes which > are responsible for downloading, comparing and generating diffs of > Monticello packages. Once again I see how extraordinary it is to have such > open system as Pharo. > > I made this web app for my work with students as often I need to compare > their versions of packages across different projects/repositories. For > instance, the package is uploaded to PillarHub-Inbox and I want to compare > and discuss changes against the main repository. > > Having this in mind I created a small web app called "Monticello Seaside > Review" (didn't get any better). > > You may find an example review here: > > http://review.pharocloud.com/msr/review/ehx82xz90kpnm56u9exkrul5q/4 > > You may also log in to this instance and play with it as it is not really > used so no problem if it crash for some reason :) > > The sources of the project can be found here: > http://smalltalkhub.com/#!/~mikefilonov/MonticelloSeasideReview > > I would be happy of someone finds the project useful and contributes some > ideas. > > Thank you, > Mike > > > > -- > View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 3, 2015

Re: [Pharo-users] NumericalMethods and SciSmalltalk

by stepharo

Nice but it looks like a physic project :) Le 3/2/15 16:02, Ignacio Sniechowski a Ã©crit : > Given that I proposed the name, I couldn't resist to propose the logo :p > what do you think? > I've checked and the image has a free license. > best > Nacho > > > *Lic. Ignacio Sniechowski, MBA** > * > *Prosavic SRL* > * > * > *Tel: (011) 4542-6714* > * > * > * > * > * > * > > * > * > * > * > * > * > * > * > * > * > * > * > > * > * > * > * > * > * > * > > ** > ** > * > > > > > On Sat, Jan 31, 2015 at 2:48 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > Le 27/1/15 00:29, Werner Kassens a Ã©crit : > > let me rephrase it <g> just that there are no > misunderstandings, NumericalMethods is independent of > SciSmalltalk and does work in Pharo4 > > > By SciTalk will include its own copy of NumericalMethods. > > Stef > > werner > > > On 01/26/2015 10:22 PM, Ignacio Sniechowski wrote: > > That was my question. If in Pharo 4 the NumericalMethods > package will be > deprecated and instead SciSmalltalk will be de defacto > package for stats. > > > > > >

Feb. 3, 2015

Re: [Pharo-users] Slides from the Pharo Status talk at FOSDEM 2015

by Sean P. DeNigris

kilon.alios wrote > Yes sure , I agree, but why that does not apply to Pharo ? Pharo as a principle has prioritized "do the right thing" over backward compatibility, and by consequence to lose users who won't accept that. Now amazingly, in practice, migration has for the most-part been a breeze, partly because a lot of the mess is buried way down in the system internals where user code isn't usually directly dependent. So I would say it doesn't apply to Pharo because Pharo is playing a different game. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Slides-from-the-Pharo-Status-talk-at-FOSDEM-2015-tp48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 3, 2015

Re: [Pharo-users] Slides from the Pharo Status talk at FOSDEM 2015

by kilon alios

Yes sure , I agree, but why that does not apply to Pharo ? I would not want to use Pharo libraries that get changed and redesigned in each version and I have to rewrite my code. I could not even imagine the nightmare scenario of having a big code base and a language that keep changing. Python broke compatibility from version 2 to version 3 and it was not a smooth ride for people, it took years for people to migrate and still there are a lot that are still using Python 2. The changes they made were not even that big and even offered a tool to automagically convert code from version 2 to version 3. What makes Pharo immune to this situation ? because the way I see it Pharo is not immune at all. On Tue, Feb 3, 2015 at 7:19 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > kilon.alios wrote > > If you mean something more than that, then I am open to other opinions as > > always :) > > The only meaning I connected to C++ and Ruby were that they were > dogmatically and widely enough approved for use to be rigid by necessity. > Based on some of your comments, I assume I probably could have used Python > as an example of a language that got popular enough to expand beyond people > that truly "get it", and thus have significant push back to > non-backward-compatibility in the community. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Slides-from-the-Pharo-Status-talk-at-FOSDEM-2015-tp48… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Feb. 3, 2015

Monticello review web application

by mikefilonov

Hello, I had some spare time and I built a prototype web application for comparing Monticello versions. I developed it using Seaside and Monticello version diff implementation in Pharo. It was super easy to reuse the classes which are responsible for downloading, comparing and generating diffs of Monticello packages. Once again I see how extraordinary it is to have such open system as Pharo. I made this web app for my work with students as often I need to compare their versions of packages across different projects/repositories. For instance, the package is uploaded to PillarHub-Inbox and I want to compare and discuss changes against the main repository. Having this in mind I created a small web app called "Monticello Seaside Review" (didn't get any better). You may find an example review here: http://review.pharocloud.com/msr/review/ehx82xz90kpnm56u9exkrul5q/4 You may also log in to this instance and play with it as it is not really used so no problem if it crash for some reason :) The sources of the project can be found here: http://smalltalkhub.com/#!/~mikefilonov/MonticelloSeasideReview I would be happy of someone finds the project useful and contributes some ideas. Thank you, Mike -- View this message in context: http://forum.world.st/Monticello-review-web-application-tp4803443.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 3, 2015

Re: [Pharo-users] Cleaning code completition's namespace

by Laura Risani

I'm using v3, and the #Spotlight (class name) that comes with it. I didn't know about Spotter of v4 before your comment. I've just tried it, it could be handy for some specific situations, after i manually tweak its non-sense whiteness which somewhy escapes global theme defaults (lovely dark theme), i'll give it a try. Yet to the end of shortcuting accessing methods/classes i found Spotlight to be more direct and keystroke cheap. Saludos On Tue, Feb 3, 2015 at 1:28 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > Spotlight or Spotter? Which version of Pharo are you using? > > I ask because the old Spotlight should be using the same code completion > mechanism => it should appear/disappear from both at the same time... > > As for spotter, I don't have an answer now :) > > Saludos, > Guille > > El Tue Feb 03 2015 at 5:24:26 PM, Laura Risani <laura.risani(a)gmail.com> > escribiÃ³: > > Thank you all for your answers. >> >> Hi Guille , >> >> Nice solution! It worked perfectly for Code Completition! >> >> Yet the obsolete symbols (class names and selectors) keep showing in >> Spotlight, but i guess this is too implementation specific. I will step >> through its execution to try to find out how it works. >> >> Best, >> Laura >> >> >> >> On Mon, Feb 2, 2015 at 8:39 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Well yes, but GCs are happening all the time :). So the problem is that >>> someone is keeping a strong reference on the symbol. >>> >>> I tried the following: >>> >>> - create a method named #unusedUnexpectedMessage: That came up in the >>> auto completion, ok >>> - remove it: Still in auto completion >>> - force GC a looot: still in auto completion >>> >>> After chasing strong references I could clean up my image by doing: >>> >>> ChangeSet cleanUp: true. >>> RecentMessageList cleanUp. >>> 10 timesRepeat: [Smalltalk garbageCollect] >>> >>> First obvious thing: changesets and friends (lets also think about >>> nautilus history that may do that) could keep strong references on symbols. >>> >>> Then the question is if that is correct or not... To me the problem is >>> that the auto completion mechanism is pretty primitive and depends on all >>> existing symbols instead of <the subset of symbols that could be messages>. >>> >>> Guille >>> >>> El Mon Feb 02 2015 at 12:05:49 PM, Sven Van Caekenberghe <sven(a)stfx.eu> >>> escribiÃ³: >>> >>> But weak refs are only killed after GC, right ? >>>> >>>> And even then... >>>> >>>> > On 02 Feb 2015, at 12:03, Guillermo Polito <guillermopolito(a)gmail.com> >>>> wrote: >>>> > >>>> > It's the table that keeps the symbols and checks their uniqueness. >>>> > >>>> > but AFAIK the symbol table is weak. So probably it's the completion >>>> mechanism that is keeping extra references... >>>> > El Mon Feb 02 2015 at 11:52:28 AM, phil(a)highoctane.be < >>>> phil(a)highoctane.be> escribiÃ³: >>>> > Got the same problem here. >>>> > >>>> > Annoying when third parties have to do something in the environment >>>> as they are shown things that do not exist. >>>> > >>>> > Where to look? What's the symbol intern table? >>>> > >>>> > Phil >>>> > >>>> > >>>> > On Mon, Feb 2, 2015 at 11:44 AM, stepharo <stepharo(a)free.fr> wrote: >>>> > Probably by resetting the Symbol intern table. but no time to dive >>>> into it now. >>>> > Hi all, >>>> > >>>> > Code completition tools show class/method old names i've changed and >>>> no longer use. How can i remove all unused (occurring nowhere in source >>>> code) or unimplemented names? >>>> > >>>> > Best, >>>> > Laura >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> >>>> >>>> >>

Feb. 3, 2015

Re: [Pharo-users] Image growing size

by phil＠highoctane.be

Try to open monticello and select any repo, right click and clear the package cache. If you are using monticello that is. Also close all windows, open a workspace and do the 10 timesRepeat: [ Smalltalk garbageCollect]. HTH Phil Le 3 fÃ©vr. 2015 17:49, "Laura Risani" <laura.risani(a)gmail.com> a Ã©crit : > Hi all, > > The official image i've downloaded weighted about 40 MB. Now its size is > about 200 MB. What is the explanation? Is this normal or have i done > something wrong? > > I haven't been using globals, just downloaded and defined some packages. > The only over persistent thing i've done is to keep an instance variable in > some classes i wanted to have a unique instance. > > > Best, > Laura >

Feb. 3, 2015