June 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

by Dale Henrichs

SETT was create based on our understanding (GemTalk Systems) of what the tonel disk format was _supposed_ to be and I think that Pharo has departed from somewhat from what was understood to be the format. I've had similar problems trying to use filetree repositories with Iceberg that have been readable by the old Monticello/Filetree readers for years [1] ... and are readable when loaded through the Monticello Browser, but not readable when using Iceberg ... One of these days, there needs to be agreement as to what the actual disk format of tonel and filetree repositories is going to be/has been and then stick to them, otherwise these problems are going to continue to plague us. Dale [1] https://github.com/pharo-vcs/iceberg/issues/1239 On 6/18/19 6:40 AM, Esteban Maringolo wrote: > Hi Guillermo, > > Your workaround effectively solved my issue. > > About the tonel format, in the .properties file at the sources > directory there was such setting: > https://github.com/eMaringolo/rbac/blob/9279f22ef5fd1c4149090b5b39a6afa143a… > > > But the .project file was missing at the root of the repository. So > maybe it is a mix of both conditions. > > In any case, I'm glad the workaround works, and that it helped > spotting a bug. > > Thank you! > > > Esteban A. Maringolo > > > On Tue, Jun 18, 2019 at 4:35 AM Guillermo Polito > <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > Iâve created an issue: > > https://github.com/pharo-vcs/iceberg/issues/1251 > >> El 18 jun 2019, a las 9:30, Guillermo Polito >> <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> >> escribiÃ³: >> >> Hi Esteban, >> >> It seems like a bug in Iceberg. If you click on debug, youâll see >> that although youâve said the project is in tonel format, itâs >> trying to use a Filetree reader >> >> <PastedGraphic-2.png> >> >> This is due to some missing metadata in the commit (iceberg is >> relying on commit information there and not working copy >> information). >> >> There is however a simple workaround. If you click in the commit >> button youâll see that Iceberg tries to create and commit the >> missing files: >> >> <PastedGraphic-3.png> >> >> If you commit those files, then youâll be able to load your packages. >> >> Guille >> >> >>> El 18 jun 2019, a las 2:34, Esteban Maringolo >>> <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> escribiÃ³: >>> >>> Hi, >>> >>> I'm trying to load a package from a Tonel repository[1] that was >>> created using SETT[2]. >>> >>> The structure seems fine, but when I try to load a package, I'm >>> getting the message saying that there is no version for the >>> package in the current commit (which seems wrong at least to the >>> naked eye). >>> >>> Eg. >>> <image.png> >>> >>> Any idea of how to fix it? >>> >>> Regards! >>> >>> [1] https://github.com/eMaringolo/rbac/tree/master/sources/ >>> [2] https://github.com/gemtalk/sett >>> >>> >>> >>> Esteban A. Maringolo >> >

June 18, 2019

Question: anyone using NOCompletion setting?

by Marcus Denker

Hi, There are two completion modes currently: the standard one and the NOControler setting the NO option has the idea that it sorts ânewlyâ compiled selectors first, else it is the same. Is anyone using this setting? Marcus

June 18, 2019

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

by Esteban Maringolo

Hi Guillermo, Your workaround effectively solved my issue. About the tonel format, in the .properties file at the sources directory there was such setting: https://github.com/eMaringolo/rbac/blob/9279f22ef5fd1c4149090b5b39a6afa143a… But the .project file was missing at the root of the repository. So maybe it is a mix of both conditions. In any case, I'm glad the workaround works, and that it helped spotting a bug. Thank you! Esteban A. Maringolo On Tue, Jun 18, 2019 at 4:35 AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Iâve created an issue: > > https://github.com/pharo-vcs/iceberg/issues/1251 > > El 18 jun 2019, a las 9:30, Guillermo Polito <guillermopolito(a)gmail.com> > escribiÃ³: > > Hi Esteban, > > It seems like a bug in Iceberg. If you click on debug, youâll see that > although youâve said the project is in tonel format, itâs trying to use a > Filetree reader > > <PastedGraphic-2.png> > > This is due to some missing metadata in the commit (iceberg is relying on > commit information there and not working copy information). > > There is however a simple workaround. If you click in the commit button > youâll see that Iceberg tries to create and commit the missing files: > > <PastedGraphic-3.png> > > If you commit those files, then youâll be able to load your packages. > > Guille > > > El 18 jun 2019, a las 2:34, Esteban Maringolo <emaringolo(a)gmail.com> > escribiÃ³: > > Hi, > > I'm trying to load a package from a Tonel repository[1] that was created > using SETT[2]. > > The structure seems fine, but when I try to load a package, I'm getting > the message saying that there is no version for the package in the current > commit (which seems wrong at least to the naked eye). > > Eg. > <image.png> > > Any idea of how to fix it? > > Regards! > > [1] https://github.com/eMaringolo/rbac/tree/master/sources/ > [2] https://github.com/gemtalk/sett > > > > Esteban A. Maringolo > > > >

June 18, 2019

Re: [Pharo-users] Autocompletion

by Marcus Denker

> On 16 Jun 2019, at 08:41, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > I found the cause - I created the #buttonBad accessing methods with code > (re)factoring (generate accessors), and in this case the accessors are made > in this fashion: > > CustomerSatisfaction >> buttonBad: *anObject > *buttonBad := *anObject > > *It's better to use > > CustomerSatisfaction >> buttonBad: *aComposablePresenterClass > *buttonBad := *aComposablePresenterClass > > *as this method is doing: > > ComposablePresenter >> instantiate: aComposablePresenterClass > "Instantiate a ComposablePresenter subclass and set its instance owner" > > ^ aComposablePresenterClass owner: self > Yes, the problem is that the Type guesser guesses types, but then they are used as if they would be the truthâ¦ this is done in two cases: 1) names of arguments, as you have seen: if you call it âanArrayâ, the code completion will only show you method for Array. 2) sends to Globals that are classes: every send of the kind âClass somethingâ will be types as âinstance of Classâ. Which is not even true for #new in all cases (see String). What would be better: distinguish between âtypesâ and âtype guessâ. The later we should use to sort the results, not to restrict it. > To find the cause, I used the debugger extensively and found the core logic > in ECInstVarTypeGuesser >> perform method - it was quite an exercise! > Wow! that is a real execise. Marcus

June 18, 2019

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

by Guillermo Polito

Iâve created an issue: https://github.com/pharo-vcs/iceberg/issues/1251 <https://github.com/pharo-vcs/iceberg/issues/1251> > El 18 jun 2019, a las 9:30, Guillermo Polito <guillermopolito(a)gmail.com> escribiÃ³: > > Hi Esteban, > > It seems like a bug in Iceberg. If you click on debug, youâll see that although youâve said the project is in tonel format, itâs trying to use a Filetree reader > > <PastedGraphic-2.png> > > This is due to some missing metadata in the commit (iceberg is relying on commit information there and not working copy information). > > There is however a simple workaround. If you click in the commit button youâll see that Iceberg tries to create and commit the missing files: > > <PastedGraphic-3.png> > > If you commit those files, then youâll be able to load your packages. > > Guille > > >> El 18 jun 2019, a las 2:34, Esteban Maringolo <emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>> escribiÃ³: >> >> Hi, >> >> I'm trying to load a package from a Tonel repository[1] that was created using SETT[2]. >> >> The structure seems fine, but when I try to load a package, I'm getting the message saying that there is no version for the package in the current commit (which seems wrong at least to the naked eye). >> >> Eg. >> <image.png> >> >> Any idea of how to fix it? >> >> Regards! >> >> [1] https://github.com/eMaringolo/rbac/tree/master/sources/ <https://github.com/eMaringolo/rbac/tree/master/sources/> >> [2] https://github.com/gemtalk/sett <https://github.com/gemtalk/sett> >> >> >> >> Esteban A. Maringolo >

June 18, 2019

Re: [Pharo-users] Iceberg loading a Tonel package migrated using SETT

by Guillermo Polito

Hi Esteban, It seems like a bug in Iceberg. If you click on debug, youâll see that although youâve said the project is in tonel format, itâs trying to use a Filetree reader This is due to some missing metadata in the commit (iceberg is relying on commit information there and not working copy information). There is however a simple workaround. If you click in the commit button youâll see that Iceberg tries to create and commit the missing files: If you commit those files, then youâll be able to load your packages. Guille > El 18 jun 2019, a las 2:34, Esteban Maringolo <emaringolo(a)gmail.com> escribiÃ³: > > Hi, > > I'm trying to load a package from a Tonel repository[1] that was created using SETT[2]. > > The structure seems fine, but when I try to load a package, I'm getting the message saying that there is no version for the package in the current commit (which seems wrong at least to the naked eye). > > Eg. > <image.png> > > Any idea of how to fix it? > > Regards! > > [1] https://github.com/eMaringolo/rbac/tree/master/sources/ <https://github.com/eMaringolo/rbac/tree/master/sources/> > [2] https://github.com/gemtalk/sett <https://github.com/gemtalk/sett> > > > > Esteban A. Maringolo

June 18, 2019

Iceberg loading a Tonel package migrated using SETT

by Esteban Maringolo

Hi, I'm trying to load a package from a Tonel repository[1] that was created using SETT[2]. The structure seems fine, but when I try to load a package, I'm getting the message saying that there is no version for the package in the current commit (which seems wrong at least to the naked eye). Eg. [image: image.png] Any idea of how to fix it? Regards! [1] https://github.com/eMaringolo/rbac/tree/master/sources/ [2] https://github.com/gemtalk/sett Esteban A. Maringolo

June 18, 2019

SETT Commit per bundle/package

by Esteban Maringolo

Hi, I don't know if anybody is using SETT to migrate from VW's Store to a Tonel repository, but I'm trying to pull back to Pharo a few packages I moved to VW and continued to maintain there. I don't understand why SETT creates a commit on a "per pundle" (package/bundle) basis. What would be the approach to get a lot of packages working together? E.g. MyPackage-Core, MyPackage-Glorp, MyPackage-Tests, etc. Should MyPackage be a Bundle instead? Regards, Esteban A. Maringolo

June 17, 2019

Re: [Pharo-users] How to visit over packages, classes, methods (all types)

by Tim Mackinnon

If you have any thoughts on direction, I could take a look - I did the âdirtyâ and reimplemented the methods like everyone elseâ¦ but it really felt like I shouldnât have had toâ¦ So my code looked a bit like this (where I should have used some sort of visitor with my stream instantiated, or maybe I could pass through some block, I think) (exercise solutionClasses asSortedCollection: [ :a :b | a name <= b name ]) do: [ :class | (exercise exercisePackage extendsClass: class) ifTrue: [ class exPrintOutExtensionsFor: exercise exercisePackage on: s ] ifFalse: [ class exPrintOutOn: s ] ] ]. And then in ClassDescription I had methods like this (noticed I need to visit the definition, the comments, the categories for class and instance etc.: exPrintOutOn: aWriteStream "Print a description of the receiver on aWriteStream." aWriteStream nextPutAll: '"-- #', self name, ' (class) --"'; cr; cr; nextPutAll: self definition; nextPut: $.; cr; cr. self hasComment ifTrue: [ aWriteStream nextPut: $". self comment trimBoth encodeDoublingDoubleQuotesOn: aWriteStream. aWriteStream nextPut: $"; cr; cr ]. self exPrintOutCategoriesFor: self class on: aWriteStream. self exPrintOutCategoriesFor: self on: aWriteStream > On 13 Jun 2019, at 08:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 19 May 2019, at 19:23, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - is there a way to iterate over all the code in a package (or class or baseline) in a generic way (to pretty print out class definitions, and methods - including extensions ). >> >> I was kind of hoping that with TonelWriter and Fileout and Critics that we would have a generic visitor mechanism but it seems that all of them just implemented it again - which misses a big opportunity for refactoring so that when you want to reason/print/manipulate code - it would be more straight forward. >> >> Is there anything/anyone addressing this ? Or maybe Iâve missed an obvious trick somewhere? >> > > I think we always wanted to add some default âvisitorâ style way of iterate over the structureâ¦ > > I will add this higher on my priorities, because it actually should be quite simple. > > > Marcus > >

June 17, 2019

Re: [Pharo-users] Introduction GSoC 2019

by HernÃ¡n Morales Durand

Hi Nina, This is very important for the community. If you want to check graph layouting applied to cancer research this is a good project to grab ideas from: http://bioinfo-out.curie.fr/projects/dedal/#downloads And you can browse Cytoscape apps for more : http://apps.cytoscape.org/ Cheers, HernÃ¡n El sÃ¡b., 11 may. 2019 a las 7:18, Nina Medic (<medicka992(a)gmail.com>) escribiÃ³: > Hello, > I am Nina, and I am a student from Serbia. Currently I am on the second > year, of my master studies in Computer science. I have been working with > Pharo for more than a year now. As a project in one of my classes, I was > implementing a program that parses graphs and makes a visualization of > them. Last semester I followed MOOC for Pharo. > > A couple of days ago, I was fortunate enough to be accepted for this year > Google Summer of Code. The project I will be working on is called *Graph > library with layouting algorithm*. What I will do is implement the graph > structure with all necessary parts in one separate library. Beside that I > will include layouthing algorithms. Some of which are already implemented > as a part of some other projects and packages, those I will pull out. For > the other ones, I will be using doctoral dissertation from Vaderna Renata > titled *Algorithms and a language for the support of automatically laying > out diagram elements*. You can find my proposal here: > > https://docs.google.com/document/d/1V8_HaZnxYsCfaiZs4vI1C5Dh4TvRPz-H51aYOuY… > > I would like to know, what are you thinking about this project. How > important is for the community? > > One of fellow students from GSoC (we are both working for Pharo > consortium) and I are considering using the same blog. What do you think > about that? I will be also posting about my progress on Twitter: > https://twitter.com/medicka992 which will make it easy for everybody to > follow my work. > > I am looking forward to working on this project and with all of you. > > Sincerely, > Nina. >

June 17, 2019