August 2012 - Pharo-users - lists.pharo.org

Downloading a .tar.gz file with Zinc in Pharo-1.4(Summer)

by Paul DeBruicker

I'm trying to download the Olson time-zone database so Chronos can automatically update its ruleset. In a workspace, when I do: ZnClient new url:'http://www.iana.org/time-zones/repository/tzdata-latest.tar.gz'; downloadTo:FileDirectory default pathName. I get a SubscriptOutOfBounds error . The file is ~207kB. The GzipReadStream>#getFirstBuffer gets the first 65,536 bytes and then hits the out of bounds error. Moving the limit in that method to 262,144 (1 << 18 rather than 1 << 16) gets us to another error from which I don't know the right way to proceed. I think that because its an content type 'application/x-tar' it shouldn't hit the GzipReadStream class at all but should just be a ReadStream that does not get decompressed in the image and instead sent straight to the disk. I'm not sure how to implement that though inside Zinc and would welcome ideas to try. Thanks Paul

Aug. 17, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by Helene Bilbo

Ricardo Moran wrote > > Hi, maybe my version of Pharo 1.4 is too old (Pharo1.4a Latest update: > #14406) or maybe this only works in Windows but I made a morph that > handles > dropped files by just overriding these two methods: > > wantsDropFiles: anEvent > ^ true > > dropFiles: evt > "Do what you want here" > That's the first thing i tried. I coudn't find #14406 but i retried in other old builds also in 1.3 but i always have the same problem: Non on the methods in this morph get's ever called, because it is the World (PasteUpMorph) that handles everything, before my morph even get's a chance. Might it have to do something with the OS? I run on MacOSX. Or can you share an image where this is working? -- View this message in context: http://forum.world.st/HowTo-make-a-Morph-that-accepts-dropped-files-and-fol… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 17, 2012

best practices for model/view dependencies

by Johann Hibschman

I'm still relatively new to Pharo and to Smalltalk in general, and I've hit a situation where I'd like a model that notifies dependent views when it changes. Classically, it looks like this was done through #addDependent:, #update, #changed, #release and friends. I don't need more than a symbol message and an associated object, so I could live with that API, but I don't quite understand #release. It sounds like originally Object class held (non-weak) references to all objects that had dependents, so unless the dependents were explicitly released, the objects would never be released. I get the impression that at some point this was switched to using weak references, so I wouldn't have to worry about closed parent/dependent loops, but I can't find this explicitly spelled out anywhere. - Question 1: Does the basic addDependent/etc. system on Pharo use weak references? - Question 2: Am I correct in understanding that the main point of the Model class was to avoid having an entry in the Object class variable, so a closed parent/dependent loop could be garbage collected? - Question 3: If Pharo uses weak references, is there any point to the Model class? I've also seen some references to the Announcements framework, but I can't find as much documentation on it as I can on the "basic" Smalltalk dependency mechanism. It seems a bit more complex, with actual event classes, but I've not understood it yet. - Question 4: Should I prefer using Announcements for even mostly trivial cases? - Question 5: What benefits would Announcements give me? Any overall pointers would be appreciated as well. Thanks, Johann

Aug. 17, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by StÃ©phane Ducasse

it should work since we did not change much in that area. Stef On Aug 16, 2012, at 9:29 PM, Ricardo Moran wrote: > Hi, maybe my version of Pharo 1.4 is too old (Pharo1.4a Latest update: #14406) or maybe this only works in Windows but I made a morph that handles dropped files by just overriding these two methods: > > wantsDropFiles: anEvent > ^ true > > dropFiles: evt > "Do what you want here" > > Cheers, > Richo > > On Thu, Aug 16, 2012 at 2:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > we already removed a bunch of them (not there but in the handMorph loop) > > but I should continue to work on it to get it ready to integrate. > > > > > > Thank's for all your hard work. > > But actualy I wait Shapes framework from Fernando Olivero. > > Ok I can understand now I would suggest to help fernando to deliver it and us to integrate it. > > Stef > > Best regards, > > Denis > > > > > > > > >

Aug. 17, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by Ricardo Moran

Hi, maybe my version of Pharo 1.4 is too old (Pharo1.4a Latest update: #14406) or maybe this only works in Windows but I made a morph that handles dropped files by just overriding these two methods: wantsDropFiles: anEvent ^ true dropFiles: evt "Do what you want here" Cheers, Richo On Thu, Aug 16, 2012 at 2:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > we already removed a bunch of them (not there but in the handMorph loop) > > but I should continue to work on it to get it ready to integrate. > > > > > > Thank's for all your hard work. > > But actualy I wait Shapes framework from Fernando Olivero. > > Ok I can understand now I would suggest to help fernando to deliver it and > us to integrate it. > > Stef > > Best regards, > > Denis > > > > > > > > >

Aug. 16, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by StÃ©phane Ducasse

> we already removed a bunch of them (not there but in the handMorph loop) > but I should continue to work on it to get it ready to integrate. > > > Thank's for all your hard work. > But actualy I wait Shapes framework from Fernando Olivero. Ok I can understand now I would suggest to help fernando to deliver it and us to integrate it. Stef > Best regards, > Denis > > >

Aug. 16, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by Denis Kudriashov

2012/8/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Aug 16, 2012, at 12:54 PM, Denis Kudriashov wrote: > > > 2012/8/16 Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> > > > > Thank you for the hint. It seems the problem lies in the fact that a > > "dropFilesEvent" is different from a "dropEvent" and therefore is not > > handled by MorphicEventDispatcher>>dispatchDropEvent:with: but by > > MorphicEventDispatcher>>dispatchEvent:with: and they handle differently > > which morph may get to process the event. > > Still i have not yet a solution ;( > > > > > http://forum.world.st/file/n4644226/Bildschirmfoto_2012-08-16_um_11.17.35.p… > > > > > > I'm always wondering when look at such code. > > How so many "if statements" can exist at smalltalk system? > > we already removed a bunch of them (not there but in the handMorph loop) > but I should continue to work on it to get it ready to integrate. > > Thank's for all your hard work. But actualy I wait Shapes framework from Fernando Olivero. Best regards, Denis

Aug. 16, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by StÃ©phane Ducasse

On Aug 16, 2012, at 12:54 PM, Denis Kudriashov wrote: > 2012/8/16 Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> > > Thank you for the hint. It seems the problem lies in the fact that a > "dropFilesEvent" is different from a "dropEvent" and therefore is not > handled by MorphicEventDispatcher>>dispatchDropEvent:with: but by > MorphicEventDispatcher>>dispatchEvent:with: and they handle differently > which morph may get to process the event. > Still i have not yet a solution ;( > > http://forum.world.st/file/n4644226/Bildschirmfoto_2012-08-16_um_11.17.35.p… > > > I'm always wondering when look at such code. > How so many "if statements" can exist at smalltalk system? we already removed a bunch of them (not there but in the handMorph loop) but I should continue to work on it to get it ready to integrate. > > Best regards, > Denis > >

Aug. 16, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by Denis Kudriashov

2012/8/16 Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> > > Thank you for the hint. It seems the problem lies in the fact that a > "dropFilesEvent" is different from a "dropEvent" and therefore is not > handled by MorphicEventDispatcher>>dispatchDropEvent:with: but by > MorphicEventDispatcher>>dispatchEvent:with: and they handle differently > which morph may get to process the event. > Still i have not yet a solution ;( > > > http://forum.world.st/file/n4644226/Bildschirmfoto_2012-08-16_um_11.17.35.p… > > I'm always wondering when look at such code. How so many "if statements" can exist at smalltalk system? Best regards, Denis

Aug. 16, 2012

Re: [Pharo-users] HowTo make a Morph that accepts dropped files and folders and produces a new FileSystem FileReference in Pharo 1.4

by StÃ©phane Ducasse

I do not know more but indeed we will have to clean and simplify that. STef On Aug 16, 2012, at 11:24 AM, Helene Bilbo wrote: > > StÃ©phane Ducasse wrote >> >>> My problem seems to be specific to the case, where a file or folder from >>> outside the Pharo window is dropped on the Morph. In this case it's >>> always >>> the World that gets to handle the drop before my Morph is even asked to >>> do >>> anything about it. >> >> Check the code in HandMorph because it is the one that we started to clean >> with igor (our cleans are not in the image). >> But the handmorph has some wonderful case statement that handle the drop >> from external >> Sorry not to be able to be more supportive. >> > > Thank you for the hint. It seems the problem lies in the fact that a > "dropFilesEvent" is different from a "dropEvent" and therefore is not > handled by MorphicEventDispatcher>>dispatchDropEvent:with: but by > MorphicEventDispatcher>>dispatchEvent:with: and they handle differently > which morph may get to process the event. > Still i have not yet a solution ;( > > http://forum.world.st/file/n4644226/Bildschirmfoto_2012-08-16_um_11.17.35.p… > > > > -- > View this message in context: http://forum.world.st/HowTo-make-a-Morph-that-accepts-dropped-files-and-fol… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 16, 2012