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

Re: [Pharo-dev] About inspectors

by Yuriy Tymchuk

Yes, I know. And this is sad :( On 07 Mar 2014, at 18:45, Tudor Girba <tudor(a)tudorgirba.com> wrote: > We cannot do that because they are based on two radically different technologies. > > Doru > > > On Fri, Mar 7, 2014 at 4:43 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone. > > This day Iâve attended Moose dojo and Iâm pretty impressed with the possibilities of GTInspector. The one thing that Iâve noticed is that both GTInspactor and EyeInspector support custom inspections for objects. Iâm wandering if we can come up with a common protocol to give an object specific infector view, and not develop a separate thing for each inspector. > > Uko > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

March 7, 2014

Re: [Pharo-dev] TWM and 3.0: icons/themes, UpdatingMenuMorph

by Sean P. DeNigris

philippeback wrote > I am trying to get TWM to work in 3.0 > ... > Where Updating MenuMorph appears to be gone in 3.0 > > What am I supposed to use as a replacement? Glad you're working on it. I got stuck in the same place. The icon problem IIRC occurs in two TWM classes. Might I suggest (which you may already have done) for the class with the many such references (the bar I think), you abstract via "#icons ^ Smalltalk ui" instead of sprinkling "Smalltalk ui xyzIcon" everywhere and having to repeat the work for Pharo #.0. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TWM-and-3-0-icons-themes-UpdatingMenuMorph-tp4747979p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 7, 2014

12911 Tests-failing-in-fresh-image-MetacelloRepositorySqueakCommonTestCase

by btc＠openinworld.com

Can someone with a Mac review... https://pharo.fogbugz.com/f/cases/edit/12911/Tests-failing-in-fresh-image-M… Its low priority but also simple - just an update for three tests to deal with difference on Windows platform . cheers -ben

March 7, 2014

Re: [Pharo-dev] About inspectors

by Tudor Girba

We cannot do that because they are based on two radically different technologies. Doru On Fri, Mar 7, 2014 at 4:43 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi everyone. > > This day I've attended Moose dojo and I'm pretty impressed with the > possibilities of GTInspector. The one thing that I've noticed is that both > GTInspactor and EyeInspector support custom inspections for objects. I'm > wandering if we can come up with a common protocol to give an object > specific infector view, and not develop a separate thing for each inspector. > > Uko > -- www.tudorgirba.com "Every thing has its own flow"

March 7, 2014

About inspectors

by Yuriy Tymchuk

Hi everyone. This day Iâve attended Moose dojo and Iâm pretty impressed with the possibilities of GTInspector. The one thing that Iâve noticed is that both GTInspactor and EyeInspector support custom inspections for objects. Iâm wandering if we can come up with a common protocol to give an object specific infector view, and not develop a separate thing for each inspector. Uko

March 7, 2014

Re: [Pharo-dev] Support for git in Pharo

by Goubier Thierry

Le 07/03/2014 09:52, Max Leske a Ã©crit : >> - And be able to rebuild package version history via the VCS history, as I do now in gitfiletree. > > Yes, that is something that should be possible. > > To be honest, those thoughts are a bit too far in the future at the moment. First, I want to have Git plumbing running, then Iâll see about the rest. That was certainly the advantage of my solution: easy plumbing, left me the time to: use it, and plan good uses of it. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 7, 2014

Re: [Pharo-dev] Support for git in Pharo

by Dale Henrichs

Frank, Yeah, for browsing Smalltalk repos on github itself, I figured that an Amber app would be the way to go ...then you could have a "real" code browser with senders implementers, etc.... and the same code could run in a pharo image to browse unloaded repos from github or disk ... Just a simple matter of putting tooling in place:) Dale On Fri, Mar 7, 2014 at 1:34 AM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 6 March 2014 20:18, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > Stephan, > > > > The reason that we have the granularity of a file per method is to > leverage > > git's history/tracking facilities on a per method basis. > > > > At this level of granularity, you can move a method around in the package > > structure and git will maintain the method modification history because > git > > treats these as a file rename and git is very good at tracking file > renames > > ... > > > > So you can use "blame" to view a line by line history of the method > > modifications ... > > > > If one starts clumping methods into files, then you lose all method > history > > when it moves from one clump to another ... > > Another huge strength with versioning per method (and one of the main > reasons I don't complain too loudly about the uselessness of GitHub in > viewing code when doing this) is also that you never ever have to try > merge two methods that two different commits have put in the same > place, and the diff algorithm has decided to _interleave_ the methods. > Fun times! > > frank > > > Dale > > > > > > > > On Thu, Mar 6, 2014 at 9:03 AM, Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> > >> Max wrote > >> >In my opinion there are other factors, like readability, maintenance > etc, > >> > that are maybe more important than speed. > >> > >> I'm not totally convinced. The readability from the outside is limited > by > >> having one file per method. > >> Mainstream tooling assumes one file per class. The emails from github to > >> this list are a good example > >> of the usability problems that leads to. I don't want to suggest > switching > >> to a larger granularity, as that > >> leads to another set of problems. > >> > >> My point was more if we could mostly avoid the source view, and directly > >> work with the archive. > >> Why is working with single files fastest? > >> > >> Stephan > > > > > >

March 7, 2014

Re: [Pharo-dev] What happened with petitmarkdown?

by Stephan Eggermont

ClÃ©ment wrote >Camillo moved all his repo on github and deleted the ones from smalltalkhub. Hmm. I strongly prefer immutability for source code repositories. And a link to older/newer repos. Stephan

March 7, 2014

Re: [Pharo-dev] What happened with petitmarkdown?

by ClÃ©ment Bera

Hey, Camillo moved all his repo on github and deleted the ones from smalltalkhub. 2014-03-07 8:10 GMT+01:00 Damien Cassou <damien.cassou(a)gmail.com>: > Try on github > On Mar 6, 2014 1:27 PM, "Stephan Eggermont" <stephan(a)stack.nl> wrote: > >> Camillo, >> >> While fixing some ci builds, I noticed that at least some of your >> smalltalkhub >> repositories are empty (petitmarkdown, ast-interpreter). What happened >> with the code? ast-interpreter I could find back, but petitmarkdown not. >> >> Stephan >> >> >>

March 7, 2014

[pharo-project/pharo-core] b3065f: 30792

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: b3065f4660c4d171cd5b87f426cad38658f3ff64 https://github.com/pharo-project/pharo-core/commit/b3065f4660c4d171cd5b87f4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-03-07 (Fri, 07 Mar 2014) Changed paths: A OpalCompiler-Core.package/IRInterpreter.class/instance/instructions/storeInstVar_.st M OpalCompiler-Core.package/IRMethod.class/instance/optimizing/removeEmptyStart.st A OpalCompiler-Core.package/IRPrinter.class/instance/instructions/storeInstVar_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script445.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30792.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30792 13053 Sync image with repo https://pharo.fogbugz.com/f/cases/13053 13002 StoreInstVar: is missing in IRPrinter https://pharo.fogbugz.com/f/cases/13002 13003 Opal cannot optimize twice an IRMethod https://pharo.fogbugz.com/f/cases/13003 http://files.pharo.org/image/30/30792.zip

March 7, 2014