- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Update] Zinc-SSO OAuth 2.0 Alpha Code & Live Demos

by Sven Van Caekenberghe

Hi Sean, On 23 Dec 2012, at 22:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote >> As mentioned here before, there is a project underway to add support for >> OAuth & OpenID to Zinc HTTP Components and thus to Pharo Smalltalk as >> well. > > Cool! I've wanted to post to twitter from Pharo via their API, but quickly > turned and ran when I got into OAuth (I know they still use v. 1 and this > won't help). It's awesome to see some social media interconnection becoming > easier. It will be fun to see what people do with it... Jan told me that OAuth version 1 support, including a Twitter demo is on its wayâ¦ Sven

Dec. 23, 2012

Re: [Pharo-project] [Update] Zinc-SSO OAuth 2.0 Alpha Code & Live Demos

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > As mentioned here before, there is a project underway to add support for > OAuth & OpenID to Zinc HTTP Components and thus to Pharo Smalltalk as > well. Cool! I've wanted to post to twitter from Pharo via their API, but quickly turned and ran when I got into OAuth (I know they still use v. 1 and this won't help). It's awesome to see some social media interconnection becoming easier. It will be fun to see what people do with it... -- View this message in context: http://forum.world.st/Update-Zinc-SSO-OAuth-2-0-Alpha-Code-Live-Demos-tp466… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 23, 2012

[Pharo-project] [Update] Zinc-SSO OAuth 2.0 Alpha Code & Live Demos

by Sven Van Caekenberghe

Hi, As mentioned here before, there is a project underway to add support for OAuth & OpenID to Zinc HTTP Components and thus to Pharo Smalltalk as well. Zinc-SSO as the project is called is not yet finished but we would like to share some alpha code and our live demos: based on Jan van de Sandt's earlier CloudforkSSO work, we now have OAuth2 basically working. Partial documentation can be found here https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md The document includes pointers to the repository where the development takes place. Note that the document itself is far from finished. This is not a subject where loading some code gives you a working demo since there is some setup to be done. Therefor we orginanized two live demos: http://sso.stfx.eu http://sso.doit.st Both allow you to use your existing Google, Facebook or Microsoft credentials (username/password) to authenticate and login to a simple demo web application. You actually grant the Zinc SSO Demo application access to view some of your basic user data - since the demo application then receives that grant it knows that you are the owner of that identity and that it can thus use it as a login. Also, as your browser probably stays logged in to the larger provider, this effectively comes down to single sign on (SSO). The first demo is running on top of Zinc only, the second demo uses Seaside for its user interface. Both use the same Zinc-SSO-OAuth2-Core code, Zinc HTTP Components, Zodiac and NeoJSON. Regards, Jan & Sven PS: We would like to thank Andy Burnett of Knowinnovation Inc and ESUG for sponsoring this open source work. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 23, 2012

[Pharo-project] Error 400 when pushing to Smalltalk with metacello

by Damien Pollet

When I use the metacello convenience method #saveModifiedPackagesAndConfiguration: my package mcz uploads fine but then I often get a 400 error for the configuration mcz (I would not say systematic but most of the time). But if I go to monticello and copy it to smalltalkhub from the package cache, it goes fine. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Dec. 23, 2012

Re: [Pharo-project] A contorted way of making things work :)

by StÃ©phane Ducasse

On Dec 23, 2012, at 5:09 PM, Igor Stasenko wrote: > On 23 December 2012 16:54, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: >> Is there a list of the pitfalls of morphic somewhere ? >> > How dare you! :) > > Of course there's no such thing. - global positioning - too many responsibilities for example handMorph - too many duplicated logic (border is one) - isKindOf: usage > Morphic was developed on premise that you are clever enough to > understand it by reading code. > > P.S. Don't think that i want to blame anyone, or discourage from using it. > Morphic based on a very good concepts. And i really like it. > But then, lack of documentation, lack of systematic approach > and no review process has led it to what we have now. This is why we should start to systematically rethink it and clean it. :)

Dec. 23, 2012

Re: [Pharo-project] A contorted way of making things work :)

by Igor Stasenko

On 23 December 2012 16:54, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > Is there a list of the pitfalls of morphic somewhere ? > How dare you! :) Of course there's no such thing. Morphic was developed on premise that you are clever enough to understand it by reading code. P.S. Don't think that i want to blame anyone, or discourage from using it. Morphic based on a very good concepts. And i really like it. But then, lack of documentation, lack of systematic approach and no review process has led it to what we have now. -- Best regards, Igor Stasenko.

Dec. 23, 2012

Re: [Pharo-project] A contorted way of making things work :)

by dimitris chloupis

Is there a list of the pitfalls of morphic somewhere ? ________________________________ From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> To: Pharo-project(a)lists.gforge.inria.fr Sent: Sunday, 23 December 2012, 17:19 Subject: Re: [Pharo-project] A contorted way of making things work :) >>> Yeah, blame and flame everyone who doesn't write code the way you do... >>> But before you do that, tell me what's wrong with that assignment. >> >> why do I always have the impression you're at extinction when I read >> an email from you? I know I can be very annoying as well :D but you > > If I understand correctly what you're trying to say, then the reason why I don't write mails here more often is because it's pointless. > >> should consider a friendlier tone ;) > > Do you think my question would have been answered if I were using a friendlier tone? I doubt it. > Do you think the mail I was replying to was friendlier than mine? I doubt it. Levente We do not consider you as a asshole or whatever. I personally always consider what you are writing with interest and you do not need to write it in a blunt way for that. I do not know why you think that sending emails here is pointless but this is not true. We value feedback, questions and remarks of people. My objective is to build an ecosystem where people can make business and invent their future, no more. Now for this exact point, morphic has some dark corners and we should address them one by one and we will. Now if certain invariants would be clear and respected the code would be in general much nicer. Stef

Dec. 23, 2012

[Pharo-project] [update 2.0] #20452

by StÃ©phane Ducasse

Dec. 23, 2012

Re: [Pharo-project] A contorted way of making things work :)

by StÃ©phane Ducasse

>>> Yeah, blame and flame everyone who doesn't write code the way you do... >>> But before you do that, tell me what's wrong with that assignment. >> >> why do I always have the impression you're at extinction when I read >> an email from you? I know I can be very annoying as well :D but you > > If I understand correctly what you're trying to say, then the reason why I don't write mails here more often is because it's pointless. > >> should consider a friendlier tone ;) > > Do you think my question would have been answered if I were using a friendlier tone? I doubt it. > Do you think the mail I was replying to was friendlier than mine? I doubt it. Levente We do not consider you as a asshole or whatever. I personally always consider what you are writing with interest and you do not need to write it in a blunt way for that. I do not know why you think that sending emails here is pointless but this is not true. We value feedback, questions and remarks of people. My objective is to build an ecosystem where people can make business and invent their future, no more. Now for this exact point, morphic has some dark corners and we should address them one by one and we will. Now if certain invariants would be clear and respected the code would be in general much nicer. Stef

Dec. 23, 2012

Re: [Pharo-project] KeyChain/UsersManager

by StÃ©phane Ducasse

Yes In fact usman got interested by the package because we should deploy application to clients with restriction. Now we should rethink it if this is to be integrated in the image. Now one of the problem is that benjmain cannot manage it completely with a configuration because some code can only be applied using CS and this is this point that we should look at. Stef > Firstly we need to aswer on question how deep this mechanism should be > integrated with the kernel. If kernel should be able to work without > UsersManger, if Monticello and Metacello should be able to work > without UsersManager, if we should provide some basic minimal > UsersManager implementation etc. > > currently the have problems with this methods: > Author>>fullNamePerSe > Author>>fullName: > MCHttpRepository>>password > MCHttpRepository>>user > > -- Pavel > > On Sun, Dec 23, 2012 at 2:13 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Yes we should unload it. >> Now I would like to know what are the hooks that we need in the kernel to support its smooth loading. >> >> Stef >> >> On Dec 23, 2012, at 1:48 PM, Pavel Krivanek wrote: >> >>> There is a lot of reasons why I think that the whole concept of >>> UsersManager is poor: >>> - direct dependency on cryptography packages >>> - there is only one current user. What about if more users is >>> connected to one image? >>> - users avatar as an ImageMorph! >>> - permissions do not reflect modular architecture. Why to have >>> permissions like canBrowse canDebug canEditCode canEvaluateCode >>> canInspect canShowMorphHalo for image that has now browser, no >>> debugger, no editor, no inspector, no compiler, no Morphic? >>> - in Smalltalk this permissions bring no real security >>> - UsersManager is not an abstract class >>> - everything is in one package >>> >>> Thanks to this addition in current state the Pharo Kernel is not able >>> to load Monticello packages and in most cases even start. We really >>> need to reject it for Pharo 2.0. >>> >>> Cheers, >>> -- Pavel >>> >>> On Thu, Dec 20, 2012 at 5:23 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> I think that we should remove the keyChain and it would be good that the system offers the right hooks so that keychain can be nicely added. >>>> Apparently ben add to provide a cs because some changes could not be applied via a slice. >>>> I planned to have a look but so far I did not find the time. >>>> >>>> >>>> >>>> On Dec 20, 2012, at 2:07 PM, Pavel Krivanek wrote: >>>> >>>>> It broke following Pharo Kernel jobs because the image crashes when a >>>>> directory is changed. So how to fix that. We have several options: >>>>> - make simple ugly fix that will check presence of this class, it will >>>>> generate unimplemented calls >>>>> - remove it and add it back fixed in 3.0 >>>>> - rewrite the Author change mechanism to Announcements (in 3.0?) >>>>> What do you propose? >>>>> >>>>> -- Pavel >>>>> >>>>> On Sat, Dec 15, 2012 at 3:01 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>> it was in the list of things to integrate :) >>>>>> but we should check to clean the dependence, because is not good. >>>>>> >>>>>> Esteban >>>>>> >>>>>> On Dec 15, 2012, at 2:16 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> what is the reason for integration of KeyChain/UsersManager to the image? It created the next kernel dependency. Should it replace Author? Should it be in the Pharo Kernel? And why there was no mention about it in this mailing list before? ;-) >>>>>>> >>>>>>> Cheers, >>>>>>> -- Pavel >>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >> >

Dec. 23, 2012