- Pharo-dev - lists.pharo.org

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

by Henrik Sperre Johansen

On 11.07.2012 18:58, Camillo Bruni wrote: > 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 I wrote yesterday: "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). " copyAfter: is exactly that protocol, so you'd probably want to re-review the Announcement changes in addition to the fact that RPackage ends up in that code path in the first place. Cheers, Henry

July 12, 2012

Re: [Pharo-project] making Apache serve .mcz files in the proper mode

by Friedrich Dominicus

Thanks I will try it with you Additon to the Directory of the repositories. Friedrich

July 12, 2012

Re: [Pharo-project] ohloh stats filling up

by Bernardo Ezequiel Contreras

Camilo could you add the url to jenkins? thanks On Wed, Jul 11, 2012 at 8:27 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > slowly slowly we get a decent overview of the efforts made for pharo :) > > https://www.ohloh.net/p/pharo > > now we have all our major sources listed on that website and we get quite > a decent 200k lines of code :P > > best > cami > > -- Bernardo E.C.

July 11, 2012

[Pharo-project] ohloh stats filling up

by Camillo Bruni

slowly slowly we get a decent overview of the efforts made for pharo :) https://www.ohloh.net/p/pharo now we have all our major sources listed on that website and we get quite a decent 200k lines of code :P best cami

July 11, 2012

Re: [Pharo-project] Visualizing Legacy at SPA conference

by Tudor Girba

Great work! Having all this run in 150 min is quite an achievement. Cheers, Doru On 11 Jul 2012, at 18:57, Stephan Eggermont wrote: > 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 -- www.tudorgirba.com If you can't say why something is relevant, it probably isn't.

July 11, 2012

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