May 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Reddit example

by Sven Van Caekenberghe

Did you follow the detailed instructions in the appendix of https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53… ? There is even a pre-built image. BTW, you are mixing packages & configurations. Sven > On 30 May 2015, at 01:11, recursive68(a)gmail.com wrote: > > Hi, > > I'm trying to load the Reddit example from SmalltalkHub (Monticello), it fails with: > > This package depends on the following classes: > DescriptorSystem > You must resolve these dependencies before you will be able to load these definitions: > RedditSchema > allTableNames > classModelForRedditLink: > constructAllClasses > descriptorForRedditLink: > tableForREDDIT_LINKS: > > and also tried loading mcz file directly that fails to. > > If I try to install using: > > MCHttpRepository > location: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Reddit/main' > user: '' > password: '' > > It fails with an incorrect url: http://http ... when attempting to pull some package. > > This is using Pharo 4. > > Thanks

May 30, 2015

Re: [Pharo-users] Issue with UDP Sockets

by Ben Coman

On Sat, May 30, 2015 at 12:23 AM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > P.S. On the plus side, I'm now able to turn my PC into a better remote for multi-cam GoPro setups than the GoPro remote itself is :) That is cool to hear. Now as much as frameworks are important, I think cool little end-user apps like this are important to hook people into Pharo. You really need only *one* feature that people find compelling. Do you need any community support to polish it, then push it on GoPro sites? (not that I have a GoPro, but maybe I'll need to get one) cheers -ben

May 30, 2015

Re: [Pharo-users] Playground inspector and the self variable

by Ben Coman

On Sat, May 30, 2015 at 12:15 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Also... I find myself accidentally closing the whole Playground in an > attempt to just close the inspector. > > I know this is related with me not being the smartest guy in the > block, but I'm so used to discard inspectors, and when you're somehow > deep inspecting you completely forgot you started in a "workspace". But there are other not-smart people ;) so we should consider your use case cheers -ben > > > > Esteban A. Maringolo > > > 2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> 2015-05-29 12:36 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >>> Hi, >>> >>> Indeed, this part of the inspector will be revisited for Pharo 5. >> >> Good. I'm sure this can be backported easily ;) >> >>> But, what exactly do you mean by " I just want to select it to run an >>> expression where self refers to the inspected object"? >> >> I have the strong habit of running expressions (it is, send messages) >> to objects directly in the inspector, in the case of the example >> array, I can fiddle selecting the different elements in the array and >> finally select the array itself ("self") to select as the receiver. I >> expect to write these expression on the pane of the right, even when I >> could do it on the pane of the left. >> >> I hope I explained myself. :) >> >> >> Esteban A. Maringolo >

May 30, 2015

Reddit example

by recursive68＠gmail.com

Hi, I'm trying to load the Reddit example from SmalltalkHub (Monticello), it fails with: This package depends on the following classes: DescriptorSystem You must resolve these dependencies before you will be able to load these definitions: RedditSchema allTableNames classModelForRedditLink: constructAllClasses descriptorForRedditLink: tableForREDDIT_LINKS: and also tried loading mcz file directly that fails to. If I try to install using: MCHttpRepository location: 'http://smalltalkhub.com/mc/SvenVanCaekenberghe/Reddit/main' user: '' password: '' It fails with an incorrect url: http://http ... when attempting to pull some package. This is using Pharo 4. Thanks

May 29, 2015

Re: [Pharo-users] Issue with UDP Sockets

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I am sure you will blog about this ! Yes, pleeeeeeease!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-with-UDP-Sockets-tp4827014p4829352.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 29, 2015

Re: [Pharo-users] Playground inspector and the self variable

by Tudor Girba

Hi, Indeed, this is a usability issue. However, your code is not lost. You can find the playground easily, and if you inspect the same objects, the raw presentation will show you the last entered code for each class. Cheers, Doru On Fri, May 29, 2015 at 6:15 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Also... I find myself accidentally closing the whole Playground in an > attempt to just close the inspector. > > I know this is related with me not being the smartest guy in the > block, but I'm so used to discard inspectors, and when you're somehow > deep inspecting you completely forgot you started in a "workspace". > > > > Esteban A. Maringolo > > > 2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > > 2015-05-29 12:36 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi, > >> > >> Indeed, this part of the inspector will be revisited for Pharo 5. > > > > Good. I'm sure this can be backported easily ;) > > > >> But, what exactly do you mean by " I just want to select it to run an > >> expression where self refers to the inspected object"? > > > > I have the strong habit of running expressions (it is, send messages) > > to objects directly in the inspector, in the case of the example > > array, I can fiddle selecting the different elements in the array and > > finally select the array itself ("self") to select as the receiver. I > > expect to write these expression on the pane of the right, even when I > > could do it on the pane of the left. > > > > I hope I explained myself. :) > > > > > > Esteban A. Maringolo > > -- www.tudorgirba.com "Every thing has its own flow"

May 29, 2015

Re: [Pharo-users] Playground inspector and the self variable

by Tudor Girba

Hi Esteban, On Fri, May 29, 2015 at 5:42 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2015-05-29 12:36 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > > > Indeed, this part of the inspector will be revisited for Pharo 5. > > Good. I'm sure this can be backported easily ;) It won't because this will be a new implementation :). > > > But, what exactly do you mean by " I just want to select it to run an > > expression where self refers to the inspected object"? > > I have the strong habit of running expressions (it is, send messages) > to objects directly in the inspector, in the case of the example > array, I can fiddle selecting the different elements in the array and > finally select the array itself ("self") to select as the receiver. I > expect to write these expression on the pane of the right, even when I > could do it on the pane of the left. > > I hope I explained myself. :) I still do not quite understand where the problem is. Could you give me a step by step description? Cheers, Doru > > > Esteban A. Maringolo > > -- www.tudorgirba.com "Every thing has its own flow"

May 29, 2015

Re: [Pharo-users] Issue with UDP Sockets

by Sven Van Caekenberghe

> On 29 May 2015, at 18:23, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> >> On 19 May 2015, at 11:01 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 19 May 2015, at 10:53, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >>> >>>> Did you look in all your package caches ? >>> I did. Must have been a victim of cleaning ... but maybe TimeMachine has something ... thanks for the reminder. >>> >>>> If it is just a small example, like one class, maybe it could be >>>> added to the image, in which case it should indeed be a slice. >>> The package was pretty simple. Basically only adding a few convenience methods around Socket>>#setOption:value: . Still I think a usage example in form of a class comment and test case might be appropriate. So unless Multicast should be part of the base image I'll start with a separate package first. >> >> Since Socket is a fundamental part, and multicast is a key feature, I think it would logical to move it to the image itself, with a test case. > > It's not just multicast... > As a Socket newbie I recently spent longer than I care to admit learning you need to set SO_BROADCAST to true to not get a primitive failure when sending to a broadcast address. > At least the comments in sqUnixSocket were entertaining! > > Though I realize which options are actually supported depends on the VM, moving the list of potentially available cross-platform options (and a description of what they're used for) to a comment in the image (setOption: value: being the obvious location) might be a nice first step. Please help in the documentation effort. > Cheers, > Henry > > P.S. On the plus side, I'm now able to turn my PC into a better remote for multi-cam GoPro setups than the GoPro remote itself is :) I am sure you will blog about this !

May 29, 2015

Re: [Pharo-users] Issue with UDP Sockets

by Henrik Johansen

> On 19 May 2015, at 11:01 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 19 May 2015, at 10:53, Udo Schneider <udo.schneider(a)homeaddress.de> wrote: >> >>> Did you look in all your package caches ? >> I did. Must have been a victim of cleaning ... but maybe TimeMachine has something ... thanks for the reminder. >> >>> If it is just a small example, like one class, maybe it could be >>> added to the image, in which case it should indeed be a slice. >> The package was pretty simple. Basically only adding a few convenience methods around Socket>>#setOption:value: . Still I think a usage example in form of a class comment and test case might be appropriate. So unless Multicast should be part of the base image I'll start with a separate package first. > > Since Socket is a fundamental part, and multicast is a key feature, I think it would logical to move it to the image itself, with a test case. It's not just multicast... As a Socket newbie I recently spent longer than I care to admit learning you need to set SO_BROADCAST to true to not get a primitive failure when sending to a broadcast address. At least the comments in sqUnixSocket were entertaining! Though I realize which options are actually supported depends on the VM, moving the list of potentially available cross-platform options (and a description of what they're used for) to a comment in the image (setOption: value: being the obvious location) might be a nice first step. Cheers, Henry P.S. On the plus side, I'm now able to turn my PC into a better remote for multi-cam GoPro setups than the GoPro remote itself is :)

May 29, 2015

Re: [Pharo-users] Playground inspector and the self variable

by Esteban A. Maringolo

Also... I find myself accidentally closing the whole Playground in an attempt to just close the inspector. I know this is related with me not being the smartest guy in the block, but I'm so used to discard inspectors, and when you're somehow deep inspecting you completely forgot you started in a "workspace". Esteban A. Maringolo 2015-05-29 12:42 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2015-05-29 12:36 GMT-03:00 Tudor Girba <tudor(a)tudorgirba.com>: >> Hi, >> >> Indeed, this part of the inspector will be revisited for Pharo 5. > > Good. I'm sure this can be backported easily ;) > >> But, what exactly do you mean by " I just want to select it to run an >> expression where self refers to the inspected object"? > > I have the strong habit of running expressions (it is, send messages) > to objects directly in the inspector, in the case of the example > array, I can fiddle selecting the different elements in the array and > finally select the array itself ("self") to select as the receiver. I > expect to write these expression on the pane of the right, even when I > could do it on the pane of the left. > > I hope I explained myself. :) > > > Esteban A. Maringolo

May 29, 2015