- Pharo-users - lists.pharo.org

Re: [Pharo-users] Zinc and Oauth2

by Sven Van Caekenberghe

Davide, The main Zinc repository is now https://github.com/svenvc/zinc (although the old ones are also still good). You should look at the baseline, but loading group SSO will get you started. I am not actively using OAuth, but several people have, so it should work (the code did not change in a long while). This is not such a simple subject though (there are several demos that used to work). Good luck, Sven > On 28 Mar 2019, at 20:54, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Davide Varvello <varvello(a)yahoo.com> > Subject: Zinc and Oauth2 > Date: 28 March 2019 at 20:54:05 GMT+1 > To: pharo-users(a)lists.pharo.org > > > Hi Guys, > I'm trying to play with Outh2, but I'm wondering how to download it in > Pharo. > > If I use the Gofer as indicated here: > https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > It returns an error. > Can you help me please? > > TIA > Davide > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

March 28, 2019

Zinc and Oauth2

by Davide Varvello

Hi Guys, I'm trying to play with Outh2, but I'm wondering how to download it in Pharo. If I use the Gofer as indicated here: https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md Gofer it url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. It returns an error. Can you help me please? TIA Davide -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 28, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Peter Kenny

Tim I found myself puzzling as to *why* James's solution works. This longer explanation helped me to understand. First, generalize moving forward to moving an arbitrary number of steps, still with wrapping. ^list at: (index + move - 1 \\ size + 1 Second, realize that moving backward one step with wrapping is exactly equivalent to moving forward (size - 1) steps - because of wrapping, a move of size steps is null. Finally, substitute move = size - 1. ^list at: (index + size - 2 \\ size + 1. This can of course easily generalize to backward moves of any size. HTH Peter Kenny -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 28, 2019

Re: [Pharo-users] Text presenter autosave features

by Offray Vladimir Luna CÃ¡rdenas

Hi, Just a remainder if anyone can help with this... Thanks, Offray On 23/03/19 12:44 p. m., Offray Vladimir Luna CÃ¡rdenas wrote: > Hi, > > While migrating Grafoscopio from Pharo 6.x to Pharo 7.x., I noticed > that auto save for text fields is not enabled. Previously, when I > wrote something in a text field, the dirty mark in the upper right > corner appeared and if autoAccept was enabled, the text was > automatically saved. Now with Pharo 7.x the dirty mark don't appear at > all, and is not making any auto-saving. > > * I see that TextPresenter is the one who is responsible for such text > objects. There is any minimal example I can use to test the proper > behavior? > > * There is any way to use WelcomeHelp class to get a similar behavior? > > Thanks, > > Offray > > >

March 28, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by James Foster

One of my recent assignments to first-year programming students was to model Left-Center-Right (https://en.wikipedia.org/wiki/LCR_(dice_game)) <https://en.wikipedia.org/wiki/LCR_(dice_game))> where they needed to do just what you are trying to do. | size stream | size := 10. stream := WriteStream on: String new. 1 to: size do: [:i | stream print: i; tab; print: i \\ size + 1; tab; print: i + size - 2 \\ size + 1; tab; cr. ]. stream contents > On Mar 28, 2019, at 8:12 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > Hey guys - Iâm wondering if someone might have a nice way of selecting the previous value in a list - but wrapping around to the last value if you are at the front. > > Essentially I have an exercise with some values in a collection like: > > list := #($a $e $o $u). > > And I have an index into the list, and want to loop around from index 1, back to 4 when I hit the beginning of the list. > > While moving forwards is pretty easy with mod - e.g. > > ^list at: (index \\ list size + 1) > > Iâm struggling with the cleanest way to do this backwards - as the following is unreadable to me (assuming index = 1) > > ^list at: (index - 2 \\ list size + 1) > > And then I tried (which isn't bad - but still not quite right). > > ^list before: (list at: index) ifAbsent: [ids last]. > > > Iâm sure there is a better way to do this - but itâs alluding me? > > Tim > > > >

March 28, 2019

Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Tim Mackinnon

Hey guys - Iâm wondering if someone might have a nice way of selecting the previous value in a list - but wrapping around to the last value if you are at the front. Essentially I have an exercise with some values in a collection like: list := #($a $e $o $u). And I have an index into the list, and want to loop around from index 1, back to 4 when I hit the beginning of the list. While moving forwards is pretty easy with mod - e.g. ^list at: (index \\ list size + 1) Iâm struggling with the cleanest way to do this backwards - as the following is unreadable to me (assuming index = 1) ^list at: (index - 2 \\ list size + 1) And then I tried (which isn't bad - but still not quite right). ^list before: (list at: index) ifAbsent: [ids last]. Iâm sure there is a better way to do this - but itâs alluding me? Tim

March 28, 2019

Re: [Pharo-users] Resolving DNS in-image

by Holger Freyther

> On 28. Mar 2019, at 08:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Holger & Norbert, > great. Regardless of how many versions exist. We should get one into the image with proper platform integration. I wasn't aware of your code but I assumed it is something you could write, hence the Paleo prefix. Now that the Paleo code is the Neo one is more funny... > NeoSimplifiedDNSClient default addressForName: 'pharo.org'. "104.28.27.35" > > One of my goals was to use it as a more reliable, non-blocking 'do we have internet access' test: > > NeoNetworkState default hasInternetConnection. "true" What is internet access and how would this be used? Is this about captive portals? With local network policy the big anycast services might be blocked but the user can still reach services. Or with deployed microservices they might reach other but not the outside? ... snip ... > The main problems are concurrent and asynchronous requests, as well as error handling. > > I would be great if we could do this well in-image. (But getting OS DNS settings is hard too). > > We should talk ;-) Agreed that getting the OS DNS settings is hard but not impossible (go seems to get away with its implementation on unix). It seems we manage to honor platform settings for http proxies and I am confident we can do it for DNS as well. I planned to solve concurrency by creating one stub resolver per request and having a shared cache. The internet can be a hostile place and DNS is an easy victim. Cache poisoning does exist and random source port, 0x20 randomization, random transaction ids, disrespecting PTMU ICMP messages are the few mitigations we have. Let's definitely talk. I hang out in the pharo discord group. :) holger

March 28, 2019

Re: [Pharo-users] Resolving DNS in-image

by Sven Van Caekenberghe

Hi Holger & Norbert, Great, but ... This did already exist in various forms, a couple of years ago I made a newer version, they can all be found in http://www.smalltalkhub.com/#!/~BenComan/DNS/ - including unit tests (but some of the older code in there is a bit stale). It covers most record types, but most of them are not used a lot. Simple usage: NeoSimplifiedDNSClient default addressForName: 'pharo.org'. "104.28.27.35" One of my goals was to use it as a more reliable, non-blocking 'do we have internet access' test: NeoNetworkState default hasInternetConnection. "true" >From the class comments: ======================= I am NeoSimplifiedDNSClient. I resolve fully qualified hostnames into low level IP addresses. NeoSimplifiedDNSClient default addressForName: 'stfx.eu'. I use the UDP DNS protocol. I handle localhost and dot-decimal notation. I can be used to resolve Multicast DNS addresses too. NeoSimplifiedDNSClient new useMulticastDNS; addressForName: 'zappy.local'. Implementation I execute requests sequentially and do not cache results. This means that only one request can be active at any single moment. It is technically not really necessary to use my default instance as I do not hold state. ==================================== I am NeoDNSClient. I am a NeoSimplifiedDNSClient. NeoDNSClient default addressForName: 'stfx.eu'. I add caching respecting ttl to DNS requests. I allow for multiple outstanding requests to be handled concurrently. Implementation UDP requests are asynchroneous and unreliable by definition. Since DNS requests can take some time, it should be possible to have multiple in flight at the same time, thus concurrently. Replies will arrive out of order and need to be matched to their outstanding request by id. If a request has been seen before and its response is not expired, it will be answered from the cache. Each incoming request is handled by creating a NeoDNSRequest object and adding that to the request queue. This triggers the start up of the backend process, if necessary. The client then waits on the semaphore inside the request object, limited by the timeout. The backend process loops while there are still outstanding requests that have not expired. It sends all unsent requests at once, and then listens briefly for incoming replies. It cleans up expired requests. When a reply comes in, it is connected to its request by id. The semaphore in the request object is then signalled so that the waiting client can continue and the request is removed from the queue. The process then loops. If the queue is empty, the backend process stops. ================ But that last one is less reliable, it was my last addition. The main problems are concurrent and asynchronous requests, as well as error handling. I would be great if we could do this well in-image. (But getting OS DNS settings is hard too). We should talk ;-) Sven > On 28 Mar 2019, at 01:32, Holger Freyther <holger(a)freyther.de> wrote: > > Norbert and me looked at using DNS for service discovery and ran into some of the limitations of the NetNameResolver[1]. In the end I created an initial DNS implementation in Pharo called Paleo-DNS[2] to overcome these. > > DNS is a protocol we use every day but rarely think of. There is an active IETF community that is evolving the protocol and finding new usages (service discovery is one of them). > > In DNS there are different types of resource records (RR). The most commonly used ones in a client ("stub") are "A" for IPv4 addresses, "AAAA" for IPv6 addresses, "CNAME" for aliases, "SRV" records. So far only support for "A" records was implemented. > > So if you are curious about DNS then this is a great opportunity to add your favorite RR implementation to it and send a PR. There are probably 20+ of them to go. ;) > > > Query example using DNS-over-TLS (DoT) to Google Public DNS > > PaleoDNSTLSTransport new > destAddress: #[8 8 4 4] port: 853; > timeout: 2 seconds; > query: (PaleoDNSQuery new > transactionId: (SharedRandom globalGenerator nextInt: 65535); > addQuestion: (PaleoRRA new rr_name: 'pharo.org.'); > addAdditional: (PaleoRROpt new udpPayloadSize: 4096)) > > > [1] It's blocking on Unix, on Mac only one look-up may occur at a time and it returns exactly one address. There is also no IPv6 support. > > [2] https://github.com/zecke/paleo-dns

March 28, 2019

[ANN] Pharo Launcher 1.8.1 released

by Christophe Demarey

Hi all, Pharo Launcher 1.8.1 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. Here is the changelog: Bug fixes: #326 Edit image description doesn't update when editing existing description #325 Instance of MacProcess did not understand #waitForCommand: #324 sources file not found for Pharo < 3.0 #321 abort process if not responding. Uses TaskIt Improvements: #239 Mac OS menus display "SqueakOSXApp" instead of Â« PharoLauncher Â» #323 Check if pharo-version.st should be updated #322 do not try to run image without preferences if not supported by the image Thanks to all contributors, including issue reports. Regards, The Pharo team.

March 28, 2019

Resolving DNS in-image

by Holger Freyther

Norbert and me looked at using DNS for service discovery and ran into some of the limitations of the NetNameResolver[1]. In the end I created an initial DNS implementation in Pharo called Paleo-DNS[2] to overcome these. DNS is a protocol we use every day but rarely think of. There is an active IETF community that is evolving the protocol and finding new usages (service discovery is one of them). In DNS there are different types of resource records (RR). The most commonly used ones in a client ("stub") are "A" for IPv4 addresses, "AAAA" for IPv6 addresses, "CNAME" for aliases, "SRV" records. So far only support for "A" records was implemented. So if you are curious about DNS then this is a great opportunity to add your favorite RR implementation to it and send a PR. There are probably 20+ of them to go. ;) Query example using DNS-over-TLS (DoT) to Google Public DNS PaleoDNSTLSTransport new destAddress: #[8 8 4 4] port: 853; timeout: 2 seconds; query: (PaleoDNSQuery new transactionId: (SharedRandom globalGenerator nextInt: 65535); addQuestion: (PaleoRRA new rr_name: 'pharo.org.'); addAdditional: (PaleoRROpt new udpPayloadSize: 4096)) [1] It's blocking on Unix, on Mac only one look-up may occur at a time and it returns exactly one address. There is also no IPv6 support. [2] https://github.com/zecke/paleo-dns

March 28, 2019