June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Array size in inspector

by Sean P. DeNigris

Davide Varvello wrote > > I've a very long array I'd like to inspect, unfortunately inspector shows > only first 100 elements and few last elements of my array. How can change > that behavior? > Hey Davide! Please ask user questions on StackOverflow (tagged with Pharo) or the Pharo Users list, so they do not get lost/confused with the development issues discussed here. If you explore your array instead of inspecting it, you should see all the elements (may take a long time, depending on the size). HTH, Sean -- View this message in context: http://forum.world.st/Array-size-in-inspector-tp4635484p4635503.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 19, 2012

Re: [Pharo-project] Integer>>asDateFromZip

by Sean P. DeNigris

Sven Van Caekenberghe wrote > > I tagged issue 6054 as FixToInclude. > While making a slice, I found a related bug and needed to cleanup some FS-related stuff. The slice needs a review (although I'm confident about it, see "Successfully loaded" part below). Like Sven said, not being able to load code is a severe bug, so let's get this checked and integrated!! Fix in inbox: SLICE-Issue-6054-Error-when-reading-zip-files-with-Squeak-datetime-format-SeanDeNigris.1 * When reading zip files, treat invalid, error-causing DOS timestamps as the old, incorrect format from Squeak - Fix ZipFileMember>>read*DirectoryFileHeader* methods - Add (now)-passing test for timestamp that caused the issue to be reported (see comment 1 in issue or test comment) * Delegate DOS timestamp processing to DateAndTime - Remove date/time zip/unzip methods from ArchiveMember - Update Zip*Member reading/writing methods - Remove zip-related methods and protocols from Date, Time, and Integer - Remove associated tests * When writing directories to zip files, append trailing slash to name, which is required (at least Mac OS X can't handle without) Successfully loaded slice into 20140 * all compression tests pass * The following fails before slice, passes after "ZipArchive new readFrom: '/path/to/Balloon-CamilloBruni.85.mcz'" -- View this message in context: http://forum.world.st/Integer-asDateFromZip-tp4635452p4635501.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 19, 2012

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

by Noury Bouraqadi

Thanx a lot germÃ n On 19 juin 2012, at 02:05, garduino wrote: > And updated ConfigurationOfXMLRPC adding 'version100Beta4' to install the > latest client code. > > -- > View this message in context: http://forum.world.st/XMLRPC-Little-client-clean-up-tp4635363p4635405.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print

June 19, 2012

[Pharo-project] Array size in inspector

by Davide Varvello

Hi, I've a very long array I'd like to inspect, unfortunately inspector shows only first 100 elements and few last elements of my array. How can change that behavior? Thanks Davide -- View this message in context: http://forum.world.st/Array-size-in-inspector-tp4635484.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 19, 2012

Re: [Pharo-project] Version of method broken

by Davide Varvello

Done. http://code.google.com/p/pharo/issues/detail?id=6085 Davide Benjamin Van Ryseghem-2 wrote > > I can have a look. Now I can't, but I will in the end of the week :) > > > Think about opening an issue on the issue tracker, with me as cc, type > nautilus and milestone 1.4 :) > Thanks in advance, > > Ben > > On Jun 18, 2012, at 11:11 PM, Mariano Martinez Peck wrote: > >> >> >> On Mon, Jun 18, 2012 at 9:21 PM, Davide Varvello <varvello@> 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 >> > -- View this message in context: http://forum.world.st/Version-of-method-broken-tp4635379p4635483.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 19, 2012

Re: [Pharo-project] Mouse down events are being processed twice

by StÃ©phane Ducasse

:) >> It's our Pharo :) And, it's usually easier to fix the bug than to suffer > from it ;-) > > Sean > > -- > View this message in context: http://forum.world.st/Mouse-down-events-are-being-processed-twice-tp4635339… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 19, 2012

Re: [Pharo-project] Integer>>asDateFromZip

by Sven Van Caekenberghe

OK, I patched with those changes, it works now, Thx! I tagged issue 6054 as FixToInclude. On 19 Jun 2012, at 14:18, Sean P. DeNigris wrote: > > Sven Van Caekenberghe wrote >> >> Is there some quick patch that I could do to get passed this, as it is >> blocking the loading of code, which is rather fundamental. >> > > I didn't realize this hadn't been integrated... > http://code.google.com/p/pharo/issues/detail?id=6054 > > -- > View this message in context: http://forum.world.st/Integer-asDateFromZip-tp4635452p4635460.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 19, 2012

Re: [Pharo-project] Version of method broken

by Benjamin

I can have a look. Now I can't, but I will in the end of the week :) Think about opening an issue on the issue tracker, with me as cc, type nautilus and milestone 1.4 :) Thanks in advance, Ben On Jun 18, 2012, at 11:11 PM, Mariano Martinez Peck wrote: > > > 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 19, 2012

[Pharo-project] The Magic of FileSystem

by Sean P. DeNigris

This... localFileName: aString | dir entry parent fileNameWithoutTrailingSlash | super localFileName: aString. parent := FileDirectory default. self flag: 'directoryExists: fails if trailing slash. Replace this whole mess with FS'. fileNameWithoutTrailingSlash := fileName last = $/ ifTrue: [ fileName allButLast ] ifFalse: [ fileName ]. (parent directoryExists: fileNameWithoutTrailingSlash) ifTrue: [ dir := FileDirectory on: (parent fullNameFor: fileName). entry := dir directoryEntry. self modifiedAt: (DateAndTime fromSeconds: entry modificationTime) ]. fileName last = $/ ifFalse: [ fileName := fileName, '/' ]. (which I *think* had an undiscovered bug, invisible due to the complexity) vs. This... localFileName: aString | file | super localFileName: aString. file := aString asFileReference. file exists ifFalse: [ ^ self ]. self modifiedAt: file entry modificationTime. Ahhhh... Cheers, Sean -- View this message in context: http://forum.world.st/The-Magic-of-FileSystem-tp4635471.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 19, 2012

Re: [Pharo-project] Process Tests and

by Frank Shearar

On 14 June 2012 11:42, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > On 14 Jun 2012, at 11:34, Frank Shearar wrote: > >>>> How do you #join Processes? I can't see anything in Process' protocol >>>> for doing so. so what am I missing? >>> >>> >>> Nothing. Â Theres no support for join. Â You have to roll your own. >> >> OK, that's what I thought. Stefan's comment intrigued me. > > Yes, my fault. I added it to some random subclass somewhere, because I thought it was handy. > It is indeed not in the standard images. > > >> >> It would be kind've handy to be able to say - even though we don't use >> native threads - something like this: >> >> (0..10).map {|i| >> Â Â Thread.new { sleep(1); i } >> }.map {|t| t.value} >> >> only in a decent language: >> >> ((0 to: 10) >> Â Â collect: [:i | [(Delay forSeconds: 1) wait. i] fork]) >> Â Â Â collect: [:p | p value]. > > Yes, that was part of the discussion. > > For the options discussed of the return value of fork, we have three options: > > Â 1. self [Smalltalk-80 defines it this way, apparently] > Â Â self is the block, > Â Â it is the consistent return value for methods without real return value. > > Â Â -> I think, this is the least useful option > > Â 2. Process [current implementation] > Â Â It's the object created as the side-effect of fork. > Â Â Allows to query whether the fork already completed. > Â Â Process could be extended to offer #join (at a cost of a semaphore, presumably). > > Â 3. Promise > Â Â As the placeholder for the result value of the block computation. > Â Â Benefit is that we get an immediate handle on the result, and the > Â Â ability to wait for the completion of the process, even if we only > Â Â care for its side-effects. > > Â Â There is however currently no Promise class in Pharo. Squeak got one, I think. Yes. Also, this mention of Promise made me start to dig into Promise and Squeak's implementation of futures. That lead me back to asking the above! What I find confusing is that I don't see how a Process can return anything. I mean, in the sense that a Process is an undelimited continuation it doesn't _have_ a return type, but we can pretend for a moment that they do, or can, return. I see no way of getting that return value. Ruby's Thread#value simply waits for the thread to terrminate, and returns the value of the last expression. A bit like a block, actually. Given the long-standing behaviour of #fork (hence many out-of-image packages using it), it seems prudent to have a _new_ API for fork/join. That new API could quite happily use Promises for both forking and joining. frank > 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 > >

June 19, 2012