- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Reminder: change the archiving tool

by Miguel CobÃ¡

El vie, 21-01-2011 a las 13:59 +0100, Igor Stasenko escribiÃ³: > All .zip files with pharo images having an annoying Apple-ism - a > .DS_Store garbage file. > Please use a zip archiver which includes only relevant files to > archive, because obviously this garbage has no use anywhere but Macs. > +1 -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 21, 2011

Re: [Pharo-project] OB failing tests in Pharo 1.2

by Tudor Girba

That is not very encouraging :) Cheers, Doru On 21 Jan 2011, at 15:43, Lukas Renggli wrote: >> Hi Lukas. I was checking the 4 failing tests in Pharo 1.2: >> http://code.google.com/p/pharo/issues/detail?id=3470 >> >> The problem seems related to the changes with the >> SmalltalkEditor/ParagraphEditor and friends. The tests fails because the >> instVar "message" is nil, because nobody call OBKeyBindingsTest >> browseIt: >> aSelector >> nor its friends. This was called in Pharo 1.1 from OBTextMorphEditor >> because it was a subclass of ParagraphEditor. >> >> Now, I have no idea how to make it work in Pharo 1.2 > > Yeah, me neither. OB-Morphic is totally broken and it cannot be > quickly fixed. The editor support has to be completely rewritten on > top of the new infrastructure to get a browser that properly works. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Jan. 21, 2011

Re: [Pharo-project] Gofer issue

by Miguel CobÃ¡

El vie, 21-01-2011 a las 11:05 +0100, Igor Stasenko escribiÃ³: > Okay, i found the solution. Use Installer ! > > Installer monticello http: 'http://www.squeaksource.com'; > project: 'VMMaker'; > install: 'CMakeVMMaker' > > > works well for me and loads correct *latest* version. That isn't a solution and open again a gratuitous discussion about gofer vs installer. The point is, in a distributed SCM system, like Monticello is, there isn't a latest version. At least not by the traditional (suversion for example) way of knowing the monotone numeric integer version number. As Lukas said, the only way to know something is latest is to compare timestamps, but not version numbers or commits id. They aren't not intended to be ordered respect to time. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 21, 2011

Re: [Pharo-project] Issue 3179 in pharo: Failing Tests for Monticello

by pharo＠googlecode.com

Updates: Status: Fixed Labels: -Milestone-1.2 Comment #8 on issue 3179 by marcus.d...(a)gmail.com: Failing Tests for Monticello http://code.google.com/p/pharo/issues/detail?id=3179 I added it to 1.2... TODO: add FixingMonticelloTestFailingInHudson.1.cs to 1.3 (and on close tag this report 1.2 again)

Jan. 21, 2011

Re: [Pharo-project] Issue 3566 in pharo: Changes needed to update Sound for 1.2

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 -Milestone-1.3 Milestone-1.2-DevImage Comment #5 on issue 3566 by marcus.d...(a)gmail.com: Changes needed to update Sound for 1.2 http://code.google.com/p/pharo/issues/detail?id=3566 (No comment was entered for this change.)

Jan. 21, 2011

Re: [Pharo-project] Issue 2757 in pharo: Refactor StringHolder

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 2757 by stephane...(a)gmail.com: Refactor StringHolder http://code.google.com/p/pharo/issues/detail?id=2757 in 13011

Jan. 21, 2011

[Pharo-project] Issue 3568 in pharo: Remove SelectorBrowser

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com CC: Benjamin...(a)gmail.com Labels: Milestone-1.3 New issue 3568 by stephane...(a)gmail.com: Remove SelectorBrowser http://code.google.com/p/pharo/issues/detail?id=3568 Now we can remove SelectorBrowser. Before we should check that '*b' . 'ab' . true shows match in Finder.

Jan. 21, 2011

Re: [Pharo-project] Issue 3563 in pharo: PCCByCompilationTest tests sometimes fail randomly

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Comment #1 on issue 3563 by marcus.d...(a)gmail.com: PCCByCompilationTest tests sometimes fail randomly http://code.google.com/p/pharo/issues/detail?id=3563 removed from 1.2 for now

Jan. 21, 2011

Re: [Pharo-project] Issue 1487 in pharo: DateAndTime/TimeStamp can't handle times with nanoseconds

by pharo＠googlecode.com

Updates: Status: Invalid Comment #3 on issue 1487 by npapoyl...(a)gmail.com: DateAndTime/TimeStamp can't handle times with nanoseconds http://code.google.com/p/pharo/issues/detail?id=1487 DateAndTime and subclasses simply do not deal with nanoseconds, the above code does not fail, but does not take the nanoseconds into account either. This seems to be intented.

Jan. 21, 2011

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Comment #19 on issue 3489 by marianopeck: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 commited and merged. Also commited to Metacell configurations. I clos ethe issue

Jan. 21, 2011