- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [XMLRPC] Little client clean up

by garduino

Ok, I published XMLRPC-Client-Core-GermanArduino.23 with the corrections. In the method sendXmlRpc: I maintained the original code commented, because need to implement some error controls in the new use of Zinc. Cheers. -- View this message in context: http://forum.world.st/XMLRPC-Little-client-clean-up-tp4635363p4635403.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 18, 2012

Re: [Pharo-project] default command line arguments

by Bernardo Ezequiel Contreras

Hi Francisco, It has been reported, see http://code.google.com/p/pharo/issues/detail?id=6075 It's a WIP On Mon, Jun 18, 2012 at 7:16 PM, Francisco Garau <francisco.garau(a)gmail.com>wrote: > Hi -- opening the latest version of Pharo (build #20134) throws an error > when trying to open the startup script (which I don't have). > > Maybe an empty Pharo-2.0.st should be included in the Pharo-2.0.zip? > > Cheers, > Francisco > > PS: let me know if I should report this with a bug entry. > > a CommandLineArguments > > '/builds/jenkins/workspace/Pharo-2.0/Pharo-2.0/Pharo-2.0.st' > > '-headless' > > MultiByteFileStream(Object)>>primitiveFailed > MultiByteFileStream(StandardFileStream)>>primClose: > MultiByteFileStream(StandardFileStream)>>close > [stream close] in FileReference>>readStreamDo: > MethodContext(ContextPart)>>resume:through: > BlockClosure>>ensure: > FileReference>>readStreamDo: > BasicCodeLoader>>installSourceFile: > [:reference | self installSourceFile: reference] in [sourceFiles > do: [:reference | self installSourceFile: reference]] in > BasicCodeLoader>>installSourceFiles > OrderedCollection>>do: > [sourceFiles > do: [:reference | self installSourceFile: reference]] in > BasicCodeLoader>>installSourceFiles > BlockClosure>>ensure: > BasicCodeLoader>>installSourceFiles > BasicCodeLoader>>activate > BasicCodeLoader class(CommandLineHandler class)>>activateWith: > DefaultCommandLineHandler>>handleSubcommand > DefaultCommandLineHandler>>handleArgument: > DefaultCommandLineHandler>>activate > [self new activate] in DefaultCommandLineHandler class>>startUp: > BlockClosure>>cull: > [each cull: resuming] in [:each | self > logStartUpErrorDuring: [each cull: resuming] > into: errors > tryDebugger: self isInteractive] in > SmalltalkImage>>executeDeferredStartupActions: > BlockClosure>>on:do: > SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: > [:each | self > logStartUpErrorDuring: [each cull: resuming] > into: errors > tryDebugger: self isInteractive] in > SmalltalkImage>>executeDeferredStartupActions: > OrderedCollection>>do: > SmalltalkImage>>executeDeferredStartupActions: > SmalltalkImage>>startupImage:snapshotWorked: > SmalltalkImage>>snapshot:andQuit: > -- Bernardo E.C.

June 18, 2012

[Pharo-project] default command line arguments

by Francisco Garau

Hi -- opening the latest version of Pharo (build #20134) throws an error when trying to open the startup script (which I don't have). Maybe an empty Pharo-2.0.st should be included in the Pharo-2.0.zip? Cheers, Francisco PS: let me know if I should report this with a bug entry. a CommandLineArguments '/builds/jenkins/workspace/Pharo-2.0/Pharo-2.0/Pharo-2.0.st' '-headless' MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primClose: MultiByteFileStream(StandardFileStream)>>close [stream close] in FileReference>>readStreamDo: MethodContext(ContextPart)>>resume:through: BlockClosure>>ensure: FileReference>>readStreamDo: BasicCodeLoader>>installSourceFile: [:reference | self installSourceFile: reference] in [sourceFiles do: [:reference | self installSourceFile: reference]] in BasicCodeLoader>>installSourceFiles OrderedCollection>>do: [sourceFiles do: [:reference | self installSourceFile: reference]] in BasicCodeLoader>>installSourceFiles BlockClosure>>ensure: BasicCodeLoader>>installSourceFiles BasicCodeLoader>>activate BasicCodeLoader class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate [self new activate] in DefaultCommandLineHandler class>>startUp: BlockClosure>>cull: [each cull: resuming] in [:each | self logStartUpErrorDuring: [each cull: resuming] into: errors tryDebugger: self isInteractive] in SmalltalkImage>>executeDeferredStartupActions: BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: [:each | self logStartUpErrorDuring: [each cull: resuming] into: errors tryDebugger: self isInteractive] in SmalltalkImage>>executeDeferredStartupActions: OrderedCollection>>do: SmalltalkImage>>executeDeferredStartupActions: SmalltalkImage>>startupImage:snapshotWorked: SmalltalkImage>>snapshot:andQuit:

June 18, 2012

Re: [Pharo-project] Version of method broken

by Mariano Martinez Peck

On Mon, Jun 18, 2012 at 9:21 PM, Davide Varvello <varvello(a)yahoo.com> wrote: > Hi, > Suddenly methods' version is broken, i.e. when I click on a method and > select "versions", the "recent versions" panel appears but looking at > method > versions, no differences is displayed with standard red and green colors > and > moreover revert button does not work anymore. > Hi Davide. All I can say is that I remember seeing this bug in previous versions of Nautilus. Of course this has been fixed in latest Nautilus versions but they are available only for Pharo 2.0. I guess the version of Nautilus that works in 1.4 is a little bit old. We (Ben) cannot maintain Nautilus working with both versions so in 1.4.1 you need to stick to that version. Maybe someone can take that version and create a new one with the bug fix... > I'm on Pharo 1.4 with Nautilus. > Hints? > Thanks > Davide > > -- > View this message in context: > http://forum.world.st/Version-of-method-broken-tp4635379.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

June 18, 2012

Re: [Pharo-project] [XMLRPC] Little client clean up

by garduino

Sure, I still must to publish latest version, await me a bit please. Will do it as soon as I can. Cheers. -- View this message in context: http://forum.world.st/XMLRPC-Little-client-clean-up-tp4635363p4635381.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 18, 2012

[Pharo-project] Version of method broken

by Davide Varvello

Hi, Suddenly methods' version is broken, i.e. when I click on a method and select "versions", the "recent versions" panel appears but looking at method versions, no differences is displayed with standard red and green colors and moreover revert button does not work anymore. I'm on Pharo 1.4 with Nautilus. Hints? Thanks Davide -- View this message in context: http://forum.world.st/Version-of-method-broken-tp4635379.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 18, 2012

Re: [Pharo-project] flatten method is kind of broken

by Fabrizio Perin

Sorry, back from long weekend offline. I can port the moose extensions to the core indeed. Doru did you open the issue already? Cheers, Fabrizio 2012/6/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > doru > > can you open a bug entry and provide necessary information? > Package and tests? > > Stef > > On Jun 16, 2012, at 8:07 AM, Tudor Girba wrote: > > > Indeed. It would be great to integrate CollectionExtensions into Pharo. > > > > For example, we have: > > #(#(1) #(2 3) #(#(4) 5) ) deepFlatten > > ==> #(1 2 3 4 5) > > > > Cheers, > > Doru > > > > On 15 Jun 2012, at 21:04, StÃ©phane Ducasse wrote: > > > >> fabrizio we should really include some of the moose extensions to pharo. > >> Could you take the lead on that? > >> > >> Did you try gather:? > >> > >> Stef > >> > >> On Jun 15, 2012, at 10:05 AM, Fabrizio Perin wrote: > >> > >>> Hi, > >>> I need to flatten a collection which does not contain other > collections necessarily. The method flatten doesn't really work: > >>> > >>> #(#(1 2) #(3 4)) flatten -> #(1 2 3 4) OK > >>> > >>> #(#(1) #(2 3) #(#(4) 5) ) flatten -> #(1 2 3 #(4) 5) I would have > expected something like #(1 2 3 4 5) > >>> > >>> #(1 2 3) flatten -> error > >>> #(#(1) 2 3) flatten -> error > >>> > >>> Is this the meant behavior for flatten? Any other method I could use > instead? > >>> > >>> Thanks, > >>> Fabrizio > >> > >> > > > > -- > > www.tudorgirba.com > > > > "We are all great at making mistakes." > > > > > > > > > > > > > > > > > > >

June 18, 2012

Re: [Pharo-project] squeaksource is down (eom)

by Fabrizio Perin

up again 2012/6/18 Chris Muller <asqueaker(a)gmail.com> > > >

June 18, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Milan Mimica

On 13 June 2012 11:08, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > - pre-load OmniBrowser. > Two things I have noticed don't work well in OB in Pharo 1.4: 1. The chasing browser for senders/implementors - well it's not chasing. 2. When you hit ctrl+f and type something, you cannot use arrow keys to select a class from the list. You have to switch focus with the mouse first. -- Milan Mimica http://sparklet.sf.net

June 18, 2012

Re: [Pharo-project] Look and font competition

by Gary Chambers

Polymorph does support such things... The buttons in Watery2 theme for example. For sizeable things (as opposed to scaleable) a composite fill style can be made with elements for corners, edges and middle. Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, June 12, 2012 10:44 PM Subject: Re: [Pharo-project] Look and font competition > On 12 June 2012 23:28, Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> > wrote: >> The subtle texture is more like overlaying the existing elements with >> white >> noise. >> >> While one can make an IconicButton of course, one can not make a Window >> Title Bar this way. There must be a way to make it directly in code? With >> more and more high resolution displays it will get interesting some day. >> Look at the OS X Lion - Pharo comparison screenshot: >> >> http://forum.world.st/file/n4634551/SubtleTexture.jpg >> > > oh .. it is indeed subtle.. i didn't get what you mean first time. > yes, of course, that's possible.. just not sure if it worth to waste > CPU cycles on this, as you said, > subtle stuff. > > > >> >> -- >> View this message in context: >> http://forum.world.st/Look-and-font-competition-tp4634175p4634551.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > > -- > Best regards, > Igor Stasenko. >

June 18, 2012