- Pharo-dev - lists.pharo.org

[Pharo-project] projects to migrate/test on 2.0

by Christophe Demarey

Hi stef here is a list of the project we should validate for 2.0 Gofer spec project: 'Gofer Core' with: [ spec className: 'ConfigurationOfGofer'; versionString: '1.0-baseline'; loads: #('Core'); file: 'ConfigurationOfGofer'; repository: 'http://www.squeaksource.com/MetacelloRepository'; repository: 'http://seaside.gemstone.com/ss/metacello' ]; Prof Stef spec className: 'ConfigurationOfProfStef'; versionString: '1.0-baseline'; file: 'ConfigurationOfProfStef'; repository: 'http://www.squeaksource.com/MetacelloRepository'

Feb. 21, 2013

Re: [Pharo-project] please test 2.0

by Sven Van Caekenberghe

Hi Yanni, On 20 Feb 2013, at 22:23, Yanni Chiu <yanni(a)rogers.com> wrote: > On 19/02/13 12:22 PM, Esteban Lorenzano wrote: >> >> We are almost there for the release, but we still need a little >> effort more. Would be terrific if everyone of you took the latest 2.0 >> image and test it with your usual workflows (we cannot imagine all, >> they are infinite :) > > I usually keep a build tracking the upcoming Pharo release, but when I tried to do it during early Pharo-2.0 development, the code was not stable. Then I never got back to it. Here's what happened, when I tried to build with the newest version. Thanks for testing, thanks for the feedback. > First try: "Notice: Your VM is too old for this image. Please download the latest VM." > > Get latest coglinux, from http://www.mirandabanda.org/files/Cog/VM/ > > Second try: "Can't infer base LD_LIBRARY_PATH. Aborting. Try adding a line for /lib/i686/cmov/libc.so.6 ..." > > Patch squeak shell script with a case for "/lib/i686/cmov/libc*" > > Third try: No complaint about LD_LIBRARY_PATH, but still says "VM is too old ..." > > Switch to a CogVM (early version of PharoVM) that was lying around. This is a bit to be expected when you use older VMs, the one-click or designated Pharo (NBCog) VMs would have prevented these issues. > More tries: > > Can't load Seaside. Update to newer seaside31.st script from https://github.com/renggli/builder/tree/master/scripts > > Magritte3/Pier3 has deprecations and undefined class. > > Revert to trying Seaside30. Get: > *** Warning: Warning: This package depends on the following classes: > BlockContext > You must resolve these dependencies before you will be able to load these definitions: > renderOn: > > Go back to trying Magritte3/Pier3 on Seaside31 again. Ignore the deprecations, find: FileSystem-Legacy, at: http://smalltalkhub.com/mc/dh83/fisleg/main > Can now load Pier3 into Pharo-20558. > > Figure out where to get the latest Zinc-Seaside. (Found at http://www.squeaksource.com/ZincHTTPComponents) Start Seaside, go to Pier link, get deprecation warnings about #includesSubString:. Try to disable warnings in System Settings. Still get warnings in webpage. Change to #includesSubString: to not call #deprecated:on:. Now, can see default Pier page. It will be a while before all third party packages are properly ported to Pharo 2.0. Many are, but that depends mostly on their authors. Now, Seaside 3.1 and friends will load and work proper on Pharo 2.0, it is just not an out-of-the-box it-just-works experience. The #includesSub[S|s]tring: issue is easy to solve, it just requires a decision on the part of the Seaside developers. See http://forum.world.st/Broken-build-because-of-use-of-includesSubstring-tt46… There also seem to be some technical reasons why a Metacello Configuration is not yet there. I guess that user pressure, once 2.0 is out, is the only thing that will make a difference. These things sometimes go slowly. This is all open source. > Next step, try to load my custom codeâ¦ Let us know how it goes ! Regards, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 21, 2013

[Pharo-project] call for speakers - pharoconf (april 2, 3) / mooseday (april 4) - bern, switzerland

by Tudor Girba

Hi, During April 2-4 we will organize a PharoConf and a MooseDay in Bern, Switzerland. Mark the day and join us. The participation will be free of charge. The conference will focus on interactivity and exchange, and will feature experience report talks, tutorials, show-us-your-project sessions and open discussions. We are looking for speakers: TUTORIAL These sessions will walk the audience through a piece of technology. Target duration: 30min - 60min. Example topics: - ZeroConf continuous integration builds - Building vectorial interfaces with Athens - Building UIs with Spec - New development tools (Fuel/Tanker, Glamorous Debugger, Nautilus ...) - Manipulating databases in Pharo (Riak, MongoDB ...) - Visualizing data (Roassal, EyeSee ...) TALK These sessions expose a topic that is not necessarily technical. Target duration: 30min - 60min. Example topics: - Experience of using Pharo to solve business problems - Experience of using Pharo and Moose to solve various technical problems (not necessarily related to Smalltalk) - Successes in marketing Pharo-based solutions - Future directions for Pharo or Moose SHOW-US-YOUR-PROJECT These sessions will feature short presentations of the projects (7-10 minutes) followed by open-space demos. Example topics: - The Glamorous Debugger - Nautilus - Analysis tools like Softwarenaut or Carrack - Fuel/Tanker - ... Please send us your submissions by email at tudor(a)tudorgirba.com. Cheers, Doru on behalf of the organizers -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Feb. 21, 2013

Re: [Pharo-project] Fwd: PositionableStream>>last

by Damien Cassou

On Thu, Feb 21, 2013 at 5:11 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> That method shouldn't even exist. You're right it's buggy. Very likely >> (hopefully) to be unused too. Thanks for spotting, should be gone soon :) another possibility is that the comment is buggy, not the code or method name. The "last" element can be understood as the "last element before the current position", or "the last element we just read". -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 21, 2013

Re: [Pharo-project] Weird behavior in Nautilus when doing a method rename

by Ben Coman

For me the issue is not so much whether there there is another way to rename, but that it is "an _unexpected_ refactoring in disguise" -ben stephane ducasse wrote: > to rename a method without refactoring: just click on the method and in the method pan change its name and recompile > > Stef > > On Feb 20, 2013, at 11:25 AM, phil(a)highoctane.be wrote: > > >> Yes, but the rename is *not* in the refactoring menu. It is *below* >> the refactoring menu. >> So, it is an unexpected refactoring in disguise... >> >> There was a simple rename in 1.4 I think. Maybe can we get that one >> back (in 3.0 of course...) >> >> Phil >> >> 2013/2/20 Fernando Olivero <fernando.olivero(a)usi.ch>: >> >>> Hi, i had the same misconception once, but i recall Lukas pointed out >>> that the refactoring engine is built on the original refactoring's >>> from Fowler's book, and implemented in Smalltalk by Roberts and >>> Johnson [1]. >>> >>> So the semantics of the refactoring are preserved in the implementation. >>> >>> If you just want a method rename, not a method refactoring rename, >>> maybe is best have an option for that in the menu [2]. >>> >>> >>> Fernando >>> >>> [1] http://st-www.cs.illinois.edu/users/droberts/tapos.pdf >>> [2] or use a better widget for editing methods, than a simple code >>> editor within the pane of the browser, as in Gaucho..which i'm working >>> on. >>> >>> On Wed, Feb 20, 2013 at 11:03 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> and you are right, scoped browsing is a very powerful feature that can be tricky to newcomers... but at least now with nautilus it is there, as first option (in OB it was there, but more or less hidden in a submenu)... >>>> It is a small step, but is something... and well... we can improve in next releases, one step at a time :) >>>> >>>> Esteban >>>> >>>> On Feb 20, 2013, at 10:52 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>> >>>> >>>>> Yes, thanks, I figured that out. A newcomer wouldn't... and renaming >>>>> is pretty common. >>>>> >>>>> What will happen is that people will remove the method and recreate a new one. >>>>> Version history will then go away. >>>>> >>>>> Or is the system smart enough to find out about these things? >>>>> >>>>> Phil >>>>> >>>>> 2013/2/20 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>>> hi, >>>>>> >>>>>> yes, you are right.. but that is a "nice to have", not a bug... so it will wait to 3.0 :) >>>>>> In the mean time, you can do a scoped rename: you select the packages you want, then right click and "browse scoped", then you apply you rename, and it will apply the refactor in the scoped selection, not all the image. >>>>>> >>>>>> cheers, >>>>>> Esteban >>>>>> >>>>>> On Feb 20, 2013, at 10:21 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>>>> >>>>>> >>>>>>> Well, look at the screenshot then tell me that this is what I want. >>>>>>> >>>>>>> It is definitively *not* what I want. Especially unchecking that >>>>>>> endless list of methods. >>>>>>> >>>>>>> Adding a "Uncheck all" "Check all" button to the Changes Browser list >>>>>>> would help... >>>>>>> >>>>>>> Regards >>>>>>> Phil >>>>>>> >>>>>>> 2013/2/20 Camillo Bruni <camillobruni(a)gmail.com>: >>>>>>> >>>>>>>> there is 1 certain bug, that is that you cannot see the changes of the refactoring: >>>>>>>> >>>>>>>> https://code.google.com/p/pharo/issues/detail?id=7547 >>>>>>>> >>>>>>>> the rest I would consider a bug as well. But in the terms of refactoring it might >>>>>>>> be "valid". It does preserve behavior by renaming also all implementors. >>>>>>>> >>>>>>>> How about this reasoning: >>>>>>>> >>>>>>>> Rename method >>>>>>>> => rename all senders (since you refactor) >>>>>>>> => you have to rename all implementors as well since you renamed all send sites >>>>>>>> otherwise you'll run for sure into a DNU >>>>>>>> >>>>>>>> I think I just convinced myself :D >>>>>>>> >>>>>>>> On 2013-02-20, at 09:26, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >>>>>>>> >>>>>>>>> I was doing a Refactoring>rename of the initialize method in Nautilus >>>>>>>>> for the ClassMethodBrowser and then the changes browser proposed me to >>>>>>>>> change all classes with initialize. WTF? >>>>>>>>> >>>>>>>>> Phil >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> <PharoScreenshot.3.png> >>>>>>> >>>>>> >>>> > > > >

Feb. 21, 2013

Re: [Pharo-project] Continuing weirdness with SS3.gemstone.com and Monticello in Pharo 2.0

by Igor Stasenko

when image freezes and not responsible anymore, VM can still respond to kill -SIGUSR1 <vm-pid> which will print the stack trace on console. this can help with determining the cause of problem. -- Best regards, Igor Stasenko.

Feb. 21, 2013

[Pharo-project] Fwd: PositionableStream>>last

by Sean P. DeNigris

>From Squeak list: Bert Freudenberg wrote >> I am reaing Class code,PositionableStream>>last >> >> last >> "Return the final element in the receiver" >> >> ^ collection at: *position* >> >> why not collection at: *readLimit*? > > That method shouldn't even exist. You're right it's buggy. Very likely > (hopefully) to be unused too. Thanks for spotting, should be gone soon :) > > - Bert - -- View this message in context: http://forum.world.st/Fwd-PositionableStream-last-tp4671176.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 21, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by Dale Henrichs

Feb. 20, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by Dale Henrichs

stef, 1.0-beta.32 is the Metacello Scripting API and that is definitely not working in Pharo 2.0 ... 1.0-beta.31.1.5 from September is the current stable version of Metacello for all platforms with the exception of Pharo2.0 (which has already been discussed) ... AFAIK Metacello was functioning correctly with 1.0-beta.31.1.5 in September when the code was released... Dale ----- Original Message ----- | From: "stephane ducasse" <stephane.ducasse(a)free.fr> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, February 20, 2013 10:29:43 AM | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | | I could not load in Pharo 2.0 latest | | (ConfigurationOfMetacello project version: '1.0-beta.32') load: 'Tests' | | Stef |

Feb. 20, 2013

Re: [Pharo-project] spec className?

by Dale Henrichs

Feb. 20, 2013