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

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by Esteban Lorenzano

he, we already have something A LOT better: Filesystem. I would like it to become the default Pharo file manager :( El 04/01/2011, a las 7:10p.m., Igor Stasenko escribiÃ³: > On 4 January 2011 23:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> Yes, 4.2.5 and exuperi both has UnixOSProcessPlugin as default (and I understand that, they are very needed :) ) >> > Err.. i asked about AioPlugin. > > Yes, OSProcessPlugin is quite useful , since with it we can perform > some OS-specific tasks directly from smalltalk code. > > Someday it will rock, especially when we will have something better > than FileDirectory & friends :) > >> Cheers, >> Esteban >> >> El 04/01/2011, a las 3:15p.m., Igor Stasenko escribiÃ³: >> >>> On 4 January 2011 17:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> On Jan 4, 2011, at 4:25 AM, David T. Lewis wrote: >>>> >>>>> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>>>>> Hello Everyone, >>>>>> So, long time squeaker, first time pharo(er ?). Please don't hold this against me ;) >>>>>> >>>>>> I am trying to get CommandShell loaded into Pharo (using the Seaside Image) via Monticello. I have tried this on Pharo 1.1/1.1.1/1.2 for the record (same thing). I skip past the MVC/Morphic errors about PluggableList etc, and I can get the command shell to pop-up, however, two things happen; >>>>>> >>>>> >>>>> The CommandShell package on SqueakSource is also now broken down >>>>> into sub-packages, so you can load the individual parts if you want. >>>>> But just proceding through the MVC warnings as you did is harmless. >>>>> >>>>>> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >>>>> >>>>> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >>>>> warning when running on a Mac. But as you say, it's just a warning. >>>> >>>> I imagine that we will see that with igor and the automatic build too. >>>> >>> >>> was this plugin included into standard vms once before? because >>> currently its not >>> and i don't remember if i built VMs it . >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 4, 2011

Re: [Pharo-project] [Vm-dev] VM Benchmarks (Was: Re: [squeak-dev] [4.2] - VM <-> image release coordination)

by Stefan Marr

Hi: On 04 Jan 2011, at 23:40, Mariano Martinez Peck wrote: > On Tue, Jan 4, 2011 at 11:35 PM, Stefan Marr <squeak(a)stefan-marr.de> wrote: > Hi Igor: > > On 04 Jan 2011, at 22:40, Igor Stasenko wrote: > > > Okay, how about creating a separate > > VMBenchmarks repository > > and putting VMBenchmarks package there? > > Sure, sounds good. There are also the Systems benchmarks at http://www.squeaksource.com/PharoBenchmarks. > > > So, at least, I was able to run all benchmarks :) > > However, it still needs cleaning, improvement, testing, blah. But it is a good start point I think. Well, I am not to sure about the general value of those benchmarks. There are many microbenchmarks which do not tell you a lot. All those test* things. And well, their value for testing is also questionable. They only can help you to identify where it goes *boom* and crashes the VM, but they do not actually assert for anything. Also not sure what the value of Slopstone and Smopstone (names from the top of my head might be slightly different) is nowadays. The compiler benchmark is a reasonable application benchmark. Would be good to have a few others in that collection, too. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 4, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by Sean P. DeNigris

Fix in inbox SLICE-Issue-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1 Added comments for TextMorph's #autoFit: and #wrapFlag: -- View this message in context: http://forum.world.st/Issue-3506-in-pharo-TextMorph-s-autoFit-and-wrapFlag-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 4, 2011

[Pharo-project] Generators for Pharo Xmax wish)

by Ralph Boland

I earlier posted a Xmas wish that Pharo add generators (steal the generators code from Squeak). No one appeared to be familiar with them. The generators code was added to Squeak by Andreas Raas. The class Generator can be found in Squeak as a subclass of Stream. It's about 140 lines of code and, as I said before, is really useful and needed in order for me to port some of the packages I am developing from Squeak to Pharo. Class Generator is tested in class GeneratorTest which also serves as examples of uses of Generators. So please, someone go steal the code! And stealing is easy. For example I stole the following comment on class Generator directly from the class comment: " A Generator transforms callback interfaces into stream interfaces. When a producer algorithm provide results as callbacks (blocks) and a consumer algorithm expects streamable input, a Generator transforms one into the other, for example: | generator | generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g yield: prime]]. [generator atEnd] whileFalse:[Transcript show: generator next]. " Regards, Ralph Boland

Jan. 4, 2011

[Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3506 by sean.p.denigris: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 If you fill an issue for the first time, please read "How to report bugs" at http://www.pharo-project.org/community/issue-tracking Pharo image: Core 1.2 12272 TextMorph's #autoFit: and #wrapFlag: are horrendously confusing. They are probably badly named, but at minimum deserve better comments.

Jan. 4, 2011

Re: [Pharo-project] [Vm-dev] VM Benchmarks (Was: Re: [squeak-dev] [4.2] - VM <-> image release coordination)

by Mariano Martinez Peck

On Tue, Jan 4, 2011 at 11:35 PM, Stefan Marr <squeak(a)stefan-marr.de> wrote: > Hi Igor: > > On 04 Jan 2011, at 22:40, Igor Stasenko wrote: > > > Okay, how about creating a separate > > VMBenchmarks repository > > and putting VMBenchmarks package there? > > Sure, sounds good. There are also the Systems benchmarks at > http://www.squeaksource.com/PharoBenchmarks. > > yes! few months ago I commited this: " Several fixes to Benchmark. Now you can run for example: Benchmark testStandardToFile: (FileStream forceNewFileNamed: 'mariano'). " So, at least, I was able to run all benchmarks :) However, it still needs cleaning, improvement, testing, blah. But it is a good start point I think. Cheers Mariano > One question would be what to include in such a benchmark suite. > And another question how to design the benchmark harness. > > I need something (and if you are going to automate it, you probably, too) > which is scriptable from the command line. > My harness registers itself in the startup list and then looks for the > command line arguments to choose a benchmark class. > > Best regards > Stefan > > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr <http://soft.vub.ac.be/%7Esmarr> > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

Jan. 4, 2011

[Pharo-project] Help system for pharo [WAS ] Re: ConfigurationOfPharo: now with Mocketry, Autotest, XMLSupport and Helps

by Mariano Martinez Peck

On Tue, Jan 4, 2011 at 10:46 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi, > > I've updated ConfigurationOfPharo 1.2-beta2: > Added: > - Mocketry > - XMLSupport > - Autotest > - Shortcuts-Help > > more tests and Help. > > Excellent!!!! :) > I've put methods in categories. > > Can someone check ? > > For independent Help packages, shouldn't we create a > ConfigurationOfPharoHelp ? > > Uhh this is a good question....let me write what it just came to my mind: - For external packages (external to PharoCore), they each have packages for tests, core, blah. Those that have Help pages, then it would be really cool to have a separate package for them. - For each external package, they need to only to put Help pages in a separate package, but also create a group for them in the Metacello Configuration. Then, people can choose what to load. - PharoDev should include the metacello groups that contains the Help. Now...regarding this example, about the shortcuts...that is related to PharoCore...So, we have to options: 1) Cotinue commiting them in 'http://www.squeaksource.com/HelpSystem' and create a ConfigurationOfPharoHelp that we load for the dev image 2) Commit them into PharoCore and then remove them in #cleanUpForProduction I am not sure which I like more, but I think 2). Since we have Help already integrated in the core, the idea is to use it, isn't it ? otherwise this should be in the dev image. And I like to have the Help as closer as possible to the real code. So, I choose for 2), but of course, I am all ears. Cheers Mariano > Cheers, > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

Jan. 4, 2011

Re: [Pharo-project] IRC meeting next Tuesday, January 4, at ...?

by laurent laffont

On Tue, Jan 4, 2011 at 10:04 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > argh I totally missed my alarm clock on my machine (while cleaning the > house :) > So did people discuss? > May be we should redo a clear call. > +1 Laurent. > > Stef > > On Jan 3, 2011, at 9:46 PM, Adrian Lienhard wrote: > > > I just figured that I also can't make it tomorrow at 20:00 (I can be > online 2 hours later, though). > > > > Anyway, I suggest that everybody who is interested to discuss and sync > meets at 20:00 and it would be nice if somebody could write a short summary, > which we can post to the mailing list and the website. > > > > BTW, the channel is #pharo-project on irc.freenode.net. If you don't > have an IRC client you can browse to > > > > http://webchat.freenode.net/?channels=pharo-project > > > > Time: > http://www.timeanddate.com/counters/customcounter.html?day=4&month=1&year=2… > > > > Cheers, > > Adrian > > > > > > > > On Jan 3, 2011, at 09:15 , StÃ©phane Ducasse wrote: > > > >> Thanks for the call adrian. I will be travelling until 16h (it was not > planned when I proposed that dat) but there is no problem, > >> Stef > >> On Jan 2, 2011, at 10:34 PM, Adrian Lienhard wrote: > >> > >>> Hi all, > >>> > >>> During the last meeting [1] we decided to do the next one on January 4 > but we didn't decide when to start. > >>> > >>> The previous meeting started at 20:00 CET/UTC/GMT+1, which may not be > optimal for people in other time zones. If somebody likes to suggest another > time, please let us know soon! > >>> > >>> Cheers, > >>> Adrian > >>> > >>> [1] http://pharo-project.org/news?article=irc-meeting-notes > >> > >> > > > > > > >

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by Igor Stasenko

On 4 January 2011 23:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > Yes, 4.2.5 and exuperi both has UnixOSProcessPlugin as default (and I understand that, they are very needed :) ) > Err.. i asked about AioPlugin. Yes, OSProcessPlugin is quite useful , since with it we can perform some OS-specific tasks directly from smalltalk code. Someday it will rock, especially when we will have something better than FileDirectory & friends :) > Cheers, > Esteban > > El 04/01/2011, a las 3:15p.m., Igor Stasenko escribiÃ³: > >> On 4 January 2011 17:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> On Jan 4, 2011, at 4:25 AM, David T. Lewis wrote: >>> >>>> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>>>> Hello Everyone, >>>>> Â So, long time squeaker, first time pharo(er ?). Please don't hold this against me ;) >>>>> >>>>> Â I am trying to get CommandShell loaded into Pharo (using the Seaside Image) via Monticello. I have tried this on Pharo 1.1/1.1.1/1.2 for the record (same thing). I skip past the MVC/Morphic errors about PluggableList etc, and I can get the command shell to pop-up, however, two things happen; >>>>> >>>> >>>> The CommandShell package on SqueakSource is also now broken down >>>> into sub-packages, so you can load the individual parts if you want. >>>> But just proceding through the MVC warnings as you did is harmless. >>>> >>>>> Â 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >>>> >>>> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >>>> warning when running on a Mac. But as you say, it's just a warning. >>> >>> I imagine that we will see that with igor and the automatic build too. >>> >> >> was this plugin included into standard vms once before? because >> currently its not >> and i don't remember if i built VMs it . >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 4, 2011

Re: [Pharo-project] Pharo and CommandShell on OSX ?

by Esteban Lorenzano

the plugin does not runs out of the box on current vm's, I'm afraid :( Tomorrow I will try to fix the remaining problems for running this plugin... wish me luck :) Cheers, Esteban El 04/01/2011, a las 6:25p.m., Stef T escribiÃ³: > > On Jan 4, 2011, at 8:36 AM, StÃ©phane Ducasse wrote: > >>> >>> >>>> On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >>>>> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning >>>> >>>> AFAIK, noone has tried building the AioPlugin for Mac, so you will get this >>>> warning when running on a Mac. But as you say, it's just a warning. >>> >>> Is there a pointer for the source code ? I am pretty handy with Xcode and don't mind giving it a whirl ;) >> >> good there is a gitorious account for the vm and we would enjoy that people can contribute via there. >> >> http://gitorious.org/cogvm >> http://gitorious.org/squeak-vm >> > > Hello StÃ©phane, Everyone, > > Under OSX (10.6.5) and pulling the vm source from squeak (either the trunk or the blessed branch) I get this when building (without making any changes to the installed plugins -- yet ;) > > Stef-T-MacBook-Pro:build stef$ ../unix/cmake/configure --without-RomePlugin --without-vm-display-Quartz > .... > [ 70%] Building C object CMakeFiles/squeakvm.dir/version.c.o > [ 71%] Building C object CMakeFiles/squeakvm.dir/disabledPlugins.c.o > Linking C executable squeakvm > Undefined symbols: > "_sendInvokeCallbackStackRegistersJmpbuf", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_classUnsafeAlien", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_primitiveFailFor", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_internalIsImmutable", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_getStackPointer", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_reestablishContextPriorToCallback", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_classAlien", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > "_internalIsMutable", referenced from: > _sqGetInterpreterProxy in sqVirtualMachine.c.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[2]: *** [squeakvm] Error 1 > make[1]: *** [CMakeFiles/squeakvm.dir/all] Error 2 > make: *** [all] Error 2 > > that's .. not looking too healthy. Is OSX 'knowingly busted' ? > > Regards > S. > > > >> >>> >>>> >>>>> but >>>>> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >>>>> >>>>> If I am doing anything obviously wrong, please feel free to hit me over the head :) >>>> >>>> Nope, it's not you, it's the plugin included with your VM. Some >>>> of the Mac VMs in circulation were accidentally built with a very >>>> out of date version of the OSProcessPlugin. Apparently you have >>>> one of them, and it will definitely not work. But I think there >>>> is a newer version (4.2.5 IIRC) that has the up to date plugin >>>> that works properly on Mac. >>>> >>> >>> Hrm, I am using the OSProcess from squeaksource .59. The version history says >>> >>> Name: OSProcess-dtl.59 >>> Author: dtl >>> Time: 28 November 2010, 8:43:48.839 pm >>> UUID: bd5d2b4e-efbd-4091-ac0a-d0bd7af64b2c >>> >>> surely this is 'new enough' ? Is there a known 'stable' version you would suggest ? >>> >>> regards >>> S. >>> >>>> Dave >>>> >>>> >>>>> >>>>> Regards >>>>> S. >>>>> >>>>> >>>>> >>>>> >>>>> 3 January 2011 6:49:43 pm >>>>> >>>>> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >>>>> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >>>>> >>>>> SecurityManager state: >>>>> Restricted: false >>>>> FileAccess: true >>>>> SocketAccess: true >>>>> Working Dir /Users/stef/squeak/SeaSide-3.0 >>>>> Trusted Dir /foobar/tooBar/forSqueak/bogus >>>>> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >>>>> >>>>> UndefinedObject(Object)>>mustBeBooleanIn: >>>>> Receiver: nil >>>>> Arguments and temporary variables: >>>>> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>>>> proceedValue: nil >>>>> Receiver's instance variables: >>>>> nil >>>>> >>>>> UndefinedObject(Object)>>mustBeBoolean >>>>> Receiver: nil >>>>> Arguments and temporary variables: >>>>> >>>>> Receiver's instance variables: >>>>> nil >>>>> >>>>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>>>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>>>> Arguments and temporary variables: >>>>> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >>>>> bufferSize: 1000 >>>>> buffer: '...etc... >>>>> count: #(0) >>>>> Receiver's instance variables: >>>>> >>>>> >>>>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>>>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>>>> Arguments and temporary variables: >>>>> >>>>> Receiver's instance variables: >>>>> >>>>> >>>>> BufferedAsyncFileReadStream>>update: >>>>> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >>>>> Arguments and temporary variables: >>>>> aParameter: a PseudoAioEventHandler >>>>> Receiver's instance variables: >>>>> >>>>> >>>>> [] in PseudoAioEventHandler(Object)>>changed: >>>>> Receiver: a PseudoAioEventHandler >>>>> Arguments and temporary variables: >>>>> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >>>>> aDependent: a PseudoAioEventHandler >>>>> Receiver's instance variables: >>>>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>>>> >>>>> DependentsArray>>do: >>>>> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> Arguments and temporary variables: >>>>> aBlock: [:aDependent | aDependent update: aParameter] >>>>> dep: BufferedAsyncFileReadStream: 'pipeReader' >>>>> i: 1 >>>>> iLimiT: 1 >>>>> Receiver's instance variables: >>>>> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> >>>>> PseudoAioEventHandler(Object)>>changed: >>>>> Receiver: a PseudoAioEventHandler >>>>> Arguments and temporary variables: >>>>> aParameter: a PseudoAioEventHandler >>>>> Receiver's instance variables: >>>>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>>>> >>>>> PseudoAioEventHandler(Object)>>changed >>>>> Receiver: a PseudoAioEventHandler >>>>> Arguments and temporary variables: >>>>> >>>>> Receiver's instance variables: >>>>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>>>> >>>>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>>>> Receiver: a PseudoAioEventHandler >>>>> Arguments and temporary variables: >>>>> d: a Delay(125 msecs) >>>>> Receiver's instance variables: >>>>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>>>> >>>>> BlockClosure>>repeat >>>>> Receiver: [self changed. >>>>> d wait] >>>>> Arguments and temporary variables: >>>>> >>>>> Receiver's instance variables: >>>>> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >>>>> startpc: 59 >>>>> numArgs: 0 >>>>> >>>>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>>>> Receiver: a PseudoAioEventHandler >>>>> Arguments and temporary variables: >>>>> d: a Delay(125 msecs) >>>>> Receiver's instance variables: >>>>> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >>>>> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >>>>> >>>>> [] in BlockClosure>>newProcess >>>>> Receiver: [[self changed. >>>>> d wait] repeat] >>>>> Arguments and temporary variables: >>>>> >>>>> Receiver's instance variables: >>>>> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >>>>> startpc: 54 >>>>> numArgs: 0 >>>>> >>>>> >>>>> --- The full stack --- >>>>> UndefinedObject(Object)>>mustBeBooleanIn: >>>>> UndefinedObject(Object)>>mustBeBoolean >>>>> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >>>>> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >>>>> BufferedAsyncFileReadStream>>update: >>>>> [] in PseudoAioEventHandler(Object)>>changed: >>>>> DependentsArray>>do: >>>>> PseudoAioEventHandler(Object)>>changed: >>>>> PseudoAioEventHandler(Object)>>changed >>>>> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >>>>> BlockClosure>>repeat >>>>> [] in PseudoAioEventHandler>>eventGeneratorProcess >>>>> [] in BlockClosure>>newProcess >>>>> >>>> >>> >>> >> >> > >

Jan. 4, 2011