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

Re: [Pharo-project] [squeak-dev] Mac carbon VM goes to 4.2.4beta1U

by Jan van de Sandt

Hello John, Is it possible to update the CurlPlugin that is shipped with the Squeak Mac VM? It is great that the plugin is part of the standard VM. But the version that is shipped is quite old. Danil Osipchuk created a new version that contains valuable new functionality. For example the possibility to add custom headers to http requests. I would really like to use this feauture for Cloudfork. I think CurlPlugin-dao.23.mcz is the latest stable version of the plugin. ( http://www.squeaksource.com/CurlPlugin.html) Regards, Jan. On 4/6/10, John M McIntosh <johnmci(a)smalltalkconsulting.com> wrote: > > In order to wrap up some VM fixes that should be pushed into the Squeak 4.x > offering I've compiled up a 4.2.4beta1U VM > This will be the last 4.x series of macintosh VMs as the 5.x series gains > support. > > Someone should run the Sunit and smoke test to ensure the VM is sane. > > Follow the macintosh link from http://www.squeakvm.org/index.html > > 4.2.4b1 We update to VMMaker 168 > > Change #versionString from 3.x.x to 4.0.2. > Fix loading of image segments that are from older, but compatible > image versions. > fix bounds bug in primitiveSoundRecordSamples. > Add primitiveUtcWithOffset. > Provide an explicit imageFormatBackwardCompatibilityVersion > Merge some/*lots* of 64bit fixes > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > > > >

April 7, 2010

[Pharo-project] Bug or new feature in RB?

by Mariano Martinez Peck

Hi Lukas. I was playing around RB (actually, looking at your screencasts) and I found something weird. Steps done: 1) Go to AST, "refactoring scope" -> "package" 2) There, took class RBReplaceRule and "refactor method" -> "rename" to the method initialize 3) Proceed -> yes There you will see the list of the initialize methods that it will apply the refactor. As you can see, all classes affected are RB, BUT Behavior and CompiledMethod. This is because the package AST has extensions to both classes. But NONE of those extensions are with the initialize method, but with parseTreeFor: and parseTree, So, my question is, shouldn't only apply the refactor to the initialize method of extended packages ONLY if that method is extended ? Because otherwise I think it is a bit dangerous. What do you think ? I attach screenshot also. Cheers Mariano

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi, On 7 Apr 2010, at 10:59, Simon Denier wrote: > > On 7 avr. 2010, at 10:52, Tudor Girba wrote: > >> Hi Simon, >> >> On 7 Apr 2010, at 10:36, Simon Denier wrote: >> >>> >>> On 7 avr. 2010, at 09:17, Lukas Renggli wrote: >>> >>>>> I see what you mean, but I don't like the way it is displayed, >>>>> because it makes navigating from section to section cumbersome >>>>> and just skimming a chapter to get an overview is difficult. >>>> >>>> While writing/editing the Seaside book we figured out the following >>>> simple guidelines that worked out quite well: >>>> >>>> http://book.seaside.st/system/howto >>> >>> >>> Thanks! That's helpful. >>> >>> Adding +value:book.contents+ to create a mini-toc for the chapter >>> works ok, although perhaps this should go in the column. >> >> Please do not use that there. It will make everything complex >> afterwards. You can always use the key navigations to switch >> between pages: > > Why exactly? Because you are mixing implementation with content. > I still would like such stuff at the chapter level. I never felt the need for this, but it is doable. It is just that this won't come too fast. >> - "j" or left arrow: previous book part >> - "k" or right arrow: next book part >> - "i": table of contents >> - "p": parent book part >> >>> Doru, another missing thing in the current config is the == syntax >>> for Smalltalk highlighting >>> See http://book.pharo-project.org/book/announcements/client >> >> Ahh, my bad again. I will look into it. >> >> Cheers, >> Doru >> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "Sometimes the best solution is not the best solution." >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Simon Denier

On 7 avr. 2010, at 10:52, Tudor Girba wrote: > Hi Simon, > > On 7 Apr 2010, at 10:36, Simon Denier wrote: > >> >> On 7 avr. 2010, at 09:17, Lukas Renggli wrote: >> >>>> I see what you mean, but I don't like the way it is displayed, because it makes navigating from section to section cumbersome and just skimming a chapter to get an overview is difficult. >>> >>> While writing/editing the Seaside book we figured out the following >>> simple guidelines that worked out quite well: >>> >>> http://book.seaside.st/system/howto >> >> >> Thanks! That's helpful. >> >> Adding +value:book.contents+ to create a mini-toc for the chapter works ok, although perhaps this should go in the column. > > Please do not use that there. It will make everything complex afterwards. You can always use the key navigations to switch between pages: Why exactly? I still would like such stuff at the chapter level. > - "j" or left arrow: previous book part > - "k" or right arrow: next book part > - "i": table of contents > - "p": parent book part > >> Doru, another missing thing in the current config is the == syntax for Smalltalk highlighting >> See http://book.pharo-project.org/book/announcements/client > > Ahh, my bad again. I will look into it. > > Cheers, > Doru > >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi Simon, On 7 Apr 2010, at 10:36, Simon Denier wrote: > > On 7 avr. 2010, at 09:17, Lukas Renggli wrote: > >>> I see what you mean, but I don't like the way it is displayed, >>> because it makes navigating from section to section cumbersome and >>> just skimming a chapter to get an overview is difficult. >> >> While writing/editing the Seaside book we figured out the following >> simple guidelines that worked out quite well: >> >> http://book.seaside.st/system/howto > > > Thanks! That's helpful. > > Adding +value:book.contents+ to create a mini-toc for the chapter > works ok, although perhaps this should go in the column. Please do not use that there. It will make everything complex afterwards. You can always use the key navigations to switch between pages: - "j" or left arrow: previous book part - "k" or right arrow: next book part - "i": table of contents - "p": parent book part > Doru, another missing thing in the current config is the == syntax > for Smalltalk highlighting > See http://book.pharo-project.org/book/announcements/client Ahh, my bad again. I will look into it. Cheers, Doru > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Simon Denier

On 7 avr. 2010, at 09:17, Lukas Renggli wrote: >> I see what you mean, but I don't like the way it is displayed, because it makes navigating from section to section cumbersome and just skimming a chapter to get an overview is difficult. > > While writing/editing the Seaside book we figured out the following > simple guidelines that worked out quite well: > > http://book.seaside.st/system/howto Thanks! That's helpful. Adding +value:book.contents+ to create a mini-toc for the chapter works ok, although perhaps this should go in the column. Doru, another missing thing in the current config is the == syntax for Smalltalk highlighting See http://book.pharo-project.org/book/announcements/client -- Simon

April 7, 2010

Re: [Pharo-project] Handle Close Event in Image - necessary for 1.0?

by Henrik Johansen

On Apr 6, 2010, at 10:48 19PM, StÃ©phane Ducasse wrote: > Torsten I appreciate your effort but we can only do what can be done in the time > we can allocate to do a task if you see what I mean. > I cannot test on windows because we do not have a windows machine. We are doing an incredible > amount of work but we cannot do more than it is reasonable to do. > > Then in freeze time this is freeze time. we will try to get shorter iteration cycles and this is not > by delaying 1.0 that we are making progress on that front. > > And this is not by saying that pharo "will be less quality than" ... more or less that it helps. > > So 1.0 will be like it can. And if people bash us this is ok too. > You remember a while ago one guy asked who is ready to pay 10 Euros per month to have a > better pharo and we got 6 persons.... > >> However I still believe that fixing this in 1.0 would not only >> be a plus - it will also prevent questions regarding this >> new problem since people WILL use newer VM's after the >> first 1.0 release of Pharo and then instantly step into the problem! >> >> >> And it is not a Windows specific problem as Stef thinks it is. >> >> Bert requested John today (see [1]) to change the default for Mac too ... > > TODAY. Imagine I was painting my house.... and this evening this would have to be fixed? > When is the last time that a bug that annoys you on windows got fixed in one day? > because for me on mac so far it took months. > >> so if you upgrade your Mac VM for whatever reason (maybe to do >> 1.1 work or since you need a newer VM for a commercial project) >> then you will step into this with the 1.0 image. > > Yes and since you are a good pharoers you will know and you will understand > and help us and help yourself. I've put some slices based on the .cs in the inbox, one for 1.0 and one for 1.1. (quitSession was moved to WorldState in 1.1, and some other minor diffs) I've also tested and can confirm they work with the newest Windows VM, not sure about the behavior on Linux, which apparently was updated as well. Cheers, Henry

April 7, 2010

Re: [Pharo-project] CollabActive book :)

by Tudor Girba

Hi, The toolbar is now available. Cheers, Doru On 7 Apr 2010, at 01:14, Simon Denier wrote: > > Also what is missing is the handy toolbar which provides buttons to > decorate the text with Pier syntax. Useful when you are not a pro of > the syntax. But I don't know how to install this widget. > -- www.tudorgirba.com "Value is always contextual."

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by laurent laffont

On Wed, Apr 7, 2010 at 10:05 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > laurent laffont a Ã©crit : > > > The tinyBenchmarks are not as good as Exupery one, but this vary a lot >> depending on the CPU. >> > > Any reason not to propose Exupery? > The idea is to propose the squeak vm 2151 I provide (source) + Exupery VM (binary - alternate link). The major problem with Exupery VM is that nobody but Bryce (as far as I know) can build it. I'm still not able to do it:(. That means no package for Linux distributions. Another one is failing tests. Laurent Laffont > > Hilaire > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 7, 2010

Re: [Pharo-project] Linux Pharo VM on Pharo website

by Hilaire Fernandes

laurent laffont a Ã©crit : > The tinyBenchmarks are not as good as Exupery one, but this vary a lot > depending on the CPU. Any reason not to propose Exupery? Hilaire

April 7, 2010