September 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Rounding float question again

by Denis Kudriashov

Hello. I know there are many similar questions. Maybe somebody give me fast answer. 146.015 roundTo: 0.01 => 146.01 I guess internal representation of 146.015 is something like 146.014999999999... That's why rounding result is 146.01 But how I can round arbitrary float my math root? How to fix my example to get 146.02? Best regards, Denis

Sept. 7, 2012

Re: [Pharo-project] integration/review process

by Nicolas Cellier

That would be much much better than what we currently have with mix of code agnostic google issue tracker + ST only MC repository... Another plus is also to make code visible/searchable/indexable outside our community, be it with less specialized (not so less powerfull) IDE. Nicolas 2012/9/7 Frank Shearar <frank.shearar(a)gmail.com>: > On 7 September 2012 11:52, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> previously: [Pharo-project] nil key in last literal in instance side methods (reproducible) >> >>> No, I'm just suggesting a poor man's simple diff in a mailing list, >>> like squeak trunk. >>> -1) inbox diff : you open a review to the whole community for comments, >> >> ok, why not on a separate mailing list that might make sense >> >>> -2) commit phase (whatever the checks you perform now are unchanged, >>> except you have to take above review into account) >>> -3) trunk diff : you open a last chance review (or post mortem >>> analysis) to retract/correct commits >> >> that is (almost) up and running with our github export: >> https://github.com/PharoProject/pharo-core >> >>> It's totally informal, and why would it work? You have to answer this >>> question first: >>> - how many people have ubiquitous web access to read the code and >>> qualified enough to emit a useful comment? >>> - how many people are downloading an image, updating to some version, >>> opening a MC browser, browsing the diffs? >>> >>> You are proposing a much more ellaborated process to review code >>> before integration. >>> I agree, this information belongs to issue tracker. >>> But formalizing and programming this process is involving (think about >>> concurrent solution, roles, requests/answers timelines etc...) >>> As you said, who will do it? >> >> >>> From pragmatic POV, I prefer a light process that provides some help, >>> than no help at all (which is close to what you get with current state >>> of issue tracker). >>> The code producing the diff and sendig the mail already exist, (you'll >>> have to handle SLICE though)... Bonus: it's Smalltalk code. >>> >>> If you prefer to wait for something better, then let's wait... >> >> well the solution would be to simply switch to git for the whole version >> management. github.com provides an excellent example of how to deal with >> you aforementioned issues. >> >> - pull requests >> - single commits >> - full history >> >> plus >> - everything can be commented / annotated from within the website => 0 setup needed >> >> >> so for me something like github is the future for development. > > And in answer to Nicolas' comment about ubiquitous web access, GitHub > can mail interested parties when something interesting happens - a new > issue, issue state change, new comments - and you can reply to those > via email. > > frank >

Sept. 7, 2012

Re: [Pharo-project] git support

by Max Leske

Runs on 1.4 and 2.0 as long as you manually backport the newest filesystem packages (I've got both images on my machine and it works fine). On 07.09.2012, at 15:32, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2012-09-07, at 15:29, Dale Henrichs <dhenrich(a)vmware.com> wrote: >> Does FsGit run in Pharo1.4 or is ti Pharo2.0 only ... if it ran in Pharo1.4 I would start using it in my daily work:) > > so that's a motivation to get it up and running in 1.4 :P > With FileSystem being backported I don't see any immediate problems ahead... > >> ----- Original Message ----- >> | From: "Camillo Bruni" <camillobruni(a)gmail.com> >> | To: Pharo-project(a)lists.gforge.inria.fr >> | Sent: Friday, September 7, 2012 6:22:44 AM >> | Subject: Re: [Pharo-project] git support >> | >> | >> | On 2012-09-07, at 15:13, Dale Henrichs <dhenrich(a)vmware.com> wrote: >> | > Cami, >> | > >> | > What kind of work needs to be done for the Cypress-compatible >> | > format? I've done a couple of different implementations already:) >> | > So I can definitely do one more ... If you give me the name of the >> | > class that is the entry point for read/write then I can take it >> | > from there ... >> | >> | Since you ported it to the new FileSystem I don't have to change much >> | :) >> | The git stuff works on top of the new FileSystem, thus completely >> | transparent to >> | whatever FileOperations you used. >> | >> | - load filetree >> | - use filetree instead of my own git exporter >> | - use filetree for recreating mc snapshots >> | >> | I will try to hook that up this weekend, then I need busy testers :P >> | >> | >> | > Metacello integration is also among the "missing" from the >> | > perspective that I want some real users using the Metacello >> | > Preview[1] and giving me feedback[2] before I make a general >> | > release. >> | >> | I guess we could push some work to Versionner? That would then have >> | to interact >> | with the low-level git filesystem to set the tags / commits >> | >> | > Also keep in mind that we will need to be inventing the Smalltalk >> | > workflow for git... >> | >> | yes :) I hope to get closer to that once I have a running >> | implementation in pharo.. >> | >> | > Dale >> | > >> | > [1] >> | > https://github.com/dalehenrich/metacello-work/blob/master/README.md >> | > [2] https://groups.google.com/group/metacello/ >> | > >> | > ----- Original Message ----- >> | > | From: "Camillo Bruni" <camillobruni(a)gmail.com> >> | > | To: "Pharo-project(a)lists.gforge.inria.fr Development" >> | > | <pharo-project(a)lists.gforge.inria.fr> >> | > | Sent: Friday, September 7, 2012 4:15:46 AM >> | > | Subject: [Pharo-project] git support >> | > | >> | > | who will help? >> | > | >> | > | max and I, stimulated by ESUG, worked on the latest version of >> | > | FS-Git >> | > | to make it stable again. >> | > | we are very close to have a complete set of git tools written in >> | > | pharo ready! >> | > | >> | > | missing >> | > | ======= >> | > | - a better mc integration >> | > | - a cypress compatible fileout format >> | > | - complete interaction with the git protocol >> | > | - a direct way to commit stuff >> | > | >> | > | as always my time is somewhat limited as well and we're the only >> | > | two >> | > | developers working on it... >> | > | >> | > | The current work is available here: >> | > | http://ss3.gemstone.com/ss/FSGit-Experimental.html >> | > | https://github.com/dalehenrich/FSGit >> | > | >> | > | best >> | > | cami >> | > | >> | > >> | >> | >> | >> > >

Sept. 7, 2012

Re: [Pharo-project] after object create callback?

by sergio_101

thanks, guille.. let me check to see if i am joined up there.. On Fri, Sep 7, 2012 at 9:44 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > In Pharo, when an object is created, the #initialize message is sent to it > automatically. You can create an #initialize method in your class and put > whatever you want in it :). > > BTW, I copy this question to the pharo_users mailing list, since it looks a > more appropiate place for it. > > Cheers, > Guille > > > On Fri, Sep 7, 2012 at 3:29 PM, sergio_101 <sergio.rrd(a)gmail.com> wrote: >> >> hey, all.. >> >> i was wondering how to implement an 'after_create' callback in smalltalk.. >> >> the idea is, immediately after creating an object, some predefined >> methods get called. >> >> any ideas? thanks! >> >> >> -- >> ---- >> peace, >> sergio >> photographer, journalist, visionary >> >> http://www.ThoseOptimizeGuys.com >> http://www.CodingForHire.com >> http://www.coffee-black.com >> http://www.painlessfrugality.com >> http://www.twitter.com/sergio_101 >> http://www.facebook.com/sergio101 >> > -- ---- peace, sergio photographer, journalist, visionary http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 335 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

Re: [Pharo-project] after object create callback?

by Guillermo Polito

Hi! In Pharo, when an object is created, the #initialize message is sent to it automatically. You can create an #initialize method in your class and put whatever you want in it :). BTW, I copy this question to the pharo_users mailing list, since it looks a more appropiate place for it. Cheers, Guille On Fri, Sep 7, 2012 at 3:29 PM, sergio_101 <sergio.rrd(a)gmail.com> wrote: > hey, all.. > > i was wondering how to implement an 'after_create' callback in smalltalk.. > > the idea is, immediately after creating an object, some predefined > methods get called. > > any ideas? thanks! > > > -- > ---- > peace, > sergio > photographer, journalist, visionary > > http://www.ThoseOptimizeGuys.com > http://www.CodingForHire.com > http://www.coffee-black.com > http://www.painlessfrugality.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > >

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 334 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» linux - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 333 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Sept. 7, 2012