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

Re: [Pharo-project] [update 1.3] #13005

by Igor Stasenko

we're already in 1.3??? wow... i didn't noticed.. guys, where is official announcement of new version release? :) On 20 January 2011 22:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 13005 > ----- > > Issue 3560: Â Â Clean of RML > Issue 3559: Â Â Remodularization of BalloonMorph > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 20, 2011

Re: [Pharo-project] [squeak-dev] Instruments for headless images

by Igor Stasenko

On 20 January 2011 22:05, Chris Muller <asqueaker(a)gmail.com> wrote: > The Ma stack does something similar, although not crippling the system > to the same extent. > well, if by 'crippling' you mean preventing any unwanted activity when headless.. then yes, i want it :) > How do you determine you're running headless? Â I attached my > implementation of #maIsHeadless for determining whether the VM was > launched headless. Â Perhaps we should integrate this functionality > into Squeak and Pharo (or a variant without the prefix, of course). > okay, as i suspected there is no direct way to determine that.. i don't like checking the command-line args, because obviously i can build vm which completely ignores that. but since there is no other options... > Then, I use MaCommandLineProcessor which is concerned with handling > the command-line Squeak was launched with: > > Then, I write my .st scripts like: > [snip] ohh.. well, but that is too much for a simple script. it would be good if image could provide something by default, because i don't want to repeat expressions like this in each script i write for running it in headless image. :) > > Â - Chris > > > On Thu, Jan 20, 2011 at 2:39 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> Hello folks. >> >> I'd like to ask, if there any 'standartized' instruments for headless >> images (or alike). >> >> I need a simple things: >> Â - redirect all Â ToolSet/UIManager messages to Transcript >> Â - redirect Transcript logging to file or stdout >> >> in short, these tools should serve a simple, yet important purpose: >> Â - if image runs in headless mode, it should suppress anything which >> expecting user interaction (like showing warnings with 'continue' >> button) and either log such messages to file >> or simply quit image with error message. >> >> Without such tool it is quite difficult to monitor, what happens with >> your headless image.. unless you have RFB installed.. but that is >> different and unrelated story. >> >> >> I did a prototype once for Hydra (you can check it at >> SqS/HydraVM/HydraVM.mcz package) >> there are two subclasses: >> - MorphicUIManager subclass: #HydraUIManager >> - StandardToolSet subclass: #HydraDebugToolSet >> >> and >> - WriteStream subclass: #HydraTranscript >> >> which can be installed as a Transcript. >> >> And in order to prepare image to run in headless mode, i issued: >> Â Â Â Â ToolSet unregister: StandardToolSet. >> Â Â Â Â ToolSet register: HydraDebugToolSet. >> Â Â Â Â UIManager default: HydraUIManager new. >> >> Also, HydraTranscript >> startUp does something like: >> >> Â Â Â Â TranscriptStream >> Â Â Â Â Â Â Â Â newTranscript: (self basicNew initialize >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â on: (String new: 1000)) >> >> >> With that i could run the image in headless mode, knowing that in case >> of error or warning etc, all will be redirected to transcript, >> moreover i even stopped the UI process, so it never run on headless images. >> >> I wonder if there are other work, which can offer similar, >> and is there any way to detect that image are running in headless mode? >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 20, 2011

Re: [Pharo-project] [squeak-dev] Instruments for headless images

by Igor Stasenko

On 20 January 2011 21:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > there is a DummyManager to control pop up and friends. where it located? > > Stef > > On Jan 20, 2011, at 9:39 PM, Igor Stasenko wrote: > >> Hello folks. >> >> I'd like to ask, if there any 'standartized' instruments for headless >> images (or alike). >> >> I need a simple things: >> - redirect all Â ToolSet/UIManager messages to Transcript >> - redirect Transcript logging to file or stdout >> >> in short, these tools should serve a simple, yet important purpose: >> - if image runs in headless mode, it should suppress anything which >> expecting user interaction (like showing warnings with 'continue' >> button) and either log such messages to file >> or simply quit image with error message. >> >> Without such tool it is quite difficult to monitor, what happens with >> your headless image.. unless you have RFB installed.. but that is >> different and unrelated story. >> >> >> I did a prototype once for Hydra (you can check it at >> SqS/HydraVM/HydraVM.mcz package) >> there are two subclasses: >> - MorphicUIManager subclass: #HydraUIManager >> - StandardToolSet subclass: #HydraDebugToolSet >> >> and >> - WriteStream subclass: #HydraTranscript >> >> which can be installed as a Transcript. >> >> And in order to prepare image to run in headless mode, i issued: >> Â Â Â ToolSet unregister: StandardToolSet. >> Â Â Â ToolSet register: HydraDebugToolSet. >> Â Â Â UIManager default: HydraUIManager new. >> >> Also, HydraTranscript >> startUp does something like: >> >> Â Â Â TranscriptStream >> Â Â Â Â Â Â Â newTranscript: (self basicNew initialize >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â on: (String new: 1000)) >> >> >> With that i could run the image in headless mode, knowing that in case >> of error or warning etc, all will be redirected to transcript, >> moreover i even stopped the UI process, so it never run on headless images. >> >> I wonder if there are other work, which can offer similar, >> and is there any way to detect that image are running in headless mode? >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 20, 2011

[Pharo-project] [update 1.3] #13005

by Marcus Denker

13005 ----- Issue 3560: Clean of RML Issue 3559: Remodularization of BalloonMorph -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 20, 2011

Re: [Pharo-project] Gofer issue

by Igor Stasenko

On 20 January 2011 21:36, Lukas Renggli <renggli(a)gmail.com> wrote: >> however, Â if i open the MC repo browser, it clearly shows that most >> recent version is >> CMakeVMMaker-Igor.Stasenko.16 Â (at the moment of writing this message) > > Following the coventions your name is 'Igor' and the package is on the > branch 'Stasenko'. Gofer proritizes the main branch. > how about retrieving the latest version regardless of branch? Can you provide an example how to tell Gofer to load it? >> Gofer new >> Â Â Â Â url: 'http://squeaksource.com/VMMaker'; >> Â Â Â Â package: 'VMMaker-oscog.46'; >> Â Â Â Â load. >> >> and it barks that given version is not found.. which of course not true. > > 'VMMaker-oscar.46' is clearly not a package name, use #version: to > refer to a specific version. > okay, i doing: Gofer new url: 'http://squeaksource.com/VMMaker'; package: 'VMMaker-oscog'; resolved an Array(a GoferResolvedReference name: 'VMMaker-oscog-Igor.Stasenko.47') hmm.. that doesn't looks right, isnt? Because as you said, following the coventions author's name is 'Igor' and the package is on the branch 'Stasenko' And since Gofer prioritizes main branch, the resolved version should be VMMaker-oscog.46 or i again misunderstood? >> Actually i surprised that Gofer simply don't reusing the MC package >> enumeration logic.. or maybe it does.. but obviously doing it wrong :) > > Please study the documentation in the class comment of Gofer. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Best regards, Igor Stasenko AKA sig.

Jan. 20, 2011

Re: [Pharo-project] Issue 3559 in pharo: Remodularization of BalloonMorph

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #1 on issue 3559 by marcus.d...(a)gmail.com: Remodularization of BalloonMorph http://code.google.com/p/pharo/issues/detail?id=3559 13005

Jan. 20, 2011

[Pharo-project] Gofer issue

by Torsten Bergmann

Hi Lukas, maybe that class comment docu is not that obvious and it's time to provide a help book. With the new help extension in Pharo 1.2 (using a pragma as you suggested) it is now also possible to write a book completely independent from HelpSystem (Alains wikistyle help based on pier). File in the attached file (with a gofer example) and open the help browser. You will find a Gofer help book then (example requires some formatting but you get the idea). The schema goes like this: fooMethod <wikiStyleHelp: 'My Book'> ^'!Topic !!Subtopic Your contents here ' Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

Jan. 20, 2011

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

by pharo＠googlecode.com

Updates: Status: Started Labels: -Milestone-1.3 Comment #3 on issue 3506 by marcus.d...(a)gmail.com: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 Fix in inbox SLICE-Issue-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1 is empty.

Jan. 20, 2011

Re: [Pharo-project] splitters in table layout

by Tudor Girba

Hi Gary, Indeed, this stops the debugger popping out. However, resizing is not live (only when I mouseUp: does the scroll pane refresh). Is there a quick way to solve this issue, or should we just go with this fix for the moment? Cheers, Doru On 20 Jan 2011, at 12:43, Gary Chambers wrote: > The attached changeset will "fix" this, though perhaps not ideal... > > Perhaps it is time to refactor all the Resizer stuff! > > Regards, Gary > > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, January 20, 2011 11:17 AM > Subject: Re: [Pharo-project] splitters in table layout > > > What does this imply? > > Cheers, > Doru > > > On 20 Jan 2011, at 12:09, Gary Chambers wrote: > >> Missed the case where fast dragging setting is enabled.... >> >> Regards, Gary >> >> ----- Original Message ----- From: "Andreas Wacknitz" <a.wacknitz(a)gmx.de> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Tuesday, January 18, 2011 8:33 PM >> Subject: Re: [Pharo-project] splitters in table layout >> >> >> >> Am 18.01.2011 um 20:58 schrieb Tudor Girba: >> >>> Yes, you missed a changeset Gary sent in the aligning morphs thread (he actually sent two, and you should pick the second one). >>> >>> Cheers, >>> Doru >>> >> Ah, thank you. I have found two messages with changesets from January 11th, 2011. >> After I filein the second changeset alas I will get a DNU Morph>>doFastWindowReframe: when I move the splitter... >> >> Regards, >> Andreas >> >> >> > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > > <EdgeGripFastReframeFix.1.cs> -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Jan. 20, 2011

Re: [Pharo-project] [squeak-dev] Instruments for headless images

by Chris Muller

The Ma stack does something similar, although not crippling the system to the same extent. How do you determine you're running headless? I attached my implementation of #maIsHeadless for determining whether the VM was launched headless. Perhaps we should integrate this functionality into Squeak and Pharo (or a variant without the prefix, of course). Then, I use MaCommandLineProcessor which is concerned with handling the command-line Squeak was launched with: Then, I write my .st scripts like: MaCommandLineProcessor do: [ : arg1 : arg2 : arg3 : etc | "my batch code script..." "args come in as Strings." "... you can have a variable number of args." ] as well as a uniform error-handler for all scripts, to redirect to stdout and stderr, thusly: MaCommandLineProcessor class>>#do: aBlock | stdOut stdErr | self ensureStartedUp. stdOut := StandardFileStream stdout. stdErr := StandardFileStream stderr. [ aBlock valueWithAllArguments: self args ] on: Notification , Warning do: [ : noti | stdOut nextPutAll: DateAndTime now asString ; space ; nextPutAll: noti description ; perform: MultiByteFileStream lineEndDefault. noti resume ] on: SyntaxErrorNotification do: [ : err | stdOut nextPutAll: err errorCode ; perform: MultiByteFileStream lineEndDefault. self haltOrQuit ] on: Error do: [ : err | stdErr nextPutAll: 'ERROR: ' ; nextPutAll: DateAndTime now asString ; space ; perform: MultiByteFileStream lineEndDefault ; nextPutAll: err description ; perform: MultiByteFileStream lineEndDefault. err isMaUserError ifFalse: [ stdErr nextPutAll: (err signalerContext longStack copyReplaceAll: Character cr asString with: (String perform: MultiByteFileStream lineEndDefault)) ]. self haltOrQuit ] #haltOrQuit is where it checks #maIsHeadless to determine whether to halt or quit. MaCommandLineProcessor is part of "Ma base additions" package, so any of the "Ma" softwares (Magma, Maui, Ma client server, etc.) will have it. But I think it would be useful to put this (or, a variant) directly into a future Squeak. - Chris On Thu, Jan 20, 2011 at 2:39 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello folks. > > I'd like to ask, if there any 'standartized' instruments for headless > images (or alike). > > I need a simple things: > Â - redirect all Â ToolSet/UIManager messages to Transcript > Â - redirect Transcript logging to file or stdout > > in short, these tools should serve a simple, yet important purpose: > Â - if image runs in headless mode, it should suppress anything which > expecting user interaction (like showing warnings with 'continue' > button) and either log such messages to file > or simply quit image with error message. > > Without such tool it is quite difficult to monitor, what happens with > your headless image.. unless you have RFB installed.. but that is > different and unrelated story. > > > I did a prototype once for Hydra (you can check it at > SqS/HydraVM/HydraVM.mcz package) > there are two subclasses: > - MorphicUIManager subclass: #HydraUIManager > - StandardToolSet subclass: #HydraDebugToolSet > > and > - WriteStream subclass: #HydraTranscript > > which can be installed as a Transcript. > > And in order to prepare image to run in headless mode, i issued: > Â Â Â Â ToolSet unregister: StandardToolSet. > Â Â Â Â ToolSet register: HydraDebugToolSet. > Â Â Â Â UIManager default: HydraUIManager new. > > Also, HydraTranscript > startUp does something like: > > Â Â Â Â TranscriptStream > Â Â Â Â Â Â Â Â newTranscript: (self basicNew initialize > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â on: (String new: 1000)) > > > With that i could run the image in headless mode, knowing that in case > of error or warning etc, all will be redirected to transcript, > moreover i even stopped the UI process, so it never run on headless images. > > I wonder if there are other work, which can offer similar, > and is there any way to detect that image are running in headless mode? > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Jan. 20, 2011