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

[Pharo-project] Pharo for iOS

by Dennis Schetinin

What is the state of the art and nearest perspectives of using Pharo/Squea (or maybe some other Smalltalk implementation) for iOS development? And does Apple officially allow to Smalltalk-based applications? -- Dennis Schetinin

Sept. 22, 2011

[Pharo-project] Integrating Changes in 1.4 that require a new VM

by Marcus Denker

Hi, There are two changesets waiting for integrating in 1.4 that have serious consequences: - Ephemerons. The VM level changes are in the Cog VMs build on Jenkins, but have not been integrated in the VMMaker codebase. http://code.google.com/p/pharo/issues/detail?id=4265 - Finalization code checks for #hasNewFinalization This is true in the current VMs build in Jenkins, but in older VMs this is not in. http://code.google.com/p/pharo/issues/detail?id=4483 There are two options: a) integrate in b) not integrate it a) means that the image runs on older VMs, too. b) means we accept that we can never improve anything for real. There will be more changes coming... e.g. imagine we have a Vector Graphics Canvas as some point next year... what will we do? use it or not use it to stay compatible? Marcus -- Marcus Denker -- http://marcusdenker.de

Sept. 22, 2011

[Pharo-project] [update 1.4] #14160

by Marcus Denker

14160 ----- Issue 4844: Add some comments on TickList* class http://code.google.com/p/pharo/issues/detail?id=4844 Issue 4378: Bad size of TasklistMorph preview with large titles http://code.google.com/p/pharo/issues/detail?id=4378 -- Marcus Denker -- http://marcusdenker.de

Sept. 22, 2011

Re: [Pharo-project] [1.4] Doing a #condenseChanges in #14158

by StÃ©phane Ducasse

>> >> Noooooooooo, please please don't... >> Method history is so much more useful than 20 extra MB's on my HD :S >> >> This is /not/ a dichotomy. For my image I wrote a condenseSources that preserves history. It edits out duplicates, and cuts off branches in the history that lead nowhere. So at the end you get all the versions of each method that are ancestors of the current version. I can email you the code and you could consider making it the default. Let me know. >> >> >> Cheers, >> Henry >> >> >> >> >> -- >> best, >> Eliot >> > What about having a changes file per release? Each .changes file records its predecessor file - including md5checksum. The search just parses multiple files. > .changes.1.0 > .changes.1.1 > .changes.1.2 > .changes.current > > In theory, anyone can decide on an individual basis how far back to keep history. An image could be shrunk for a client deliverable but easily added back in to troubleshoot the client's live image. ideally we would love to have a little db can branch to existing one or distributed one and keep all the non redundant changes. Now it requires a lot of work. Stef

Sept. 22, 2011

Re: [Pharo-project] thoughts of a tired but happy man...

by StÃ©phane Ducasse

On Sep 21, 2011, at 10:44 PM, Laszlo Zsolt Kiss wrote: > Dear Stef. > The Hungarians have a saying: > "We cry together and laugh together." :) > If you tired, think about my son Patrik (4 and half years old) , who every week "working" with Pharo. I have one of nearly 5 and he is so energetic :) > Energy is important, therefore we are sending a big portion of the good energy on the occult roads.:) > > Best regards: > > LÃ¡szlÃ³ Zsolt

Sept. 22, 2011

Re: [Pharo-project] thoughts of a tired but happy man...

by StÃ©phane Ducasse

On Sep 21, 2011, at 11:34 PM, mike(a)sharedlogic.ca wrote: > Hi Stef, > > From one of those who manages to eke out a living using Pharo, a very big "Thank You" to you all. I'm happy :) > > Best regards, > > Mike > > > Sent from my BlackBerry device on the Rogers Wireless Network > > -----Original Message----- > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Sender: pharo-project-bounces(a)lists.gforge.inria.fr > Date: Wed, 21 Sep 2011 21:45:50 > To: An open mailing list to discuss any topics related to an open-sourceSmalltalk<Pharo-project(a)lists.gforge.inria.fr> > Reply-To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] thoughts of a tired but happy man... > > Since I work too much I'm tired and when I'm tired I have strange thoughts :) > Let us see what they are (if of any interest) > > I do not really know if people realize that in fact we could be payed for building our own private little toy > and we could publish cool papers, looks smart and look at ourselves quite proudly in the mirror the morning. > The look of the guy that accomplished his duty and is quite cool too. > This would be a perfect life: a full life of a brillant researcher having fun with his little toys. Students > of course would have fun with us and we would be a happy family. Imagine we could even write > books, little books and everybody would be happy. flower, butterflies and the rest... > > Now we decided to do pharo. Why: because we want other people to be able to make a living out of it. > > I'm not sure that people deeply understand that. We do pharo (of course so that we can experiment crazy ideas > but we could have probably do that better in Scheme from my experience) because we want others to be empowered > and in the position of making money with it and changing/controlling their life because they are not forced to use > something that they do not like. > > So this means that each time we spend time on it (we = the community) we make sure that others or the community > can feed their kids based on our labor. For me this is a cool task and I enjoyed doing it even if sometimes my moral > is low because I would like to go much much faster. > > You could think that we should have better done to have fun > with our little toys and sometimes I think that yes this could be true. But we decided that it was more rewarding > to build real systems with customers that are not always happy, have bugs. So when you have strong expectations, > bold statements about Pharo think also that this is the simple work of people most of the time not payed to do it and that nicely > share it. > > We know where we want to go, sometimes the system does not get the shape we want. but each little peebles after the other > one we shape it. Now you can also help to make it better. > > Stef > >

Sept. 22, 2011

Re: [Pharo-project] Clarifying and optimizing Integer>>asFloat

by StÃ©phane Ducasse

Hello nicolas On Sep 22, 2011, at 12:17 AM, Nicolas Cellier wrote: > It's too long for a mail, but all explained here: > http://smallissimo.blogspot.com/2011/09/clarifying-and-optimizing.html > > Optimizing such kernel message is important - for example when reading > a file of floats... > Which version do you prefer ? > Shall comments be that long ? YESSSSS :) We love good comments! And comments should be close to the code else they rot. There is no problem having long nd precise comments that empower the reader. > Any other opinion ? One important question is what is the impact of the hardware dirven solution on bit identical computation on different machine. I would do the following: use the smalltalk - bit identical idea all the times provide one methods for people knowing that they want to get faster but potentially different floats on different platform. Does it make sense? Stef > > Nicolas >

Sept. 22, 2011

[Pharo-project] local metacello?

by HwaJong Oh

Hi, Squeaksource is down at this moment. While wating, I send this question. Can Metacello work locally and remotely to squeaksource or other 3rd server? Stack up some versions locally and later sync them with squeaksource? HwaJong Oh -- View this message in context: http://forum.world.st/local-metacello-tp3832544p3832544.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 22, 2011

Re: [Pharo-project] [1.4] Doing a #condenseChanges in #14158

by btc＠openInWorld.com

Sept. 21, 2011

[Pharo-project] Clarifying and optimizing Integer>>asFloat

by Nicolas Cellier

It's too long for a mail, but all explained here: http://smallissimo.blogspot.com/2011/09/clarifying-and-optimizing.html Optimizing such kernel message is important - for example when reading a file of floats... Which version do you prefer ? Shall comments be that long ? Any other opinion ? Nicolas

Sept. 21, 2011