July 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Changing method definition at runtime

by Steven Costiou

Hello, a mean to achieve behavior modification of methods at runtime could be context oriented programming (COP). It allows a method to have multiple behavior variations that can be (de)activated dynamically. However to my knowledge there is no context oriented extension for Pharo yet. I would also be interested by any known way to change method behavior dynamically, as COP is not an option for now. Maybe by working on ast nodes, by dynamically replacing them ? Steven. Le 2016-07-23 00:41, Eric Velten de Melo a Ã©crit : > Hello, > > One thing I try to do often is changing the behaviour of a method dynamically at runtime. The current way I do this is by having a block as an instance variable and having the method call this block, but I find this approach a bit cumbersome. Is there some other way or is this the recommended approach? > > I mean, I suppose methods could be changed dynamically by means of reflection somehow, but is this an easy or recommended way of programming in Smalltalk? Should slots make things easier? > > Eric -- kloum.io

July 23, 2016

Changing method definition at runtime

by Eric Velten de Melo

Hello, One thing I try to do often is changing the behaviour of a method dynamically at runtime. The current way I do this is by having a block as an instance variable and having the method call this block, but I find this approach a bit cumbersome. Is there some other way or is this the recommended approach? I mean, I suppose methods could be changed dynamically by means of reflection somehow, but is this an easy or recommended way of programming in Smalltalk? Should slots make things easier? Eric

July 22, 2016

Re: [Pharo-users] [ANN] JSONWebToken

by Norbert Hartl

Hey Johan, didn't find it when starting my own. Mine is between 2 and 3 years old. Maybe parallel development ;) Mine is pretty basic and uses only SHA256. I implemented for internal use and just released as sven was asking. Norbert > Am 22.07.2016 um 19:20 schrieb Johan Brichau <johan(a)inceptive.be>: > > Hey Norbert, > > Also see here: http://smalltalkhub.com/#!/~JohanBrichau/Json-WebToken > > ;) > > Are you using cryptography package? > > Cheers, > Johan > >> On 22 Jul 2016, at 10:17, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Hi, >> >> thanks to the inquiry of Sven I published an implementation of JSONWebToken to smalltalkhub. It is available at >> >> http://smalltalkhub.com/#!/~NorbertHartl/JSONWebToken >> >> For those who don't know JSONWebToken or short JWT pronounced "jot" is a token format suitable for authentication and authorization. The token consist of a header, a payload and a signature. The header defines crypto algorithms, compression and other things needed to read a token on reception. The payload is called a claim set which is basically a dictionary with well-known and custom keys. If we think about OAuth or OpenId the values contained map directly to JWT claims. For OpenID connect which is an identification mechanism on top of OAuth the usage of JWT is one of the building blocks. >> >> What are the advantages in using JWT? >> >> - it defines a header for encoding the content so it is quite flexible in the ways compression and encryption of the key is done >> - defines a payload which maps arbitrary keys and there is a set of well-known keys that implementations of OAuth, OpenID can understand >> - defines a signature that makes it easy to trust the information contained or to give the token to someone who is not trusted >> - token format is a single line string so it can be used e.g. in HTTP authentication headers >> >> A problem JWT can solve: >> >> In our company we have a lot of little REST servers serving some duties. To minimize the chaos I want to have a central authentication and authorization point. If we assume having 20 images running and we look at typical way how authorization works: >> >> there is image A (Authentication), image S (Service) und client C. Client C wants to use the service S >> >> 1. client C authenticates and retrieves authorization information from A (or from S which redirects him to A) >> 2. client C hands out the authorization information to S >> 3. S needs to check at A if the information is valid (client C could have modified it or generated it) >> 4. S grants C access >> >> Taking the assumption of having 20 service images, every image would need to get back to A in order to check authorization information. The more services images you have the more load it will put on A. In a JWT use case scenario the same would look like >> >> 1. client C authenticates and receives a JWT containing authorization information. The token is signed by A >> 2. client C hands out JWT to service S >> 3. S checks the signature of A and knows that the authorization information contained is valid. >> 4. S grants C access >> >> FYI, >> >> Norbert >>

July 22, 2016

Re: [Pharo-users] System Browser "Implementors of..." drill down?

by HernÃ¡n Morales Durand

Yes, I know you like GTSpotter. But as difficult as you may find, me (and others possibly) didn't find GTSpotter so cool, or even an usable tool, so we don't feel the love you feel. Why? Well, there was too many discussions about this tool in the mailing list. On the other side, I would be *REALLY* surprised if System Browser gets replaced with Spotter. But I'd also like that you convince the guys which decides which tools goes to official image, because there is no voting here so convincing those guys will be enough, and would be super fun to sit down and read people's reaction when they open a Pharo and didn't find the classic System Browser. Maybe not a great move from the product developement POV, but will be fantastic as a terrible experiment :) HernÃ¡n 2016-07-22 7:11 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > Choosing a programming language is too > > Nonetheless GTSpotter make the navigation easier, mainly because it works > hand in hand with System Browser . So you dont have to choose one or the > other, rather find the workflow that fits your needs. Of course that will > depend on the specifics of the situation. > > Another advantage of GTSpotter is that its easier to customise to your > needs, I would not be suprised if GTSpotter at some point completely > replace System Browser. Actually I would be suprised if it does not. > > On Fri, Jul 22, 2016 at 10:27 AM HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> 2016-07-22 3:47 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >> >>> Learn to use GTSpotter , will make your experience 10 times easier and >>> faster. >>> >> >> And of course, that is completely subjective :) >> >> HernÃ¡n >> >>

July 22, 2016

Re: [Pharo-users] [ANN] JSONWebToken

by Sven Van Caekenberghe

> On 22 Jul 2016, at 19:20, Johan Brichau <johan(a)inceptive.be> wrote: > > Hey Norbert, > > Also see here: http://smalltalkhub.com/#!/~JohanBrichau/Json-WebToken > > ;) And now we have not one but two implementations ? I would guess Johan's version is more Seaside oriented, or not ? > Are you using cryptography package? > > Cheers, > Johan > > On 22 Jul 2016, at 10:17, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Hi, >> >> thanks to the inquiry of Sven I published an implementation of JSONWebToken to smalltalkhub. It is available at >> >> http://smalltalkhub.com/#!/~NorbertHartl/JSONWebToken >> >> For those who don't know JSONWebToken or short JWT pronounced "jot" is a token format suitable for authentication and authorization. The token consist of a header, a payload and a signature. The header defines crypto algorithms, compression and other things needed to read a token on reception. The payload is called a claim set which is basically a dictionary with well-known and custom keys. If we think about OAuth or OpenId the values contained map directly to JWT claims. For OpenID connect which is an identification mechanism on top of OAuth the usage of JWT is one of the building blocks. >> >> What are the advantages in using JWT? >> >> - it defines a header for encoding the content so it is quite flexible in the ways compression and encryption of the key is done >> - defines a payload which maps arbitrary keys and there is a set of well-known keys that implementations of OAuth, OpenID can understand >> - defines a signature that makes it easy to trust the information contained or to give the token to someone who is not trusted >> - token format is a single line string so it can be used e.g. in HTTP authentication headers >> >> A problem JWT can solve: >> >> In our company we have a lot of little REST servers serving some duties. To minimize the chaos I want to have a central authentication and authorization point. If we assume having 20 images running and we look at typical way how authorization works: >> >> there is image A (Authentication), image S (Service) und client C. Client C wants to use the service S >> >> 1. client C authenticates and retrieves authorization information from A (or from S which redirects him to A) >> 2. client C hands out the authorization information to S >> 3. S needs to check at A if the information is valid (client C could have modified it or generated it) >> 4. S grants C access >> >> Taking the assumption of having 20 service images, every image would need to get back to A in order to check authorization information. The more services images you have the more load it will put on A. In a JWT use case scenario the same would look like >> >> 1. client C authenticates and receives a JWT containing authorization information. The token is signed by A >> 2. client C hands out JWT to service S >> 3. S checks the signature of A and knows that the authorization information contained is valid. >> 4. S grants C access >> >> FYI, >> >> Norbert >>

July 22, 2016

Re: [Pharo-users] [ANN] JSONWebToken

by Johan Brichau

Hey Norbert, Also see here: http://smalltalkhub.com/#!/~JohanBrichau/Json-WebToken ;) Are you using cryptography package? Cheers, Johan > On 22 Jul 2016, at 10:17, Norbert Hartl <norbert(a)hartl.name> wrote: > > Hi, > > thanks to the inquiry of Sven I published an implementation of JSONWebToken to smalltalkhub. It is available at > > http://smalltalkhub.com/#!/~NorbertHartl/JSONWebToken > > For those who don't know JSONWebToken or short JWT pronounced "jot" is a token format suitable for authentication and authorization. The token consist of a header, a payload and a signature. The header defines crypto algorithms, compression and other things needed to read a token on reception. The payload is called a claim set which is basically a dictionary with well-known and custom keys. If we think about OAuth or OpenId the values contained map directly to JWT claims. For OpenID connect which is an identification mechanism on top of OAuth the usage of JWT is one of the building blocks. > > What are the advantages in using JWT? > > - it defines a header for encoding the content so it is quite flexible in the ways compression and encryption of the key is done > - defines a payload which maps arbitrary keys and there is a set of well-known keys that implementations of OAuth, OpenID can understand > - defines a signature that makes it easy to trust the information contained or to give the token to someone who is not trusted > - token format is a single line string so it can be used e.g. in HTTP authentication headers > > A problem JWT can solve: > > In our company we have a lot of little REST servers serving some duties. To minimize the chaos I want to have a central authentication and authorization point. If we assume having 20 images running and we look at typical way how authorization works: > > there is image A (Authentication), image S (Service) und client C. Client C wants to use the service S > > 1. client C authenticates and retrieves authorization information from A (or from S which redirects him to A) > 2. client C hands out the authorization information to S > 3. S needs to check at A if the information is valid (client C could have modified it or generated it) > 4. S grants C access > > Taking the assumption of having 20 service images, every image would need to get back to A in order to check authorization information. The more services images you have the more load it will put on A. In a JWT use case scenario the same would look like > > 1. client C authenticates and receives a JWT containing authorization information. The token is signed by A > 2. client C hands out JWT to service S > 3. S checks the signature of A and knows that the authorization information contained is valid. > 4. S grants C access > > FYI, > > Norbert >

July 22, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 22/07/16 08:41, Thibault ARLOING wrote: > Features > > * Check phase to check syntax > * EPub exporter for e-books (use pillar archetypes for this) > * Semantic links to Youtube and Wikipedia > * Citations for LaTeX > * Structures (see Pillar documentation) > * Footnotes for HTML, Markdown, LaTeX and AsciiDoc > * Improvement of parsing configuration failure message > Nice to see footnotes and citations. That were two missing features for me that were provided for pandoc. I need to see Zotero integration for bibliographic references (using [@keyword] aliases in pandoc's case), but these new features made the documentation system richer and show Pillar advancing in good directions. Congrats and keep the good work, Offray

July 22, 2016

data driven web apps - reactivity - how to do that in Pharo/Zn ?

by CÃ©drick BÃ©ler

Hi all, I would like to have a reactive approach in a web client, i.e. when the data changes in the server or the client the change is propagatedâ¦ I liked this when trying meteor and DDP (its data driven protocol). I now use Zinc with templates using mustache. Itâs quite straightforward.Now Iâd like to have the Â« reactivity Â» dimension. Do you have any pointer or ideas ? Iâm having a look right now at these solutions: - mapless + redis (http://sebastianconcept.github.io/Mapless/) I donât know if usable - doesnât load form the catalog - http://knockoutjs.com Anyone tried that ? Iâm having a look (donât really see how to manage the model in js) - other jsframeworks - React, Ractive, https://rrees.me/2015/06/04/overview-of-javascript-reactive-frameworks/ - porting DDP - not trivial - http://smalltalkhub.com/#!/~Guille/ReactiveExtensions I donât know if any relationâ¦ TIA, CÃ©drik

July 22, 2016

[ANN] Pillar 4.0.0

by Thibault ARLOING

Hello, I'm happy to announce the latest release of Pillar. This release has been possible because of the hard work of Damien Cassou, Cyril Ferlicot, Yann Dubois, Thibault Arloing and Lukas Komarek. What did it bring and what are the largest changes ? * Huge cleaning of code and Dependencies * Many bug fixes * Huge refactoring of internal parts * Extract phase management into an external project (LightPhaser) * Transformers and Phases are all Pipes Remove Compilation cycle * Remove template handling from Pillar * Remove generation of pillarpostExport.sh * Pillar now exports files to JSON format * Command for pillar archetypes "./pillar archetype book", book can be replaced by other archetype names (see Pillar documentation) * Possibility to load an archetype with a Makefile to compile pillar files Features * Check phase to check syntax * EPub exporter for e-books (use pillar archetypes for this) * Semantic links to Youtube and Wikipedia * Citations for LaTeX * Structures (see Pillar documentation) * Footnotes for HTML, Markdown, LaTeX and AsciiDoc * Improvement of parsing configuration failure message Major changes * Metadata field in configuration to separate data from configuration properties * Support files in configuration does no longer exists * "disableTransformers" property is now named "disabledPhases" * AsciiDoc file extension is now ".asciidoc" * Pillar now manages one input file, not a collection of input files anymore * Parameter inputFiles is now replaced by inputFile The documentation of Pillar will be update as soon as possible to fit those changes. Cheers, Thibault

July 22, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] JSONWebToken

by Andy Burnett

I am really interested in this work on JWT. We've been using it quite a lot. For instance we use JWT to link an application written in PHP to a Firebase backend. Works beautifully. The thing that I am still trying to wrap my head around, is whether there is a â standard â way of using the claims asserted in the JWT token to control access to objects in a Pharo/seaside application. I know that gemstone has an access control list system but does anything like that exist in Pharo? If not, how do people control access to the data? Cheers Andy,

July 22, 2016