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

[Pharo-project] Syntax highlighting changed in 10500?

by Simon Denier

Why did the colors change in syntax highlighting for 10500? Especially, there is no more color-based discrimination between a class name, a local variable, a parameter, or an instance variable. I think it is a regression. -- Simon

Dec. 14, 2009

Re: [Pharo-project] Let's hire a Pharo developer

by StÃ©phane Ducasse

We should fix that :) On Dec 14, 2009, at 6:48 AM, John M McIntosh wrote: > Well for one thing it's hard to collect funds when you visit both the squeak and pharo home pages > and there is no "donation" link. If there is no way to make a donation, then don't expect one. > > The esug site is almost there, until you tap the "But, you you can make a donation to support ESUG." and get > Error: "/seaside/pier/supportesug" not found. No doubt someone should fix that, also a link that isn't as hard to find would be welcome.

Dec. 14, 2009

[Pharo-project] [update 1.1] #11100

by Damien Cassou

11100 ----- Issue 1595: ReadStream upTo: and upToEnd do not honour the readLimit (thank you Nicolas Cellier) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 14, 2009

Re: [Pharo-project] Let's hire a Pharo developer

by Mariano Martinez Peck

Me too. On Mon, Dec 14, 2009 at 10:21 AM, Francois Stephany < tulipe.moutarde(a)gmail.com> wrote: > > I'm the first one in the list. Who else? > > Even if I'm not involved in Smalltalk those days I would be in. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 14, 2009

Re: [Pharo-project] Let's hire a Pharo developer

by Francois Stephany

> I'm the first one in the list. Who else? Even if I'm not involved in Smalltalk those days I would be in.

Dec. 14, 2009

Re: [Pharo-project] stream nile fixes?

by Damien Cassou

On Sun, Dec 13, 2009 at 11:04 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > could you check if the following is working in Nile? > http://code.google.com/p/pharo/issues/detail?id=1595 I wrote Nile results. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 14, 2009

Re: [Pharo-project] Gofer git

by Peter Hugosson-Miller

Thanks, Lukas. Just checking that I hadn't missed something - not impossible before I've had my first coffee of the day ;-) -- Cheers, Peter. On 14 dec 2009, at 09.27, Lukas Renggli <renggli(a)gmail.com> wrote: > Obviously a copy and paste error. It should be like this: > > 6. The following command downloads all versions of SomePackage from > the remote repository to the local package-cache, if not present yet: > > Gofer new > squeaksource: 'repository'; > package: 'SomePackage'; > fetch > > 7. The following command uploads all versions of SomePackage from the > local package-cache to the remote repository, if not present yet: > > Gofer new > squeaksource: 'repository'; > package: 'SomePackage'; > push > > Better? > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 14, 2009

Re: [Pharo-project] Gofer git

by Lukas Renggli

Obviously a copy and paste error. It should be like this: 6. The following command downloads all versions of SomePackage from the remote repository to the local package-cache, if not present yet: Gofer new squeaksource: 'repository'; package: 'SomePackage'; fetch 7. The following command uploads all versions of SomePackage from the local package-cache to the remote repository, if not present yet: Gofer new squeaksource: 'repository'; package: 'SomePackage'; push Better? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 14, 2009

Re: [Pharo-project] Gofer git

by Peter Hugosson-Miller

Hmmm... Examples 6 and 7 look the same to me, care to explain further? -- Cheers, Peter. On 14 dec 2009, at 09.11, Lukas Renggli <renggli(a)gmail.com> wrote: > The latest version of Gofer should be more stable. I've rewritten most > internal implementation details, the tests should run faster and they > do not depend on an external repository anymore. Most of the core > functionality is now tested, not just things that are easy to test. I > did the following changes: > > 1. I've renamed #addPackage: and #addVersion: to #package: and > #version:. The #add: caused some confusion and people asked me what > was done at this point. Since this is just a plain specification of a > package or a version it is now called like that. It is also shorter. > > 2. Gofer doesn't support any longer to work on different repository > groups in one operation. I've never used it and it made the > implementation more complicated than necessary. The order in which > things are defined in Gofer doesn't matter anymore. The following > specification would try to operate on the packages Seaside2.8a1, > Scriptaculous and RSRSS2 in the repositories of Seaside and rsrss. > > Gofer new > squeaksource: 'Seaside'; > package: 'Seaside2.8a1'; > package: 'Scriptaculous'; > squeaksource: 'rsrss'; > package: 'RSRSS2' > > The above snipped is the same as the one below (which is the preferred > way of writing it): > > Gofer new > squeaksource: 'Seaside'; > squeaksource: 'rsrss'; > package: 'Seaside2.8a1'; > package: 'Scriptaculous'; > package: 'RSRSS2' > > 3. Gofer prefers to load versions from faster repositories. The > package-cache and local file-directories have higher priority than > remote repositories. > > 4. Gofer implicitly declares the local package cache as a repository. > To disable this, send the message #disablePackageCache to the Gofer > instance. > > 5. Gofer throws errors if a repository is not reachable. To disable > this, send the message #disableRepositoryErrors to the Gofer instance. > The example below will silently load the latest Seaside version from > the package-cache, if the remote repository is not reachable (network > error, squeaksource down, invalid repositor): > > Gofer new > disableRepositoryErrors; > squeaksource: 'Seaside'; > package: 'Seaside2.8a1'; > load > > 6. The following command fetches all versions of SomePackage into the > local package-cache that are not downloaded yet: > > Gofer new > squeaksource: 'repository'; > package: 'SomePackage'; > fetch > > 7. The following command commits all versions of SomePackage into the > remote repository that are not uploaded yet: > > Gofer new > squeaksource: 'repository'; > package: 'SomePackage'; > fetch > > 8. Gofer has better support for FTP repositories: > > Gofer new > url: 'ftp://wtf-is-ftp.com/code'; > ... > > 9. And local directories: > > Gofer new > directory: '/home/renggli/repository'; > ... > > 10. And local directories with subdirectories: > > Gofer new > directory: '/home/renggli/repository/*'; > ... > > With all this new functionality there might be bugs :-) > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 14, 2009

Re: [Pharo-project] Gofer git

by Lukas Renggli

The latest version of Gofer should be more stable. I've rewritten most internal implementation details, the tests should run faster and they do not depend on an external repository anymore. Most of the core functionality is now tested, not just things that are easy to test. I did the following changes: 1. I've renamed #addPackage: and #addVersion: to #package: and #version:. The #add: caused some confusion and people asked me what was done at this point. Since this is just a plain specification of a package or a version it is now called like that. It is also shorter. 2. Gofer doesn't support any longer to work on different repository groups in one operation. I've never used it and it made the implementation more complicated than necessary. The order in which things are defined in Gofer doesn't matter anymore. The following specification would try to operate on the packages Seaside2.8a1, Scriptaculous and RSRSS2 in the repositories of Seaside and rsrss. Gofer new squeaksource: 'Seaside'; package: 'Seaside2.8a1'; package: 'Scriptaculous'; squeaksource: 'rsrss'; package: 'RSRSS2' The above snipped is the same as the one below (which is the preferred way of writing it): Gofer new squeaksource: 'Seaside'; squeaksource: 'rsrss'; package: 'Seaside2.8a1'; package: 'Scriptaculous'; package: 'RSRSS2' 3. Gofer prefers to load versions from faster repositories. The package-cache and local file-directories have higher priority than remote repositories. 4. Gofer implicitly declares the local package cache as a repository. To disable this, send the message #disablePackageCache to the Gofer instance. 5. Gofer throws errors if a repository is not reachable. To disable this, send the message #disableRepositoryErrors to the Gofer instance. The example below will silently load the latest Seaside version from the package-cache, if the remote repository is not reachable (network error, squeaksource down, invalid repositor): Gofer new disableRepositoryErrors; squeaksource: 'Seaside'; package: 'Seaside2.8a1'; load 6. The following command fetches all versions of SomePackage into the local package-cache that are not downloaded yet: Gofer new squeaksource: 'repository'; package: 'SomePackage'; fetch 7. The following command commits all versions of SomePackage into the remote repository that are not uploaded yet: Gofer new squeaksource: 'repository'; package: 'SomePackage'; fetch 8. Gofer has better support for FTP repositories: Gofer new url: 'ftp://wtf-is-ftp.com/code'; ... 9. And local directories: Gofer new directory: '/home/renggli/repository'; ... 10. And local directories with subdirectories: Gofer new directory: '/home/renggli/repository/*'; ... With all this new functionality there might be bugs :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 14, 2009