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

Re: [Pharo-project] ohloh stats filling up

by phil＠highoctane.be

Sweet! 2012/7/12 Camillo Bruni <camillobruni(a)gmail.com> > all new pharo changes are logged to a git repos here: > https://github.com/PharoProject/pharo-core > > The older history has been: > https://github.com/pharogenesis/pharogenesis > > You can find all the repos under the settings of the ohloh project :) > > On 2012-07-12, at 10:53, phil(a)highoctane.be wrote: > > How did you managed to get the lines of Smalltalk counted by oloh? > > > > Phil > > > > 2012/7/12 Camillo Bruni <camillobruni(a)gmail.com> > > > >> done! > >> > >> CI is linked under "Other" > >> > >> On 2012-07-12, at 01:51, Bernardo Ezequiel Contreras wrote: > >> > >>> 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 12, 2012

Re: [Pharo-project] ohloh stats filling up

by Camillo Bruni

all new pharo changes are logged to a git repos here: https://github.com/PharoProject/pharo-core The older history has been: https://github.com/pharogenesis/pharogenesis You can find all the repos under the settings of the ohloh project :) On 2012-07-12, at 10:53, phil(a)highoctane.be wrote: > How did you managed to get the lines of Smalltalk counted by oloh? > > Phil > > 2012/7/12 Camillo Bruni <camillobruni(a)gmail.com> > >> done! >> >> CI is linked under "Other" >> >> On 2012-07-12, at 01:51, Bernardo Ezequiel Contreras wrote: >> >>> 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 12, 2012

Re: [Pharo-project] ohloh stats filling up

by phil＠highoctane.be

How did you managed to get the lines of Smalltalk counted by oloh? Phil 2012/7/12 Camillo Bruni <camillobruni(a)gmail.com> > done! > > CI is linked under "Other" > > On 2012-07-12, at 01:51, Bernardo Ezequiel Contreras wrote: > > > 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 12, 2012

Re: [Pharo-project] ohloh stats filling up

by Camillo Bruni

done! CI is linked under "Other" On 2012-07-12, at 01:51, Bernardo Ezequiel Contreras wrote: > 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 12, 2012

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

by Camillo Bruni

On 2012-07-12, at 09:52, Henrik Sperre Johansen wrote: > 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). " actually that's bug I introduced, but the stuff currently failing is still due to double subscriptions of the RPackageOrganizer > 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. Indeed my bad :P. I quickly wrote a decent implementation that does not have to copy around stuff in the case of ifCurtailed...

July 12, 2012

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