September 2015 - Pharo-users

Observing changes of regular attributes

by Peter UhnÃ¡k

Hi, is there a mechanism for observing a change of regular variables? Normally I would use ValueHolder (or fire announcements manually), but this assumes I can change the code. For example imagine a method of someone else's package ~~~~~~~~~~~~~~~ FAMIXNamedEntity>>name: aString name := aString ~~~~~~~~~~~~~~~ I could simply override the method, but that's very brittle since if I were to update the package it would load the "unmodified" version. Can I somehow overload the assignment operator? Can I augment methods? Is this even possible? Thanks, Peter

Sept. 9, 2015

Re: [Pharo-users] Having a look at Git+Pharo

by Thierry Goubier

2015-09-09 16:43 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > - a discussion about moving a smalltalkhub repository to git while >> preserving history > > > I've migrated some time ago > > http://forum.world.st/moving-to-git-and-preserving-monticello-history-td480… > > some (if not all) of the issues were resolved iirc, however since I didn't > need to migrate since then I don't know the current status. > > - a discussion about which process to follow in which conditions >> (should I use GitFileTree or FileTree?) > > > Please note that GitFileTree didn't reliably work under Windows (problems > with ProcessWrapper or something; crashing a lot), don't know the current > status. > I don't either. I made some changes on the ProcessWrapper use, hoping for the best, but I can't test :( > However from practical standpoint: > * with GitFileTree each MC commit inside Pharo creates a Git commit, so if > you change X packages within a single repo, you get also X git commits > * with FileTree you could pack them together more tightly but you need to > commit to git explicity. > Dale has the idea of a project (grouping packages) with a single commit; however the MC API has no notion of committing multiple packages in one step except when dealing with dependencies. GitFileTree, for handling package dependencies, has a mode for writing multiple packages and commit only once, so one commit for multiple packages would be very easy to do. A special api for Versionner? Thierry

Sept. 9, 2015

Re: [Pharo-users] [Pharo-dev] [ANN] MessageFlowBrowser

by Torsten Bergmann

Nicolai wrote: >You need to set the class this method belongs to: > >a smalltalkCode > smalltalkClass: [:each | each <class/behavior> ]; > display: [:each | each sourceCode ]]. Yes - I know that. At least from the code I found in the image. But how do I do that in the context of Glamour where the tree is transmitted to the code pane... See #openOn: in MessageFlowBrowser. Thanks T.

Sept. 9, 2015

Re: [Pharo-users] Having a look at Git+Pharo

by Peter UhnÃ¡k

> > - a discussion about moving a smalltalkhub repository to git while > preserving history I've migrated some time ago http://forum.world.st/moving-to-git-and-preserving-monticello-history-td480… some (if not all) of the issues were resolved iirc, however since I didn't need to migrate since then I don't know the current status. - a discussion about which process to follow in which conditions > (should I use GitFileTree or FileTree?) Please note that GitFileTree didn't reliably work under Windows (problems with ProcessWrapper or something; crashing a lot), don't know the current status. However from practical standpoint: * with GitFileTree each MC commit inside Pharo creates a Git commit, so if you change X packages within a single repo, you get also X git commits * with FileTree you could pack them together more tightly but you need to commit to git explicity. but otherwise I don't see much practical difference - what happens if a Metacello description loads a project hosted in git > but I still want to be able to hack on this dependency. So, this > dependency should not be read-only for me This is in my eyes very messy.... you could either add the package to a repository after you have loaded your project, or lock local repos... but it's quite a pain to keep everything in sync... but I didn't have time to simplify my workflow here yet. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "GitFileTree" Gofer new url: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main'; configurationOf: 'GitFileTree'; loadDevelopment. "Dependency 1" Metacello new baseline: 'Dependency1'; repository: 'gitfiletree:///home/wherever/dependency1/repository'; lock. "Dependency 2" Metacello new baseline: 'Project2'; repository: 'gitfiletree:///home/wherever/project2/repository'; lock. "My Project" Metacello new baseline: 'MyProject'; repository: 'gitfiletree:///home/wherever/myProject/repository'; onConflict: [ :ex | ex allow ]; load. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter

Sept. 9, 2015

Re: [Pharo-users] Having a look at Git+Pharo

by Thierry Goubier

2015-09-09 16:04 GMT+02:00 Damien Cassou <damien.cassou(a)inria.fr>: > Hi, > > today I wanted to have a look at how git integrates with Pharo. This is > what I found (mostly done by Thierry Goubier, thank you very much) and > what I didn't find: > > - there is some documentation here: > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > But this is largely unfinished material. I contributed by adding a few > things here and there but not much. If you have some experience, > please share it there > (https://github.com/SquareBracketAssociates/PharoInProgress) Missing > things include: > > - a discussion about which process to follow in which conditions > (should I use GitFileTree or FileTree?) > > - a discussion about moving a smalltalkhub repository to git while > preserving history > > - a discussion on how to write Metacello configurations for a project > on git and for a project which depends on a project on git. > > - there is a nice git merge driver > (https://github.com/ThierryGoubier/GitFileTree-MergeDriver) It seems > to work fine. I sent 3 minor pull requests. > > - a list of tools missing before everyone uses git. For example: > > - A tool to resolve merge conflicts in Pharo. We should reuse the diff > widget we have. > Dale proposed some tools: a diff parser/reader? A reader for files with conflict markers. Thierry > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

Sept. 9, 2015

Re: [Pharo-users] Having a look at Git+Pharo

by Thierry Goubier

2015-09-09 16:29 GMT+02:00 Damien Cassou <damien.cassou(a)inria.fr>: > > something else I forgot: > > - what happens if a Metacello description loads a project hosted in git > but I still want to be able to hack on this dependency. So, this > dependency should not be read-only for me > Can you give an example? > > - where to put the git repositories when images are frequently deleted > and downloaded again from the launcher? What if I Pillar is hosted on > github, Jenkins build Pillar images, and I want to download an image > with Pillar inside? How do I link the Pillar of the image to a > repository? Which repository? > Having a gitfiletree repository with an auto-clone / lazy clone option would work. When you open the repository for the first time, it clones it from where it was originally referenced. May not work transparently if there are authentification issues for the clone. Thierry > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

Sept. 9, 2015

Re: [Pharo-users] Having a look at Git+Pharo

by Damien Cassou

something else I forgot: - what happens if a Metacello description loads a project hosted in git but I still want to be able to hack on this dependency. So, this dependency should not be read-only for me - where to put the git repositories when images are frequently deleted and downloaded again from the launcher? What if I Pillar is hosted on github, Jenkins build Pillar images, and I want to download an image with Pillar inside? How do I link the Pillar of the image to a repository? Which repository? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 9, 2015

Having a look at Git+Pharo

by Damien Cassou

Hi, today I wanted to have a look at how git integrates with Pharo. This is what I found (mostly done by Thierry Goubier, thank you very much) and what I didn't find: - there is some documentation here: https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… But this is largely unfinished material. I contributed by adding a few things here and there but not much. If you have some experience, please share it there (https://github.com/SquareBracketAssociates/PharoInProgress) Missing things include: - a discussion about which process to follow in which conditions (should I use GitFileTree or FileTree?) - a discussion about moving a smalltalkhub repository to git while preserving history - a discussion on how to write Metacello configurations for a project on git and for a project which depends on a project on git. - there is a nice git merge driver (https://github.com/ThierryGoubier/GitFileTree-MergeDriver) It seems to work fine. I sent 3 minor pull requests. - a list of tools missing before everyone uses git. For example: - A tool to resolve merge conflicts in Pharo. We should reuse the diff widget we have. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 9, 2015

Re: [Pharo-users] [ANN] MessageFlowBrowser

by Nicolai Hess

2015-09-09 14:07 GMT+02:00 Torsten Bergmann <astares(a)gmx.de>: > A new tool to browse and dive deep into the flow of messages > using a tree representation (messages, senders, implementors, ...) > and further on. I know such a tool from Smalltalk/MT and it is really > helpful to trace a message flow without running in the debugger. > Great! > > > If someone with GT knowledge and time could help to correct the syntax > highlighting > in the code pane this would be super cool (see method MessageFlowBrowser > #openOn:). > You need to set the class this method belongs to: a smalltalkCode smalltalkClass: [:each | each <class/behavior> ]; display: [:each | each sourceCode ]]. > Also selection could be improved to show/highlight the messages sent > directly > in the code. Unfortunately I'm not so familar with the current code > editors - so > any help is appreciated. > > Repo is open for contribution. > > Thanks > T. > >

Sept. 9, 2015

[ANN] MessageFlowBrowser

by Torsten Bergmann

A new tool to browse and dive deep into the flow of messages using a tree representation (messages, senders, implementors, ...) and further on. I know such a tool from Smalltalk/MT and it is really helpful to trace a message flow without running in the debugger. See the attached screenshot, the best is to try it: In a latest Pharo 5.0 image (Pharo5.0 Latest update: #50314) you can evaluate: Gofer new url: 'http://smalltalkhub.com/mc/TorstenBergmann/MessageFlowBrowser/main'; package: 'Tool-MessageFlowBrowser'; load to load it. Then open whatever method in Nautilus and choose "Message Flow" from the context menu. The nice thing is that you can dive into senders, implementors, messages sent deeper and deeper (or up again) and you do not open more and more windows but stay in a single window !!! Alternatively you can start the tool from the playground: MessageFlowBrowser openOn: #inspect "open the flow browser on a selector" MessageFlowBrowser openOn: (Compiler>>#evaluate) "open the flow browser on a method" MessageFlowBrowser openOn: Object "open the flow browser on a class" 1 messageFlow. "open the flow browser on the class of an instance" If someone with GT knowledge and time could help to correct the syntax highlighting in the code pane this would be super cool (see method MessageFlowBrowser #openOn:). Also selection could be improved to show/highlight the messages sent directly in the code. Unfortunately I'm not so familar with the current code editors - so any help is appreciated. Repo is open for contribution. Thanks T.

Sept. 9, 2015