April 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Any hope for Smalltalk on Raspberry Pi?

by Alistair Grant

Hi Damien, On Sun, Apr 17, 2016 at 08:46:19PM +0200, Damien Pollet wrote: > http://stephane.ducasse.free.fr/FreeBooks.html > and in the middle is > Smalltalk-80: The Language and its Implementation > > On 17 April 2016 at 19:37, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Sun, Apr 17, 2016 at 09:52:54AM +0200, stepharo wrote: > > ... > > check the new blue book on my web page to get an idea > > Would you mind providing a link? Thanks for your reply. I had found that page, but Stepharo had mentioned a "new" blue book, so assumed it was something else. Thanks again, Alistair

April 17, 2016

Re: [Pharo-users] Any hope for Smalltalk on Raspberry Pi?

by Damien Pollet

http://stephane.ducasse.free.fr/FreeBooks.html and in the middle is Smalltalk-80: The Language and its Implementation <http://sdmeta.gforge.inria.fr/FreeBooks/BlueBook/> On 17 April 2016 at 19:37, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Sun, Apr 17, 2016 at 09:52:54AM +0200, stepharo wrote: > > ... > > check the new blue book on my web page to get an idea > > Would you mind providing a link? > > Thanks, > Alistair > > P.S. Does anyone know what happened to Glenn Krasner post ParcPlace? > One of the nicer people I've met in my life and I'd be interested to > know. Thanks. > >

April 17, 2016

Re: [Pharo-users] Any hope for Smalltalk on Raspberry Pi?

by Alistair Grant

On Sun, Apr 17, 2016 at 09:52:54AM +0200, stepharo wrote: > ... > check the new blue book on my web page to get an idea Would you mind providing a link? Thanks, Alistair P.S. Does anyone know what happened to Glenn Krasner post ParcPlace? One of the nicer people I've met in my life and I'd be interested to know. Thanks.

April 17, 2016

Re: [Pharo-users] Load a project from GitHub with command line

by Thierry Goubier

Le 17/04/2016 17:17, Damien Pollet a Ã©crit : > On 17 April 2016 at 16:47, Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>> wrote: > > In fact it is there, but indirect (you can give a $WHERE when you > create a remote git repository with Monticello: it's the name > parameter). > > > But I'd have to somehow create the monticello repo then pass it to > metacello? No. When GitFileTree prepares for a clone, it already manipulates a $WHERE (which is, by default, the repository name, i.e. filetree) and checks a few things about it (does it exists, is it a git repo?) before calling git clone $WHERE. > But, if we focus on the $WHERE more directly, what would you like? > > - A per-url/per-project SWHERE? It could make the url syntax a bit > hard (there is already a $: to indicate branch and, implicitely, > subdirectory inside the git repo) but there is nothing forbidding > it. Something like: > 'gitfiletree://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/h… > <http://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/use…>' > (is that a correct url syntax?) > > > Yes, per-project. > > My use-case is I often clone repos with a different name than they have > on github (e.g. I took the convention that my github repos are named > pharo-something so that they stand out, but locally I don't care too > much about the pharo- prefix. I could also imagine a > myproject/dependencies/ subdirectory, where all clones of accessory > projects would go. Ok. > About the URL, I'm not sure the colon used for branch/subdir is really > correct; usually that's the role of the fragment, no? > https://url.spec.whatwg.org/#url-syntax Hum: one could use a fragment, but we'd be limited to one? The current syntax is the one used in github:// urls, so this is one we're quite familiar with. > Does this have to be specified in the URL? Conceptually, the monticello > repo that should be created/used is gitfiletree://imageDirectory/$WHERE. > Metacello does have to know from which git remote URL to do the clone, > but that's not the same thing as the filetree repo per se. The problem is that Metacello doesn't clone; it is delegated to Monticello(GitFileTree) (which allows for a clean extension of Metacello). This is different from the implementation of github/bitbucket urls (and even in thoses, Metacello sees only a "repository" spec). > - Note that I have a procedure for having the Pharo build > environment integrated inside the git, if you'd like (i.e. git clone > download also the build command for the right Pharo image: this is > my professional setup). > > > In fact my current project is trying to do exactly that: a command-line > tool that knows which base image to get, which VM to run it with, which > baselines to get / load, etc. â and as a preemptive heads-up, I already > have a name for it: fari (italian for "lighthouses" and esperanto for > "to do"; fari.st <http://fari.st> would even look like faristo = maker Oh. I just use makefiles and `pwd` to recover where is the gitfiletree repo (and download the right image and setup everything). I even have a Makefile that detects that you are either within git or inside a release, and toggles appropriately between GitFileTree and FileTree. What was important to me was to version the Makefile within the project. And to be able to be multi-language: build a C library and a Pharo image, in a project mixing C and Smalltalk. Thierry

April 17, 2016

Re: [Pharo-users] Load a project from GitHub with command line

by Damien Pollet

On 17 April 2016 at 16:47, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > In fact it is there, but indirect (you can give a $WHERE when you create a > remote git repository with Monticello: it's the name parameter). > But I'd have to somehow create the monticello repo then pass it to metacello? > But, if we focus on the $WHERE more directly, what would you like? > > - A per-url/per-project SWHERE? It could make the url syntax a bit hard > (there is already a $: to indicate branch and, implicitely, subdirectory > inside the git repo) but there is nothing forbidding it. Something like: > 'gitfiletree:// > github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/username/p…' > (is that a correct url syntax?) > Yes, per-project. My use-case is I often clone repos with a different name than they have on github (e.g. I took the convention that my github repos are named pharo-something so that they stand out, but locally I don't care too much about the pharo- prefix. I could also imagine a myproject/dependencies/ subdirectory, where all clones of accessory projects would go. About the URL, I'm not sure the colon used for branch/subdir is really correct; usually that's the role of the fragment, no? https://url.spec.whatwg.org/#url-syntax Does this have to be specified in the URL? Conceptually, the monticello repo that should be created/used is gitfiletree://imageDirectory/$WHERE. Metacello does have to know from which git remote URL to do the clone, but that's not the same thing as the filetree repo per se. > - Note that I have a procedure for having the Pharo build environment > integrated inside the git, if you'd like (i.e. git clone download also the > build command for the right Pharo image: this is my professional setup). > In fact my current project is trying to do exactly that: a command-line tool that knows which base image to get, which VM to run it with, which baselines to get / load, etc. â and as a preemptive heads-up, I already have a name for it: fari (italian for "lighthouses" and esperanto for "to do"; fari.st would even look like faristo = maker

April 17, 2016

Re: [Pharo-users] Load a project from GitHub with command line

by Thierry Goubier

Le 17/04/2016 16:59, Peter UhnÃ¡k a Ã©crit : > 'gitfiletree://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/h… > <http://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/use…>' > (is that a correct url syntax?) > > > Isn't this overloading the url a bit? ;) That's why I described the url. But you may be indicating below a better counter argument: $WHERE should not be a feature of the url; it is an element of the local copy (in short, you don't want the repository owner to control the $WHERE). > Why not: > > Metacello new > baseline: 'FT'; > repository: > 'gitfiletree://github.com/dalehenrich/filetree:pharo5.0/repository > <http://github.com/dalehenrich/filetree:pharo5.0/repository>'; > workingDirectory: '/home/username/project/filetree'; (or > #localClone, or #localRepository, or #something) > load > > Or (using git terminology): > > Metacello new > baseline: 'FT'; > repository: '/home/username/project/filetree'; > origin: > 'gitfiletree://github.com/dalehenrich/filetree:pharo5.0/repository > <http://github.com/dalehenrich/filetree:pharo5.0/repository>'; > load Yes, this would work. The first one is closer to the way the MCFileTreeGitRepository API represent it, but both may well already be usable (read: already implemented on the GitFileTree side) as soon as Metacello get that API. Thierry > > On Sun, Apr 17, 2016 at 4:47 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 17/04/2016 16:31, Damien Pollet a Ã©crit : > > Is there a convenient way to control where the clone will be > made in the > local filesystem? > Meaning: using something else than the implicit value for $WHERE: > > git clone $GITHUB_CLONE_URL $WHERE > > > In fact it is there, but indirect (you can give a $WHERE when you > create a remote git repository with Monticello: it's the name > parameter). > > But, if we focus on the $WHERE more directly, what would you like? > > - A per-url/per-project SWHERE? It could make the url syntax a bit > hard (there is already a $: to indicate branch and, implicitely, > subdirectory inside the git repo) but there is nothing forbidding > it. Something like: > 'gitfiletree://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/h… > <http://github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/use…>' > (is that a correct url syntax?) > > - Note that I have a procedure for having the Pharo build > environment integrated inside the git, if you'd like (i.e. git clone > download also the build command for the right Pharo image: this is > my professional setup). > > - A per-image $WHERE? > > - Reusing the Monticello default local repository directory setting? > (current behavior, actually). > > Thierry

April 17, 2016

Re: [Pharo-users] Trapping the Pharo window close event

by Nicolai Hess

2016-04-14 19:57 GMT+02:00 kmo <voxkmp(a)gmail.com>: > How do you get rid of that "Quit Pharo without saving message" that comes > up > when you try to close the Pharo window? I want to just let the user exit > without any message or perhaps replace the message with one of my own. > > > Aboiut what are we talking ? The "Quit Pharo without saving message" is something I only see on the Windows platform. And for getting rid of this message, you can set EnableAltF4Quit=0 in Pharo.ini The Other message that exists is "Save changes before quitting" when selecting the "Quit" menu in Pharos world menu. > > > > -- > View this message in context: > http://forum.world.st/Trapping-the-Pharo-window-close-event-tp4890079.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 17, 2016

Re: [Pharo-users] RBAddClassRefactoring ensuring existence

by Peter UhnÃ¡k

> > The ugly way: > > [ refactoring execute ] on: RBRefactoringError do:[:ex | ex resume]. > I thought about this, but there are many things that could go wrong (there are about ten preconditions), and I am certainly not interested in breaking my system by accident. However after fighting a lot with refactorings I found that I would need this behavior for many other thingsâ¦ ensuring that attribute exists, that method is the same... etc. And since there is no such support in refactorings it's kind of pointless for me to use as I will need to always work around it... or maybe I could make some sort of "Ensuring" framework on top... Peter

April 17, 2016

Re: [Pharo-users] Load a project from GitHub with command line

by Peter UhnÃ¡k

> > 'gitfiletree:// > github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/username/p…' > (is that a correct url syntax?) Isn't this overloading the url a bit? Why not: Metacello new baseline: 'FT'; repository: 'gitfiletree:// github.com/dalehenrich/filetree:pharo5.0/repository'; workingDirectory: '/home/username/project/filetree'; (or #localClone, or #localRepository, or #something) load Or (using git terminology): Metacello new baseline: 'FT'; repository: '/home/username/project/filetree'; origin: 'gitfiletree:// github.com/dalehenrich/filetree:pharo5.0/repository'; load On Sun, Apr 17, 2016 at 4:47 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 17/04/2016 16:31, Damien Pollet a Ã©crit : > >> Is there a convenient way to control where the clone will be made in the >> local filesystem? >> Meaning: using something else than the implicit value for $WHERE: >> >> git clone $GITHUB_CLONE_URL $WHERE >> > > In fact it is there, but indirect (you can give a $WHERE when you create a > remote git repository with Monticello: it's the name parameter). > > But, if we focus on the $WHERE more directly, what would you like? > > - A per-url/per-project SWHERE? It could make the url syntax a bit hard > (there is already a $: to indicate branch and, implicitely, subdirectory > inside the git repo) but there is nothing forbidding it. Something like: > 'gitfiletree:// > github.com/dalehenrich/filetree:pharo5.0/repository/?where=/home/username/p…' > (is that a correct url syntax?) > > - Note that I have a procedure for having the Pharo build environment > integrated inside the git, if you'd like (i.e. git clone download also the > build command for the right Pharo image: this is my professional setup). > > - A per-image $WHERE? > > - Reusing the Monticello default local repository directory setting? > (current behavior, actually). > > Thierry > > >> On 15 April 2016 at 19:08, Thierry Goubier <thierry.goubier(a)gmail.com >> <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 15/04/2016 18:49, Damien Pollet a Ã©crit : >> >> On 15 April 2016 at 17:39, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com> >> <mailto:thierry.goubier@gmail.com >> <mailto:thierry.goubier@gmail.com>>> wrote: >> >> And then you can load your project with: >> >> Metacello new >> baseline: 'YourTribes'; >> repository: >> 'gitfiletree://github.com/HappyPharoHackers/YourTribes >> <http://github.com/HappyPharoHackers/YourTribes>'; >> load: #(tests) >> >> >> So this does the clone directly from github? YAY :D >> >> >> Yes :) >> >> Thierry >> >> >> >> > >

April 17, 2016

Re: [Pharo-users] [Pharo-dev] GTDebugger shortcuts usability

by Peter UhnÃ¡k

Well, I've added a startup script for myself... but it would be nice to have it everywhere by default in some variant... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ StartupPreferencesLoader default executeAtomicItems: { StartupAction name: 'Change debugger labels & shortcuts' code: [ GLMMorphicActionRenderer compile: ( (GLMMorphicActionRenderer>>#render:) sourceCode copyReplaceAll: 'setBalloonText: (anAction title' with: 'setBalloonText: (anAction title asString' ). RestartDebugAction compile: 'defaultKeyText ^ ''R'''. RestartDebugAction compile: 'defaultLabel ^ ''Restart'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. ResumeDebugAction compile: 'defaultKeyText ^ ''P'''. ResumeDebugAction compile: 'defaultLabel ^ ''Proceed'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. StepIntoDebugAction compile: 'defaultKeyText ^ ''I'''. StepIntoDebugAction compile: 'defaultLabel ^ ''Into'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. StepOverDebugAction compile: 'defaultLabel ^ ''Over'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. StepThroughDebugAction compile: 'defaultLabel ^ ''Through'' asText addAttribute: TextEmphasis underlined from: 1 to: 1'. ] runOnce: true. } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Sat, Apr 16, 2016 at 11:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Letâs turn this energy into something positive. Please propose a concrete >> set of default keybindings that you think would work better. In this >> process, please take into account all keybindings that are already defined >> in the code editor (it might not be so easy as it appears). >> > > As I've said: > > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) > 2. can we use the default shortcuts pattern where one of the letters is > underlined? > > as for the shortcuts themselves, problem is proceed, restart & into > > proceed: ctrl+shift+p is not taken, so I don't see why it has shortcut > confusing with restart > restart: ctrl+shift+r indents, but I'd argue that uniformity is more > important here... indent is just convenience > into: ctrl+shift+i is taken (I've never used it, but it maybe it's > important), but we can still use ctrl+shift+n and underline n (point 2) > > If points 1 & 2 are implemented, then the letter is not as important, > although first letter is always preferable. > > Peter > > >> Cheers, >> Doru >> >> >> > On Apr 16, 2016, at 8:37 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> > >> > Hi, >> > >> > I'm getting fed-up with GTDebugger shortcuts since they are completely >> random. >> > >> > Can we have them more meaningful and/or somehow visible? >> > >> > For now I ended up overriding the labels so I can at least see them... >> but doing this is also stupid, because I still have to look at them since I >> cannot remember random shortcuts. >> > >> > <debugger.png> >> > â >> > 1. can we unify the shift vs ctrl+shift nonsense? (I'm using linux btw) >> > 2. can we use the default shortcuts pattern where one of the letters is >> underlined? >> > >> > Peter >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Value is always contextual." >> >> >> >> >> >> >

April 17, 2016