April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 4000 in pharo: Little improvement in MenuMorph

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 4000 by marcus.d...(a)gmail.com: Little improvement in MenuMorph http://code.google.com/p/pharo/issues/detail?id=4000 in 13145

April 12, 2011

[Pharo-project] [COTDC] 47 - TAssertable

by laurent laffont

Today: TAssertable Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

April 12, 2011

Re: [Pharo-project] [COTDC] 46 - SUnitUnloader

by laurent laffont

Thank you Sven ! Laurent On Mon, Apr 11, 2011 at 9:03 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > I am SUnitUnloader, a little tool to unload SUnit and a fixed set of Tests > from the current image. > > Usage: SUnitUnloader new unloadAll > > Caveat: #unloadTestPackages uses a fixed and probably ill maintained list > of what packages hold unit tests. > > > On 11 Apr 2011, at 20:21, laurent laffont wrote: > > > Today: SUnitUnloader > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > >

April 12, 2011

Re: [Pharo-project] Please clarify which versions to report issues on

by Marcus Denker

On Apr 12, 2011, at 9:33 PM, DougEdmunds wrote: > Where's the best place to get the most recent v 1.3 on any given day? > > Some choices appear to be: > > 1. https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/ > (but which link?) The latest image is this: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/la… > 2. http://www.pharo-project.org/pharo-download : the link to "PharoCore 1.3 > (just core)" Hudson needs to start somewhere, and loading 140 updates is to slow. So we checkpoint all 10-20 updates (good to have anyway), and that is linked here: http://www.pharo-project.org/pharo-download/unstable-core It tends to be a relatively un=broken image, too. The hudson one is build after *every* update, and can be in need of another update to be usable. (But that does not happen often) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 12, 2011

Re: [Pharo-project] Please clarify which versions to report issues on

by DougEdmunds

Where's the best place to get the most recent v 1.3 on any given day? Some choices appear to be: 1. https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/ (but which link?) 2. http://www.pharo-project.org/pharo-download : the link to "PharoCore 1.3 (just core)" 3. Other location? -- View this message in context: http://forum.world.st/Please-clarify-which-versions-to-report-issues-on-tp3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 12, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Sven Van Caekenberghe

On 12 Apr 2011, at 16:20, Stephan Eggermont wrote: > http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-April/002802.html Sounds nice, but could you give some context, URLs ? What are they talking about ? Sven

April 12, 2011

Re: [Pharo-project] Issue 3062 in pharo: CompilerEvaluationTest >> testEvaluationOfSelfSend dependent on SmalltalkEditor

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3062 by marcus.d...(a)gmail.com: CompilerEvaluationTest >> testEvaluationOfSelfSend dependent on SmalltalkEditor http://code.google.com/p/pharo/issues/detail?id=3062 This has been fixed

April 12, 2011

Re: [Pharo-project] Issue 3109 in pharo: TextURL >> #actOnClickFor: dependent on network

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3109 by marcus.d...(a)gmail.com: TextURL >> #actOnClickFor: dependent on network http://code.google.com/p/pharo/issues/detail?id=3109 #actOnClickFor: has been removed in 1.3

April 12, 2011

Re: [Pharo-project] Please clarify which versions to report issues on

by Marcus Denker

On Apr 12, 2011, at 7:00 PM, DougEdmunds wrote: > If you start to open a new issue on > http://code.google.com/p/pharo/issues/list > this is what appears: > > "We are currently working on version 1.2, so please verify your issue with > the latest 1.2 Unstable version before reporting it - we improved a lot > the system." > We forgot to update this. So I updated it now. We are working on 1.3. 1.2 will only see fixes of real bugs of the kind that are extremely important. > But on http://www.pharo-project.org/pharo-download, the 'unstable' version > is listed as > Pharo 1.3 image (unstable), with a link to PharoCore 1.3 (just core). > > Is there another place to go to for 1.2 Unstable? Or should everything be > reported against 1.3? > 1.3 > If it is 1.3, can someone update the default text new issue info on > code.google.com? DONE -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 12, 2011

Re: [Pharo-project] Issue 3262 in pharo: Debugger enhancement to open in a background process when the UI process is busy

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3262 by marcus.d...(a)gmail.com: Debugger enhancement to open in a background process when the UI process is busy http://code.google.com/p/pharo/issues/detail?id=3262 "Strangely enough the functions introduced by eliot got removed and not invoked in latter versions." So let's close this

April 12, 2011