- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

June 8, 2014

[pharo-project/pharo-core] 56a944: 40015

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 56a94496fd3eb54e33ec3265b33cf78089f4015f https://github.com/pharo-project/pharo-core/commit/56a94496fd3eb54e33ec3265… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-08 (Sun, 08 Jun 2014) Changed paths: M NautilusCommon.package/extension/RBBrowserEnvironment/instance/traitsDo_.st R Refactoring-Critics.package/extension/ClassTestCase/instance/testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script15.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40015.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Settings.package/extension/FilePathEncoder/class/settingInputWidgetForNode_.st M System-Support.package/SmalltalkImage.class/instance/miscellaneous/metacelloPlatformAttributes.st Log Message: ----------- 40015 13281 Wrong environment when browsing scoped https://pharo.fogbugz.com/f/cases/13281 13301 Update metacelloPlatformAttributes https://pharo.fogbugz.com/f/cases/13301 13267 Settings Browser: Missing fields and file-dialogs in the Appearance Section https://pharo.fogbugz.com/f/cases/13267 13285 duplicated test: testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits https://pharo.fogbugz.com/f/cases/13285 http://files.pharo.org/image/40/40015.zip

June 8, 2014

[ANN] bugfix release Seaside 3.0.13

by Johan Brichau

Hi, This email only concerns people using the legacy 3.0.x version of Seaside. If you are still using a 3.0.x version of Seaside in Pharo 3 or Gemstone 3.2, you will benefit from upgrading to its latest bugfix release 3.0.13 [1] Cheers Johan [1] https://code.google.com/p/seaside/wiki/Seaside3011Changelog

June 8, 2014

Re: [Pharo-dev] issue validation for pharo40

by Esteban Lorenzano

yesterday I fixed a problem in the monkey (it was going to look for slices to old inbox) but looks not enoughâ¦ tomorrow I will take a closer look. Esteban On 08 Jun 2014, at 05:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 07 Jun 2014, at 22:18, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> I guess you all already know, that the issuevalidator doesn't work for >> slices from pharo40 inbox. Is there anything we can do? >> > > Yes, It is on my TODO for next weekâ¦ (just came back from holidays). > > Marcus > >

June 8, 2014

Re: [Pharo-dev] Pipe operator

by Nicolas Cellier

2014-06-08 12:12 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: > What is that extension? > > Norbert > > I'm curious too :) I recently proposed to enable caret as a binary selector, maybe there's been a confusion... I remember a discussion about using ;; as pipe "operator" (it's more syntax sugar than operator), in august 2007 or so. But it was not me. http://bugs.squeak.org/view.php?id=6649 > Am 08.06.2014 um 09:27 schrieb stepharo <stepharo(a)free.fr>: > > if you are talking about the extension made by nicolas cellier: probably. > > Stef > > On 8/6/14 00:10, S. Garth Holland wrote: > > Will Pharo ever get the pipe opeator? > > http://www.reddit.com/r/smalltalk/comments/27k27b/chaining_messages/ > > /Garth > > > >

June 8, 2014

Re: [Pharo-dev] Pipe operator

by Norbert Hartl

What is that extension? Norbert > Am 08.06.2014 um 09:27 schrieb stepharo <stepharo(a)free.fr>: > > if you are talking about the extension made by nicolas cellier: probably. > > Stef > >> On 8/6/14 00:10, S. Garth Holland wrote: >> Will Pharo ever get the pipe opeator? >> >> http://www.reddit.com/r/smalltalk/comments/27k27b/chaining_messages/ >> >> /Garth >

June 8, 2014

Re: [Pharo-dev] Pipe operator

by Norbert Hartl

I think you need to be more specific. The word pipe is misleading and not mentioned in the reddit post. The solution in that post is not an operator but a pattern you can implement easily yourself. To be more monadic like it wouldn't be this like in the example item safeChain recipient; address; street. Here you need to make sure all messages are chained (using the ; in smalltalk is actually chaining) on the proxy. If the proxy does not return the requested value but again a proxy with that value it would come closer. But not sure what you meant. Norbert > Am 08.06.2014 um 00:10 schrieb "S. Garth Holland" <steve9571952(a)hotmail.com>: > > Will Pharo ever get the pipe opeator? > > http://www.reddit.com/r/smalltalk/comments/27k27b/chaining_messages/ > > /Garth > >

June 8, 2014

Re: [Pharo-dev] some random git docs

by kilon alios

git also has excellent documentation http://git-scm.com/doc On Sun, Jun 8, 2014 at 12:37 PM, Ben Coman <btc(a)openinworld.com> wrote: > > I am using git for the first time (for documentation) and was trying to > understand the options for merging and conflict handling, and found some > stuff I thought might be generally useful to others - in particular what > "rebasing" was and when it might be appropriate - which I didn't have a > clue before. So here they are... > > http://blog.wuwon.id.au/2010/09/painless-merge-conflict-resolution-in.html > > http://softwareswirl.blogspot.com.au/2009/04/truce-in-merge- > vs-rebase-war.html > > http://stackoverflow.com/questions/457927/git-workflow- > and-rebase-vs-merge-questions > > http://differential.io/blog/best-way-to-merge-a-github-pull-request > > cheers -ben > > > >

June 8, 2014

some random git docs

by Ben Coman

I am using git for the first time (for documentation) and was trying to understand the options for merging and conflict handling, and found some stuff I thought might be generally useful to others - in particular what "rebasing" was and when it might be appropriate - which I didn't have a clue before. So here they are... http://blog.wuwon.id.au/2010/09/painless-merge-conflict-resolution-in.html http://softwareswirl.blogspot.com.au/2009/04/truce-in-merge-vs-rebase-war.h… http://stackoverflow.com/questions/457927/git-workflow-and-rebase-vs-merge-… http://differential.io/blog/best-way-to-merge-a-github-pull-request cheers -ben

June 8, 2014

Re: [Pharo-dev] issue validation for pharo40

by Marcus Denker

On 07 Jun 2014, at 22:18, Nicolai Hess <nicolaihess(a)web.de> wrote: > I guess you all already know, that the issuevalidator doesn't work for > slices from pharo40 inbox. Is there anything we can do? > Yes, It is on my TODO for next weekâ¦ (just came back from holidays). Marcus

June 8, 2014