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

Re: [Pharo-project] MVP
by Marcus Denker March 5, 2012

March 5, 2012

On Mar 5, 2012, at 6:45 PM, Schwab,Wilhelm K wrote: > I can use 1.4 to look at the code. Once shout works in the browsers, I might make the switch anyway. > In Pharo 1.4 as downloaded here: https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifac… Shout is working in the Browsers. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] small thoughts... system browser to show super methods & wide debugger
by Marcus Denker March 5, 2012

March 5, 2012

On Mar 5, 2012, at 11:33 AM, Ben Coman wrote: > > Just sharing some small thoughts as they cross my mind on the chance the are of any interest. Not necessarily looking for any response or action. > > 1. In the System Browser when viewing a method, this might include an expandable list of overridden methods. Beneath the code of the current method being viewed each 'super' method would be listed with an expandable '+' symbol. I have attached a mock up [1] showing all expanded but the default might be the collapsed state. > > 2. The debugger lists instance and temporary variables to be inspected, but not every object that 'passes through' the method being executed is held in a variable. More often messages are chained together such that to inspect the object returned from the middle of this chain you need to select that bit of the code and choose to inspect it again. However there may be side-effects of executing that a second time so you are not guaranteed to end up looking at the object actually encountered by the execution of the method. > What would be interesting would be if in certain circumstances every object returned by every message in a method was held to be inspected. This might take the form of hovering or right-clicking on any message an choosing something like 'inspect context'. The circumstances this might be turned on for could be: > a. globally > b. ongoing execution from within debugger > c. certain methods / classes / categories. > > 3. With screens getting much bigger, perhaps the debugger could have an option to show code from previous calls back to a certain level. I have attached a mock up [2]. Even though this image shows using a lot of vertical space, this would be scrolled. Ultimately it would be horizontal space required as the code steps in, but todays wide screens match this even better than those a few years ago. Note the yellow highlighted line in the top pane which can position how far back you look. > I like the debugger idea! Especially combined with mouse-over infos (show the value if var in a pop-up when the mouse it over it), this should allow for a very quick way to understand code... Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] [update 1.4] #14378
by Marcus Denker March 5, 2012

March 5, 2012

14378 ----- Issue 5436: Move DialogItemsChooser to Finder (its only user) http://code.google.com/p/pharo/issues/detail?id=5436 Issue 5435: clean up unusedBlocks tests http://code.google.com/p/pharo/issues/detail?id=5435 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.4] #14375
by Marcus Denker March 5, 2012

March 5, 2012

14375 ----- Issue 5290: Cleanup Startup Error Handling http://code.google.com/p/pharo/issues/detail?id=5290 Camillo Bruni. - provide a more readable log output on stdout - properly handle the -interactive -headless switch - reuse existing code when using scripts (CodeLoader) - cleanup the logging in SmalltalkImage - added exit code (this was loaded as a hand-orderd .cs... next update will sync with the repository) Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Fwd: Showing the setUp method in Nautilus
by Alexandre Bergel March 5, 2012

March 5, 2012

It may interest some of you. Alexandre Begin forwarded message: > From: Alexandre Bergel <alexandre.bergel(a)me.com> > Subject: Showing the setUp method in Nautilus > Date: 5 March 2012 08:52:39 GMT-03:00 > To: benjamin Van Ryseghem <benjamin.vanryseghem(a)gmail.com> > > Hi! > > I worked on a new method item action to easily show the setUp method of a testCase. This helps reduce the amount of clicks and context switching when one wants to know what the setUp method is about while writing a test method. > > I think it is a good candidate for being included in Nautilus. > Ben, if you agree with this, I can to commit in the Nautilus rep and produce a new version of the configuration. How does that sound? > > Question: how to associate a shortcut to an action? > > Side comment: it would be a good move to adopt a class hierarchy a la OB to define commands. Defining all the commands in NautilusUI does not scale and simply does not work for non trivial command. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 267 - Still Unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 5, 2012

March 5, 2012

1 0

[Pharo-project] [TODO] Issue tracker status
by Marcus Denker March 5, 2012

March 5, 2012

Issues all together: 439 http://code.google.com/p/pharo/issues/list?can=2 Issues tagged 1.3: 9 (3 of which are tagged 1.4, too) http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Issues tagged 1.4: 39 (of which 1 toInclude, 11 to review) http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] MVP
by Marcus Denker March 5, 2012

March 5, 2012

On Mar 5, 2012, at 10:03 AM, Schwab,Wilhelm K wrote: > Stef, > > Thanks for the code! #stable does some things on 1.4, but I still got nowhere with 1.3. The big thing keeping me off of 1.4 is shout in the browsers - I *really* like syntax highlighting. Isn't Shout enabled in 1.4? > In fairness, I have not looked at 1.4 in a week or so, so maybe that's been fixed. However, I can certainly run it to play around with spec. > > Even on 1.4, I got a DNU over groups; this time I had to add the noop to OB, which is apparently the default in 1.4?? In the past you have shown to want very stable, out of the box usable, "I can not do anything wrong" kind of software. Does it then make sense to use Nautilus, which is in active development? Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] small thoughts... system browser to show super methods & wide debugger
by Ben Coman March 5, 2012

March 5, 2012

Just sharing some small thoughts as they cross my mind on the chance the are of any interest. Not necessarily looking for any response or action. 1. In the System Browser when viewing a method, this might include an expandable list of overridden methods. Beneath the code of the current method being viewed each 'super' method would be listed with an expandable '+' symbol. I have attached a mock up [1] showing all expanded but the default might be the collapsed state. 2. The debugger lists instance and temporary variables to be inspected, but not every object that 'passes through' the method being executed is held in a variable. More often messages are chained together such that to inspect the object returned from the middle of this chain you need to select that bit of the code and choose to inspect it again. However there may be side-effects of executing that a second time so you are not guaranteed to end up looking at the object actually encountered by the execution of the method. What would be interesting would be if in certain circumstances every object returned by every message in a method was held to be inspected. This might take the form of hovering or right-clicking on any message an choosing something like 'inspect context'. The circumstances this might be turned on for could be: a. globally b. ongoing execution from within debugger c. certain methods / classes / categories. 3. With screens getting much bigger, perhaps the debugger could have an option to show code from previous calls back to a certain level. I have attached a mock up [2]. Even though this image shows using a lot of vertical space, this would be scrolled. Ultimately it would be horizontal space required as the code steps in, but todays wide screens match this even better than those a few years ago. Note the yellow highlighted line in the top pane which can position how far back you look. cheers, -ben [1] SystemBrowser - showing-overriden-methods.png [2] Debugger - expanded code display.png

2 1

[Pharo-project] Pharo 1.4 Tests-Mac - Build # 254 - Still unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 5, 2012

March 5, 2012

1 1