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

Re: [Pharo-project] [ANN]: Vim Shortcuts for Nautilus (Proof-of-concept)

by Sean P. DeNigris

Version 0.2 (proof-of-concept)... Normal (ESC)/insert (i) toggle working. Still only one normal mode shortcut (dd), but they should mostly be easy to add (see below)... * Disable toggling text cursor with mode. Paragraph will have to be refactored to allow per-Morph cursor styles * Fix normal/insert mode toggling. Now works per-morph The only normal mode shortcut so far is dd (delete line), but it should be simple to add most of them. The only ones I'm not sure about are multiples, like 3dd. I'm not sure if you can do regex shortcuts with Keymapping (e.g. '\d*' asRegexShortcut, $d asShortcut, $d asShortcut) * Load Pharo Slice 6300, if not present Sean P. DeNigris wrote > > In Pharo 2.0: > > Gofer new > url: 'http://ss3.gemstone.com/ss/VimPharo'; > package: 'ConfigurationOfVimPharo'; > load > > ConfigurationOfVimPharo project development load. > 1. open a Nautilus browser 2. In the code pane, press escape to enter Vim command mode 3. Press the d key twice to delete the current line 4. Press the i key and you will be back in insert mode (the usual Pharo mode) -- View this message in context: http://forum.world.st/ANN-Vim-Shortcuts-for-Nautilus-Proof-of-concept-tp463… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 11, 2012

Re: [Pharo-project] Versionner: Committing a config commits twice

by Juan Pablo Sandoval Alcocer

Hi, I am working in this issue, I will notify you when it's fixed. Thanks, Juan Pablo 2012/7/7 Sean P. DeNigris <sean(a)clipperadams.com> > Versionner is getting *really* cool!! > > I found a bug: > http://ss3.gemstone.com/ss/Versionner.html/Issues > Issue 1: Committing a config commits twice > > 1. In Pharo 2.0, "ConfigurationOfVersionner project development > load:#('Core' 'Spec')." > 2. Create new config for a package > 3. Click commit > > It saves it, but then is shows it dirty again and asks about a new version > number. Even though I cancelled, it saved the config to the repo (in this > case http://ss3.gemstone.com/ss/VimPharo) again: > ConfigurationOfVimPharo-SeanDeNigris.1.mcz > ConfigurationOfVimPharo-SeanDeNigris.2.mcz > > -- > View this message in context: > http://forum.world.st/Versionner-Committing-a-config-commits-twice-tp463898… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Juampi

July 11, 2012

Re: [Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by Dale Henrichs

Ah yes ... RPackage was trying to send an odd message at one point ... that sounds right... Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, July 11, 2012 9:58:04 AM | Subject: Re: [Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping? | | The problem we face right now are related to RPackage | Somehow the registration mechanism for system events (classes|methods | added|removed|modified) | got mixed up. | | Eventually this leads to some warnings when removing methods :/ | I thought I fixed it this morning but I was wrong :D | | | | On 2012-07-11, at 18:54, Dale Henrichs wrote: | | > I was trying to work with Pharo2.0 the other day and ran into weird | > modified package issues ... Metacello-Base was involved ... I was | > actually trying to get something else accomplished and don't have | > time to debug Pharo2.0 issues, since they are not likely to be | > directly caused by Metacello... | > | > Dale | > ----- Original Message ----- | > | From: "DeNigris Sean" <sean(a)clipperadams.com> | > | To: metacello(a)googlegroups.com, | > | pharo-project(a)lists.gforge.inria.fr | > | Sent: Wednesday, July 11, 2012 9:47:21 AM | > | Subject: [Metacello] Did Pharo 2.0 Update #20200 break Metacello | > | bootstrapping? | > | | > | (Posting to Metacello and Pharo-project lists) | > | | > | Metacello bootstraps in #20199, but not #20200, #20201, or | > | #20202. | > | | > | Try: | > | Gofer new | > | url: 'http://ss3.gemstone.com/ss/Versionner'; | > | package: 'ConfigurationOfVersionner'; | > | load. | > | | > | (Smalltalk at: #ConfigurationOfVersionner) project development | > | load:#('Core' 'Spec'). | > | | > | When the dialog pops up about loading a package with unsaved | > | changes, | > | if you choose merge and keep the current version for all the | > | removed | > | classes and methods, it bootstraps. If you "Load" instead of | > | Merge, | > | it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" | > | | > | Sean | > | | |

July 11, 2012

Re: [Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by Camillo Bruni

The problem we face right now are related to RPackage Somehow the registration mechanism for system events (classes|methods added|removed|modified) got mixed up. Eventually this leads to some warnings when removing methods :/ I thought I fixed it this morning but I was wrong :D On 2012-07-11, at 18:54, Dale Henrichs wrote: > I was trying to work with Pharo2.0 the other day and ran into weird modified package issues ... Metacello-Base was involved ... I was actually trying to get something else accomplished and don't have time to debug Pharo2.0 issues, since they are not likely to be directly caused by Metacello... > > Dale > ----- Original Message ----- > | From: "DeNigris Sean" <sean(a)clipperadams.com> > | To: metacello(a)googlegroups.com, pharo-project(a)lists.gforge.inria.fr > | Sent: Wednesday, July 11, 2012 9:47:21 AM > | Subject: [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping? > | > | (Posting to Metacello and Pharo-project lists) > | > | Metacello bootstraps in #20199, but not #20200, #20201, or #20202. > | > | Try: > | Gofer new > | url: 'http://ss3.gemstone.com/ss/Versionner'; > | package: 'ConfigurationOfVersionner'; > | load. > | > | (Smalltalk at: #ConfigurationOfVersionner) project development > | load:#('Core' 'Spec'). > | > | When the dialog pops up about loading a package with unsaved changes, > | if you choose merge and keep the current version for all the removed > | classes and methods, it bootstraps. If you "Load" instead of Merge, > | it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" > | > | Sean >

July 11, 2012

[Pharo-project] Visualizing Legacy at SPA conference

by Stephan Eggermont

Last week Willem and I presented a workshop Visualizing Legacy, using MOOSE, at SPA2012 in London. In a 150 minutes workshop we showed how to use glamour and mondrian to visualize the github repository data from 4 ruby projects and the code used for these analysis and the workshop itself. The exercises work toward the creation of a glamour browser with a mondrian pane showing custom visualizations not achievable by more static tools like Sonar. The answering of specific questions that arise during the analysis of the data show the strengths of the MOOSE toolchain. We started by showing some of the work Diego and I have done for the conversion of the data of a cobol ERP system to a modern ERP system. By creating (at least) one browser/visualization a day, we were able to make the subject matter expert, a very busy senior executive of the company, steer the conversion process to her satisfaction. By treating her as the bottleneck, and making it as easy as possible for her to see where we were, and what we still had to do/understand, she could effectively prioritize and decide. Then we asked the participants what they expected/wanted from visualizing their legacy code. The answers were a mix of things that tools like Sonar can easily provide, with very specific questions that need a programmable tool like MOOSE. As we expected, it took most of the about 14 participants quite a lot of effort and time to get to grips with the smalltalk environment to work in. So much so, that some asked for a separate smalltalk workshop to do before this one, or a larger timeslot for this workshop. The few participants experienced with Smalltalk had been using VW/VA and also had some problems finding their way around. In the end, the participants who managed to just follow the exercises achieved the goals without too much interventions needed. Inspired by ProfStef, we build a custom glamour browser for the workshop. The code can be found in the SpaTutorial project on ss3. (The ConfigurationOfâ¦ is no Metacello) http://ss3.gemstone.com/ss/SpaTutorial It is split in a generic part, allowing you to create tutorials, and a specific part for this workshop. We might want to extend it so the exercises can be done entirely in the custom browser. That might help the smalltalk newbies. Now the participants needed two class browsers in addition to the tutorial, one to edit the exercise code, and one to look at the domain model. We believe the learning curve can be flattened by extending the SpaTutorial browser so it can save code, and extracting some methods so the tutorial browser only shows the bits participants have to work on right now, gradually expanding the scope as it progresses. It uses the data collected for the SPA2011 great egg-race. http://chatley.com/posts/06-20-2011/spa-great-egg-race/ Git commit data was collected by Michael Feathers from four ruby projects, a.o. active_merchant and diaspora. After my holidays I'll put the data in a zip in https://github.com/StephanEggermont/repodepot-ruby For the 150 minute timeslot we focused on glamour and mondrian, although we also prepared an eyesee exercise. Next time we might switch the exercises around - mondrian looks more glamourous than glamour ;). A longer version may also be in the works if we can run it somewhere. It was only after the mondrian exercise that participants could start playing with the data on their own. Participants indicated they associatied mondrian more with visualization than glamour. Stephan Eggermont & Willem van den Ende

July 11, 2012

Re: [Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by Dale Henrichs

I was trying to work with Pharo2.0 the other day and ran into weird modified package issues ... Metacello-Base was involved ... I was actually trying to get something else accomplished and don't have time to debug Pharo2.0 issues, since they are not likely to be directly caused by Metacello... Dale ----- Original Message ----- | From: "DeNigris Sean" <sean(a)clipperadams.com> | To: metacello(a)googlegroups.com, pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, July 11, 2012 9:47:21 AM | Subject: [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping? | | (Posting to Metacello and Pharo-project lists) | | Metacello bootstraps in #20199, but not #20200, #20201, or #20202. | | Try: | Gofer new | url: 'http://ss3.gemstone.com/ss/Versionner'; | package: 'ConfigurationOfVersionner'; | load. | | (Smalltalk at: #ConfigurationOfVersionner) project development | load:#('Core' 'Spec'). | | When the dialog pops up about loading a package with unsaved changes, | if you choose merge and keep the current version for all the removed | classes and methods, it bootstraps. If you "Load" instead of Merge, | it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" | | Sean

July 11, 2012

[Pharo-project] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

by DeNigris Sean

(Posting to Metacello and Pharo-project lists) Metacello bootstraps in #20199, but not #20200, #20201, or #20202. Try: Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) project development load:#('Core' 'Spec'). When the dialog pops up about loading a package with unsaved changes, if you choose merge and keep the current version for all the removed classes and methods, it bootstraps. If you "Load" instead of Merge, it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:" Sean

July 11, 2012

[Pharo-project] [Jenkins] Work on Networking tonight and tomorrow night

by Marcus Denker

Hi, Because of networking work (physical) at the building, Jenkins can be unreachable tonight (11) and tomorrow (12th). Local time 18 onwards, downtime might extend to 9am the next morning. Mailinglist, gforge and website will not be affected. Marcus -- Marcus Denker -- http://marcusdenker.de

July 11, 2012

[Pharo-project] Issue 6340: [BUG]: Browsing changes on a slice

by Sean P. DeNigris

Type-Bug Milestone-2.0 Pharo2.0a Latest update: #20202 1. Change a package required by a slice: Example: Gofer it url: 'http://ss3.gemstone.com/ss/PharoInbox'; version: 'SLICE-Issue-6300-Detach-keymaping-shortcuts-SeanDeNigris.2'; load. KMFactory class compile: 'keymapContainer ^ KMRepository default.' 2. In an MC Browser, select the changed package (Keymapping-Core in the example), and click "Changes" You will see only the changes you made in step 1 3. In the MC Browser, select the Slice package and click "Changes" 4. Close the changes browser 5. Repeat step 2 Now you will see a huge change list, where most things have not in fact been changed -- View this message in context: http://forum.world.st/Issue-6340-BUG-Browsing-changes-on-a-slice-tp4639553.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 11, 2012

Re: [Pharo-project] [Jenkins] New issue status for real problems.

by Henrik Sperre Johansen

On 11.07.2012 15:41, Camillo Bruni wrote: > On 2012-07-11, at 15:28, Henrik Sperre Johansen wrote: > >> On 11.07.2012 15:14, Camillo Bruni wrote: >>> On 2012-07-11, at 15:02, StÃ©phane Ducasse wrote: >>> >>>> On Jul 11, 2012, at 11:05 AM, Camillo Bruni wrote: >>>> >>>>> That was a weird bug... but I fixed it. >>>>> We need a Debugger for the announcement system! >>>> What do you mean? >>>> Because what I know is that debugging the test of announcement can be a pain because registrations are done in another world. >>> the problem is, that on:fork: and co are used in the WeakMessageSends >>> and thus lose the complete reference to where they came from.. >>> >>>>> I tried to refactoring a bit so you can get a clue what's going on when stepping through with the debuggerâ¦ >>>> What you describe is more related to the state of the debugger and yes it was on our todo to fix the debugger. >>> no no, when you do SubscriptionRegistry >> #deliver: >>> you create a complete copy of the subscriptions collection. >>> This is not very useful, since you can filter them while copying => less items to copy, easier to inspect >> Not threadsafely. > ? this has absolutely nothing to do with thread safeness.... You're right, I'd forgotten exactly what we'd done :) In my mind it still read something like: deliver: anAnnouncement subscriptions copy do: [:each | each deliver: anAnnouncement ], relying on atomicity implicit through copy primitives rather than explicitly with a mutex. Filtering with the standard collection methods leaves you with an IdentitySet though, so you'd have to either convert it afterwards, change the curtailing code in deliver:to: (which uses Sequenceable protocol). Either probably has some tradeoff in readability/performance compared to the current delivery. Cheers, Henry

July 11, 2012