March 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 252d6a: 40566

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 252d6aa07e54f8efd01e514322bad290e5664b0b https://github.com/pharo-project/pharo-core/commit/252d6aa07e54f8efd01e5143… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-19 (Thu, 19 Mar 2015) Changed paths: A Collections-Strings.package/String.class/instance/converting/asLegalSelector.st M Morphic-Core.package/WorldState.class/class/world menu items/mostUsedToolsOn_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script565.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script566.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40565.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40566.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-Workspace.package/Workspace.class/class/instance creation/title.st Log Message: ----------- 40566 14969 Bring back #asLegalSelector https://pharo.fogbugz.com/f/cases/14969 14137 Workspace/GTPlayground windows should be called appropriately https://pharo.fogbugz.com/f/cases/14137 http://files.pharo.org/image/40/40566.zip

March 19, 2015

[pharo-project/pharo-core]

by GitHub

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

March 19, 2015

Re: [Pharo-dev] Jenkins build trigger

by Christophe Demarey

Le 17 mars 2015 Ã 19:41, Stephan Eggermont a Ã©crit : > On 17/03/15 16:08, Christophe Demarey wrote: >> >> Le 17 mars 2015 Ã 15:28, Stephan Eggermont a Ã©crit : >>> That results in scheduled. The first time, it resulted in two builds being scheduled. After trying again, one build was scheduled. >>> After committing again, no build was scheduled. >> >> then, the problem should be investigated on the Smalltalkhub side. >> It would be good to have a test button there and be able to get the feedback. >> Without that, difficult to say what is wrong > > I find it interesting that the missing build gets triggered after triggering a build with a web browser, and especially that a normal > curl/wget does not work. Which projects actually use this build trigger? Not a lot as it is a new feature. I use it for another project and works well. I'm not aware of other projects using it. > Versionner still uses both url trigger and this one. Good catch, I forgot to remove the url trigger. I just updated it.

March 19, 2015

Re: [Pharo-dev] [Pharo4] 203 issues tagged tagged for Pharo4

by Marcus Denker

88. https://pharo.fogbugz.com/f/filters/103/4-0-All > On 18 Mar 2015, at 16:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Now we are at 98 > > Below 100, this is a good milestone. > >> On 17 Mar 2015, at 10:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Wow! Great! >> >> Now: 125 >

March 19, 2015

Re: [Pharo-dev] #instVarNamed: mixed up ?

by Marcus Denker

Ups, a bug. I will investigateâ¦ > On 19 Mar 2015, at 07:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I had the strangest problem yesterday in #40528 > > Define a class: > > Object subclass: #AAA > instanceVariableNames: 'five four one three two' > classVariableNames: '' > category: '_UnpackagedPackage' > > With one method: > > initialize > super initialize. > one := 1. > two := 2. > three := 3. > four := 4. > five := 5 > > Open a playground and do it & go an instance: > > AAA new > > In the raw tab execute: > > self class allInstVarNames collect: [ :each | each -> (self instVarNamed: each) ]. > > Which gives you, as expected: > > {#five->5. #four->4. #one->1. #three->3. #two->2} > > Now auto generate one accessor, say for one. > > Play again, and now the result is: > > {#five->1. #four->2. #one->3. #three->4. #two->5} > > !? > > Reaccepting the class definition fixes the problem. > > Sven > > PS: this code is used by STON, NeoJSON & NeoCSV. > > >

March 19, 2015

#instVarNamed: mixed up ?

by Sven Van Caekenberghe

I had the strangest problem yesterday in #40528 Define a class: Object subclass: #AAA instanceVariableNames: 'five four one three two' classVariableNames: '' category: '_UnpackagedPackage' With one method: initialize super initialize. one := 1. two := 2. three := 3. four := 4. five := 5 Open a playground and do it & go an instance: AAA new In the raw tab execute: self class allInstVarNames collect: [ :each | each -> (self instVarNamed: each) ]. Which gives you, as expected: {#five->5. #four->4. #one->1. #three->3. #two->2} Now auto generate one accessor, say for one. Play again, and now the result is: {#five->1. #four->2. #one->3. #three->4. #two->5} !? Reaccepting the class definition fixes the problem. Sven PS: this code is used by STON, NeoJSON & NeoCSV.

March 19, 2015

Re: [Pharo-dev] GitFileTree repository commitish doesn't support slashes

by Thierry Goubier

Hi Peter, Le 19/03/2015 01:31, Peter UhnÃ¡k a Ã©crit : > Hi, > > the repository specification > 'github://<user name>/<project name>[:comitish]/<path to filetree repo>' > doesn't support slashes in commitish. > > For example if I have branch named 'feature/something', or > 'hotfix/otherthing' it breaks. Yes, it certainly would. > There may be conflict also with path (imagine having branch > repository/repository and and actual folder called repository), so this > may require something special... like having another separator... i.e. > <project name>[:commitish[:]]/<path to filetree repo>? (Optional ending > colon.) Yes, it looks like a good approach. But what if you have $: in the commitish? Another one would be to have, like gitfiletree urls, the ability to write: 'github://<user name>/<project name>[[?commit=comitish]&path=<path to filetree repo>]' Well, I was considering to allow, in gitfiletree, the following 'gitfiletree://<user name>/<project name>[:branch]/<path to filetree repo>', so now I'm having an excuse for not doing it ;) Thierry

March 19, 2015

GitFileTree repository commitish doesn't support slashes

by Peter UhnÃ¡k

Hi, the repository specification 'github://<user name>/<project name>[:comitish]/<path to filetree repo>' doesn't support slashes in commitish. For example if I have branch named 'feature/something', or 'hotfix/otherthing' it breaks. There may be conflict also with path (imagine having branch repository/repository and and actual folder called repository), so this may require something special... like having another separator... i.e. <project name>[:commitish[:]]/<path to filetree repo>? (Optional ending colon.) Peter

March 19, 2015

Re: [Pharo-dev] Workspace and GTPlayground menu item

by Norbert Hartl

> Am 18.03.2015 um 23:05 schrieb Aliaksei Syrel <alex.syrel(a)gmail.com>: > > >> On Wed, Mar 18, 2015 at 10:51 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> What is wrong with this: > > Nothing serious, just horrible ugliness (imho) > That depends on the needed space of the extra elements. might be solvable in a different way. IMHO every additional visual element that doesn't serve a purpose just clutters the view and makes it harder to use. A tab header is always ugly to me but as long as I gain ease of use I can live with it. Norbert

March 18, 2015

Re: [Pharo-dev] Workspace and GTPlayground menu item

by Aliaksei Syrel

On Wed, Mar 18, 2015 at 10:51 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > What is wrong with this: Nothing serious, just horrible ugliness (imho) Cheers, Alex

March 18, 2015