December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo+Git cons?

by Norbert Hartl

> Am 04.12.2014 um 07:24 schrieb Thierry Goubier <thierry.goubier(a)gmail.com>: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : >> Eliot Miranda wrote: >>> >>> [and apologies for being deliberately incendiary but I *hate* the >>> movement away from tools in Squeak/Pharo. It is a movement towards >>> stasis and death, and personally I'm enjoying life too much]. >> >> So what we need is a native Smalltalk git ;) > > We need a better-than-git Smalltalk thing :) > +1 darcs anyone? Norbert >> Yes I know... more work with limited resources, but native git its being >> done in other places... (not sure how successfully) > > I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. > > Thierry > >> >> Javascript >> https://github.com/creationix/js-git >> >> Java >> http://eclipse.org/jgit/ >> >> Haskall >> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ >> https://github.com/vincenthz/hit >> >> Python >> https://www.samba.org/~jelmer/dulwich/ >> >> Perl >> https://metacpan.org/pod/Git::PurePerl > >

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Esteban Lorenzano

> On 04 Dec 2014, at 09:07, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-12-04 8:27 GMT+01:00 Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>>: > >> On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 03/12/2014 14:02, Ben Coman a Ã©crit : >>> Eliot Miranda wrote: >>>> >>>> [and apologies for being deliberately incendiary but I *hate* the >>>> movement away from tools in Squeak/Pharo. It is a movement towards >>>> stasis and death, and personally I'm enjoying life too much]. >>> >>> So what we need is a native Smalltalk git ;) >> >> We need a better-than-git Smalltalk thing :) >> >>> Yes I know... more work with limited resources, but native git its being >>> done in other places... (not sure how successfully) >> >> I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. >> >> https://github.com/dalehenrich/FSGit <https://github.com/dalehenrich/FSGit> >> >> https://github.com/theseion/fs-git <https://github.com/theseion/fs-git> >> >> http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> >> http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem <http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem> >> >> They do lack a bit of activity. > > Thatâs because they should be superseded by the libgit2 bindings. > > If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer. The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format. > > But correct me if I got that wrong. it was Camilloâs work/idea, not Benâs. and well, it was a great idea, but never more than an experiment. I wanted it too, but I didnât continue the work because it would be different from monticello and community has proved been refractory to ideas that goes further it. so I get back to the other idea (Yours, Max) which was made monticello work with git. It will not be complete, but it will be a start. not that I have had actually time to work on it, but I will continue Max work as soon as I can allocate some time. Esteban > > > This is the right repo: http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> (the github version is outdated). > > Thanks for the reminder (and the hard work you're putting into the libgit2 bindings), > > Thierry > > >> >> Thierry >> >>> >>> Javascript >>> https://github.com/creationix/js-git <https://github.com/creationix/js-git> >>> >>> Java >>> http://eclipse.org/jgit/ <http://eclipse.org/jgit/> >>> >>> Haskall >>> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ <http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/> >>> https://github.com/vincenthz/hit <https://github.com/vincenthz/hit> >>> >>> Python >>> https://www.samba.org/~jelmer/dulwich/ <https://www.samba.org/~jelmer/dulwich/> >>> >>> Perl >>> https://metacpan.org/pod/Git::PurePerl <https://metacpan.org/pod/Git::PurePerl>

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Thierry Goubier

2014-12-04 8:27 GMT+01:00 Max Leske <maxleske(a)gmail.com>: > > On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : > > Eliot Miranda wrote: > > > [and apologies for being deliberately incendiary but I *hate* the > movement away from tools in Squeak/Pharo. It is a movement towards > stasis and death, and personally I'm enjoying life too much]. > > > So what we need is a native Smalltalk git ;) > > > We need a better-than-git Smalltalk thing :) > > Yes I know... more work with limited resources, but native git its being > done in other places... (not sure how successfully) > > > I can give you a head start. There is some Smalltalk code to reuse; it's > called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. > > > That's because they should be superseded by the libgit2 bindings. > If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer. The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format. But correct me if I got that wrong. > This is the right repo: > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git (the github > version is outdated). > Thanks for the reminder (and the hard work you're putting into the libgit2 bindings), Thierry > > > Thierry > > > Javascript > https://github.com/creationix/js-git > > Java > http://eclipse.org/jgit/ > > Haskall > http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ > https://github.com/vincenthz/hit > > Python > https://www.samba.org/~jelmer/dulwich/ > > Perl > https://metacpan.org/pod/Git::PurePerl > > > > > > > >

Dec. 4, 2014

GTPlayground cache

by Nicolai Hess

Since 40393 the play-cache is not read when you open the first GTPlayground in a fresh image.

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Max Leske

> On 04.12.2014, at 07:24, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 03/12/2014 14:02, Ben Coman a Ã©crit : >> Eliot Miranda wrote: >>> >>> [and apologies for being deliberately incendiary but I *hate* the >>> movement away from tools in Squeak/Pharo. It is a movement towards >>> stasis and death, and personally I'm enjoying life too much]. >> >> So what we need is a native Smalltalk git ;) > > We need a better-than-git Smalltalk thing :) > >> Yes I know... more work with limited resources, but native git its being >> done in other places... (not sure how successfully) > > I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. > > https://github.com/dalehenrich/FSGit > > https://github.com/theseion/fs-git > > http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git > http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem > > They do lack a bit of activity. Thatâs because they should be superseded by the libgit2 bindings. This is the right repo: http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git <http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git> (the github version is outdated). > > Thierry > >> >> Javascript >> https://github.com/creationix/js-git >> >> Java >> http://eclipse.org/jgit/ >> >> Haskall >> http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ >> https://github.com/vincenthz/hit >> >> Python >> https://www.samba.org/~jelmer/dulwich/ >> >> Perl >> https://metacpan.org/pod/Git::PurePerl >> >> >> >> > >

Dec. 4, 2014

Re: [Pharo-dev] failing test in writing files

by Sven Van Caekenberghe

self assert: (file species isKindOf: FileStream) But that is a weird test. What is the point ? You have to test behaviour, like write a file and see if it was written. Testing types is very seldom done, because this is an implementation detail. > On 04 Dec 2014, at 01:32, sheridan(a)sheridan-mahoney.com wrote: > > Hi there, > > I have a failing test and was wondering if anyone would have a sense as to why: > > | testString filename file | > testString := 'ascii String'. > filename := 'test-file-' , 99 atRandom printString , '.txt'. > filename asFileReference ensureDelete. > file := filename asFileReference > writeStreamDo: [ :stream | > stream > nextPutAll: testString; > crlf ]. > self assert: file species = FileStream. > > > Many thanks, > > Sheri > > > >

Dec. 4, 2014

Re: [Pharo-dev] Pharo+Git cons?

by Thierry Goubier

Le 03/12/2014 14:02, Ben Coman a Ã©crit : > Eliot Miranda wrote: >> >> [and apologies for being deliberately incendiary but I *hate* the >> movement away from tools in Squeak/Pharo. It is a movement towards >> stasis and death, and personally I'm enjoying life too much]. > > So what we need is a native Smalltalk git ;) We need a better-than-git Smalltalk thing :) > Yes I know... more work with limited resources, but native git its being > done in other places... (not sure how successfully) I can give you a head start. There is some Smalltalk code to reuse; it's called FileSystem-Git, or FS-Git. https://github.com/dalehenrich/FSGit https://github.com/theseion/fs-git http://smalltalkhub.com/#!/~FileSystemGitDev/FileSystem-Git http://smalltalkhub.com/#!/~FileSystemGitDev/Git-FileSystem They do lack a bit of activity. Thierry > > Javascript > https://github.com/creationix/js-git > > Java > http://eclipse.org/jgit/ > > Haskall > http://stefan.saasen.me/articles/git-clone-in-haskell-from-the-bottom-up/ > https://github.com/vincenthz/hit > > Python > https://www.samba.org/~jelmer/dulwich/ > > Perl > https://metacpan.org/pod/Git::PurePerl > > > >

Dec. 4, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40398 Home: https://github.com/pharo-project/pharo-core

Dec. 4, 2014

[pharo-project/pharo-core] b1943b: 40398

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b1943b98454f7963a03fa907fad6625c33b6b4d8 https://github.com/pharo-project/pharo-core/commit/b1943b98454f7963a03fa907… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-04 (Thu, 04 Dec 2014) Changed paths: M KernelTests.package/ManifestKernelTests.class/definition.st M SUnit-UI.package/TestRunner.class/definition.st M SUnit-UI.package/TestRunner.class/instance/accessing-categories/categorySelected.st M SUnit-UI.package/TestRunner.class/instance/accessing-categories/categorySelected_.st M SUnit-UI.package/TestRunner.class/instance/updating/updateCategories.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script398.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40398.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40398 12854 TestRunner package pane <shift> key multi-select not working https://pharo.fogbugz.com/f/cases/12854 14565 ManifestKernelTest superclass should be PackageManifest https://pharo.fogbugz.com/f/cases/14565 http://files.pharo.org/image/40/40398.zip

Dec. 4, 2014

Re: [Pharo-dev] terminating a String in Smalltalk?

by Eliot Miranda

Hi Sheridan, On Wed, Dec 3, 2014 at 10:14 AM, <sheridan(a)sheridan-mahoney.com> wrote: > > > Hi all, > > How do you terminate a string in Smalltalk so that it can be written to a > file? > You don't need to. Smalltalk objects include their size so there is no need to add a null byte to recognise their end. One may need to copy a string to add a null byte if passing a string to e.g. C, but inside the system no null termination is ever needed. You might want to read some treatment of the Smalltalk object model such as the last section of the Blue Book, or the Back to teh Future paper or my presentation on SPur at ESUG 2014, or... Thanks, > > Sheridan > -- best, Eliot

Dec. 4, 2014