- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] about the Pharo Catalog

by StÃ©phane Ducasse

On 19 Dec 2013, at 11:40, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Thu, Dec 12, 2013 at 9:59 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I really want to have an official catalog soon, so please add the missing metadata in your configurations. > > > please tell us what is a good example of a project so we can get > inspiration from it. Also, can I use Pillar syntax in the strings? Soup you can in the changes and keyclasses use pillar we could use it in the description too. Stef

Dec. 25, 2013

Re: [Pharo-dev] Critical ClassBuilder bug

by Marcus Denker

On 25 Dec 2013, at 20:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Guillermo > > do you have a test because we should really cover the classBuilder with such > scenario? > Yes, tests and the fix have been integrated last friday. > Stef > On 17 Dec 2013, at 16:59, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > >> Hi!! >> >> I started this afternoon to see a bug on class bindings on trait methods. This one: https://pharo.fogbugz.com/f/cases/11756/Reshaping-a-class-breaks-classBindi… >> >> Now, after playing and moving around that, I noticed that the problem is worse: >> >> 1)Create Class A. >> 2)Create method A>>m1. >> 3)Create method A>>m2. >> 4)reshape the class (e.g. add an inst var) >> >> Then: (A>>#m2) classBinding == (A>>#m3) classBinding ==> false!!! >> >> >> The problem is caused because the recompilation of the methods is taking place in a class that is not yet installed in its environment (the Smalltalk system dictionary in this case). The installation of the class takes part after the reshaping+the recompilation. Then, when the methods are compiled, the binding is not available for them and new bindings are created. >> >> Would someone with more idea on the new class builder give some advice? Cause I'm a bit lost in the new class builder code :) >> >> Tx, >> Guille >

Dec. 25, 2013

Re: [Pharo-dev] inspect slices

by StÃ©phane Ducasse

I would take an older image and do a merge like that you see the changes contained in the slices but this is not satisfactory. I would like to have a db storing all the changes and that we could do queries like show me the diff between the senders of foo in version 30399 and 30405 we are slowly getting there. Stef > On 18 Dec 2013, at 00:26, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > How can I find out the changes from a slice that is already included > > in the main image? > > So what I just do is to âmergeâ â> if empty, all changes are in. > > Marcus > > > This "all changes are in" case is where I want to know "what were these changes". > Or, how can we "undo" those changes made by the fix for issue 12288, for example. > Or can I open a version browser on all those changes from this slice. > > Nicolai >

Dec. 25, 2013

Re: [Pharo-dev] Easy issue to fix: 12063

by StÃ©phane Ducasse

> \That wasn't a report of a bug. It was just tracking my progress as I tried to understand it - but point taken - it is easier for reviewers if there is not too much irrelevant details. > btw, What do you think about Finder > Search > Source being inclusive of class comments? Yes it should be like that :) > Then I would not have ended up down that path. > > > btw2, Slice submitted for 12063, and also a new related one I found along the way > https://pharo.fogbugz.com/f/cases/12446 > > cheers -ben

Dec. 25, 2013

Re: [Pharo-dev] Critical ClassBuilder bug

by StÃ©phane Ducasse

Guillermo do you have a test because we should really cover the classBuilder with such scenario? Stef On 17 Dec 2013, at 16:59, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi!! > > I started this afternoon to see a bug on class bindings on trait methods. This one: https://pharo.fogbugz.com/f/cases/11756/Reshaping-a-class-breaks-classBindi… > > Now, after playing and moving around that, I noticed that the problem is worse: > > 1)Create Class A. > 2)Create method A>>m1. > 3)Create method A>>m2. > 4)reshape the class (e.g. add an inst var) > > Then: (A>>#m2) classBinding == (A>>#m3) classBinding ==> false!!! > > > The problem is caused because the recompilation of the methods is taking place in a class that is not yet installed in its environment (the Smalltalk system dictionary in this case). The installation of the class takes part after the reshaping+the recompilation. Then, when the methods are compiled, the binding is not available for them and new bindings are created. > > Would someone with more idea on the new class builder give some advice? Cause I'm a bit lost in the new class builder code :) > > Tx, > Guille

Dec. 25, 2013

Re: [Pharo-dev] Class comment versioning

by Marcus Denker

On 25 Dec 2013, at 18:09, Nicolai Hess <nicolaihess(a)web.de> wrote: > Are different versions of class comments stored somewhere? > > Looking at RGCommentDefinition, class comments can have > a timestamp. But I couldn't found a way to browse class comment versions. > There is a but right nowâ¦ https://pharo.fogbugz.com/f/cases/7315/Class-comments-have-no-timestamp The whole code that realised the changes+source stuff is quite old and hard to understandâ¦ so itâs easy to introduce bugs, as happened here quiet a while ago. Marcus

Dec. 25, 2013

Re: [Pharo-dev] [Moose-dev] Re: Activity Diagram

by Marcus Denker

On 25 Dec 2013, at 19:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes indeed then in that case I would really try to get ConnectorMorph working in pharo. > I can send you a drop box with a working version in 3.9 > Keep in mind that Connectors where a quite huge and complex (and intrusive) (yet *Very very* coolâ¦) piece of workâ¦ getting them to work in Pharo will be a challenge. In the end, I think the largest problem of connectors always was that they here not merged with Morphic *for real* (while cleaning up both), as they show very much the real power of Morphic. I did start to integrate the hooks + enhancements in Squeak 3.9, but in the end it turned out to be quite a hack in some parts and thus just increased the complexity of Morphicâ¦ Marcus

Dec. 25, 2013

Re: [Pharo-dev] Relation tower is coming for Roassal

by StÃ©phane Ducasse

this is really nice What I would like is if we can have a relation to another element on the left and that such elements are placed I would really like to have a visualization that I could use to display procedural code and their invocations. procedure def foo calling zork procedure def bar call foo procedure def zork and be able to see that foo calls zork Stef > Hi! > > A new builder for Roassal is comingâ¦ The goal of Relation tower is to easily visualize relations between group of elements. We had the inspiration from the following website http://peoplemov.in/#! > > Here are some screenshots: > https://www.facebook.com/media/set/?set=a.559114290841839.1073741837.340543… > > If you like these screenshots, then you know where the like button is :-) > > We will have this visualization on the web, thanks to our smooth and nice Pharo2Amber migration process. > > Any idea on how to extend/apply Relation tower? Any set of data you want us to play with? Your data? > Feedback are very welcome! > > Cheers, > Ricardo & Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >

Dec. 25, 2013

Re: [Pharo-dev] Class comment versioning

by StÃ©phane Ducasse

Normally they should be stored somewhere in the change file but may be we got a bug somewhere. Now I really hope that Epicea will replace the changesorter model. Stef > Are different versions of class comments stored somewhere? > > Looking at RGCommentDefinition, class comments can have > a timestamp. But I couldn't found a way to browse class comment versions. > > regards > Nicolai

Dec. 25, 2013

Re: [Pharo-dev] Nautilus as default/only Systembrowser for pharo3

by StÃ©phane Ducasse

> I understand, lack of time/manpower. But if we have the time, to introduce new or experimental things, > we should focus to have stable tools. Believe me that I completely agree with you :). Iâm always trying to get stable and better tools. What are the problems that you have? Because I work daily with Nautilus. Now you should realise that Ben did Nautilus because he was fed up with the old browser and he was a third and four year student. Then he built nautilus so that we can remove the really old code StringHolder and subclasses from the system. Then from this experience we saw that building tools did not scale so this is why we worked on Spec. And now Spec went from version 1 to version 2 and now we will be able to rewrite Nautilus again. Now to complete the story: we worked one year to clean and make a solid version of package but protocols were so deep into the system that we had to fix Nautilus and esteban rewrote a part in a hurry. But again Esteban is not payed for that and some of the glitches we will be fixed when we find them and fix them. Stef

Dec. 25, 2013