- Pharo-dev - lists.pharo.org

[Pharo-project] from bash to Coral
by laurent laffont March 15, 2011

March 15, 2011

Hi, Is it possible today to write this using Coral ? find application library -type f $ -name "*.php" -o -name "*.phtml" $ -exec /usr/local/bin/xgettext -j -L PHP --from-code=utf-8 --keyword=traduire --keyword=_ -o library/translation/fr.pot {} \; for i in `ls library/translation/*.po` do /usr/local/bin/msgmerge -s $i library/translation/fr.pot -o $i /usr/local/bin/msgfmt -o `echo $i|cut -d '.' -f1`.mo $i done I need to write several scripts like this - would be cool to start with Coral. Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

5 6

[Pharo-project] Question about the design of the setting browser
by StÃ©phane Ducasse March 15, 2011

March 15, 2011

Hi alain I was reading the settingbrowser code and I have a question: why the settingbrowser inherits from MorphTreeModel. Why it does not inherits from Object or Model and has different widgets that may or not inherits from MorphTreeModel. To me it fits better the composition. Stef

2 1

[Pharo-project] Fwd: [Pharo-users] Riak Interface for Pharo Smalltalk
by Mariano Martinez Peck March 14, 2011

March 14, 2011

---------- Forwarded message ---------- From: Runar Jordahl <runar.jordahl(a)gmail.com> Date: Mon, Mar 14, 2011 at 10:59 PM Subject: [Pharo-users] Riak Interface for Pharo Smalltalk To: A friendly place where any question about pharo is welcome < pharo-users(a)lists.gforge.inria.fr> I have published the first beta version of a Pharo Smalltalk interface to Bashoâs key-value database âRiakâ: http://blog.epigent.com/2011/03/riak-interface-for-pharo-smalltalk.html Regards Runar Jordahl http://blog.epigent.com/

1 0

[Pharo-project] help about package naming conventions
by StÃ©phane Ducasse March 14, 2011

March 14, 2011

Hi I want to align all the packages to follow the convention: Announcements-Core Announcements-Help Announcements-Tests-Core Announcements-View Now what about package with a composed name: Compression-Streams I started with the package named Compression-Streams Because for me this is not Compression-Streams Collections-Tests-Streams This looks strange to me because I want to be able to load Compression-Streams without Compression-Archives because there are two different things. Stef

2 1

[Pharo-project] There is life in Mars. A post explaining current status
by Esteban Lorenzano March 14, 2011

March 14, 2011

Hi all, Several months passed without Mars news, and I'm trying to correct that (it is "some kind" a compromise to publish some news at least once a month, starting from now... so people can see our advances). I prepared a very long post explaining last months and next steps we want to make (to long to add it as a simple mail to the list). If you are interested, you can read it here: http://smallworks.com.ar/blogs/The+Martian+Chronicles/2011-03-14-The-fly-to… Cheers, Esteban

1 0

[Pharo-project] Issue 3815 in pharo: Filing in Class comments raises an error
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: ryd...@gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3815 by ryd...@gmail.com: Filing in Class comments raises an error http://code.google.com/p/pharo/issues/detail?id=3815 Broken by SourceReference changes. ChangeRecord >> fileIn directly notifies deprecated RecentMessageSet. It seems to me like the #comment:stamp: call should correctly update RecentMessageList through the SystemChangeNotifier, and the calls could simply be removed. Need external confirmation of this though, as I have not beeen involved, and have no idea what the implications/consequences of RecentMessageSet deprecation really is. PS. We need tests for fileIns of different kinds, all tests passing for 1.2 without catching stuff like this is bad :)

1 14

[Pharo-project] Issue 3445 in pharo: [Repackage] "SUnit" should be well structured
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Status: Accepted Owner: Torsten....@astares.de New issue 3445 by Torsten....@astares.de: [Repackage] "SUnit" should be well structured http://code.google.com/p/pharo/issues/detail?id=3445 Pharo 1.2beta 12280: I now reorganized the SUnit package: - introduce a SUnit-Core-X category instead of SUnit-X categories - rename SUnitGUI into SUnit-UI category - SUnit-Events becomes SUnit-Core-Announcements since announcements are used - rename ivar result in TestCaseAnnouncement into testResult since this is more consistent with ivar testCase and testSelector - method comments on TestCaseAnnouncement - class comment on TestCaseAnnouncement, TestCaseEnded and TestCaseStarted - a new "SUnit-Core" package => this has to be SAVED in Monticello - a new "SUnit-UI" package => this has to be SAVED in Monticello A help package/tutorial is in preparation ... Attachments: Repackage-SUnit-Reorganize.cs 3.8 KB

1 5

Re: [Pharo-project] Issue 3073 in pharo: A version of Compiler with support for methods with many arguments including external FFI calls - For inclusion in Pharo 1.2
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Updates: Status: FixProposed Comment #3 on issue 3073 by marcus.d...@gmail.com: A version of Compiler with support for methods with many arguments including external FFI calls - For inclusion in Pharo 1.2 http://code.google.com/p/pharo/issues/detail?id=3073 (No comment was entered for this change.)

1 0

Re: [Pharo-project] Issue 1036 in pharo: Better interrupt handler registration
by pharo＠googlecode.com March 14, 2011

March 14, 2011

Updates: Status: FixProposed Comment #7 on issue 1036 by marcus.d...@gmail.com: Better interrupt handler registration http://code.google.com/p/pharo/issues/detail?id=1036 (No comment was entered for this change.)

1 0

[Pharo-project] [Bug Tracker] fixed vs. fixedProposed...
by Marcus Denker March 14, 2011

March 14, 2011

Hi, There was always the confusion of the meaning of "fixed", which actually had no clear meaning... I therefore added some weeks ago FixProposed --> this issue has a proposal of a fix, but there is no consensus that it's good FixToInclude ---> Please add to unstable ASAP This makes it clear what the status is. I now re-tagged all "fixed" issues as "FixProposed" and removed the "fixed" status. Next step: There are far too many items tagged "1.3". I think only a very select set of items should have that tag. -> FixToInclude -> Show stoppers ("If we release tomorrow, would this be a show stopper?") -> Failing tests -> Things people are actively working on. I will re-tag items... but I will turn off Email notification so that we don't get 130 mails. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0