February 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo & LDAP

by Olivier Auverlot

Hi, For a project of REST services with Pharo and Seaside, I need to send requests to an LDAP server. I found a project named LDAPlayer on squeaksource. Now, I can create a connection and do a request to the LDAP server. But... my problem is to read an attribute in the result. In the LDAPSearchResultEntry object, the method to get a value is : attrAt: aKey | selected | selected := attrs at: (aKey asByteArray) ifAbsent: [ ^ nil ]. ^ selected first asString. The problem seems to be on the third line with the use of the asByteArray method. Why used this method ? For my tests, I remplaced it with : selected := attrs at: aKey ifAbsent: [ ^ nil ]. And now, it's ok but I don't know if my modification could introduce others problems. What do you think about that ? Someone has used LDAPlayer with Pharo ? Best regards Olivier ;-) www.auverlot.fr

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Jan van de Sandt

No, CloudforkSSO only supports HMAC-SHA1 signatures. This is enough to work with the major providers. You do need to handle https requests. But I learned that this can be done with a plain HttpClient and stunnel. Jan. On Wed, Feb 16, 2011 at 1:57 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > On 16.02.2011, at 13:55, Jan van de Sandt wrote: > > Hi Norbert, > > No, there is no GemStone port yet and I don't have any experience with > GemStone. It should not be too difficult I think. > > Isn't there a lot of crypto stuff involved? > > Norbert > > On Wed, Feb 16, 2011 at 1:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> On 16.02.2011, at 13:09, Jan van de Sandt wrote: >> >> Hi Janko, >> >> CloudforkSSO has its own small portability layer. The library is already >> ported to VA Smalltalk. A VisualWorks version will be available within a few >> days. >> >> CloudforkSSO uses an abstract HttpClient class that has a different >> concrete subclass for each platform. So no need for socket level >> portability. For future versions we were thinking about using Grease. The >> main reason for this is portable UTF-8 support. >> >> That would be great! I would like to have these on gemstone. Did you take >> any effort in supporting this? >> >> Norbert >> >> >> 2011/2/16 Janko MivÅ¡ek <janko.mivsek(a)eranova.si> >> >>> Hi Jan, >>> >>> On 16. 02. 2011 12:18, Jan van de Sandt wrote: >>> >>> > Porting CloudforkSSO to AIDA should be pretty easy. The OAuth and >>> OpenID >>> > base classes use WAUrl and the JSON classes of Seaside. AIDA probably >>> > has good alternatives for these. >>> >>> Good to know that! Another issue could be a portability. Aida is always >>> up-to-date on Squeak/Pharo and VisualWorks thanks to a big care that all >>> code is portable upfront. >>> >>> How is CloudFork portable, do you use or plan to use libraries like >>> Sport for socket level portability? >>> >>> Best regards >>> Janko >>> >>> > >>> > Jan. >>> > >>> > On Wed, Feb 16, 2011 at 11:22 AM, Geert Claes < >>> geert.wl.claes(a)gmail.com >>> > <mailto:geert.wl.claes@gmail.com>> wrote: >>> > >>> > >>> > >>> > Janko MivÅ¡ek wrote: >>> > > >>> > > It would be nice to rebirth back past Squeak People into >>> something >>> > like >>> > > Smalltalk People on http://people.world.st and use account there >>> for >>> > > single sign-on on all other Smalltalk websites, what do you >>> think? >>> > > >>> > > We'd need that for our GSoC site for instance, to avoid that >>> painful >>> > > registration process needed to differentiate real Smalltalkers >>> from >>> > > spammers... >>> > > >>> > >>> > I'm in favor of not have all these different accounts everywhere >>> > hence why I >>> > was excited to see Seaside supporting OAuth/OpenID so people can >>> sign-up >>> > with their Google/Yahoo/Twitter/Facebook etc accounts they already >>> have. >>> > Maybe the sso can be ported to AIDA as well? >>> > >>> > -- >>> > View this message in context: >>> > http://forum.world.st/New-Squeaksource-tp3308305p3308534.html >>> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> > >>> > >>> >>> -- >>> Janko MivÅ¡ek >>> AIDA/Web >>> Smalltalk Web Application Server >>> http://www.aidaweb.si >>> >>> >> >> > >

Feb. 16, 2011

Re: [Pharo-project] Issue 3712 in pharo: Still CustomMenu references in Pharo 1.2 dev

by pharo＠googlecode.com

Comment #2 on issue 3712 by stephane...(a)gmail.com: Still CustomMenu references in Pharo 1.2 dev http://code.google.com/p/pharo/issues/detail?id=3712 I started to fix them :) More after the train trip Attachments: fixingCustomMenu.1.cs 2.1 KB

Feb. 16, 2011

[Pharo-project] Issue 3717 in pharo: Missing float array methods

by pharo＠googlecode.com

Status: Fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3717 by stephane...(a)gmail.com: Missing float array methods http://code.google.com/p/pharo/issues/detail?id=3717 while fixing the customMenu references I played with the spectrumAnalyzerMorph :) and I found that a lot of method were missing in FloatArray. The changeset makes it work again. Attachments: floatarrayMissingMethods.1.cs 3.0 KB

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Norbert Hartl

On 16.02.2011, at 13:55, Jan van de Sandt wrote: > Hi Norbert, > > No, there is no GemStone port yet and I don't have any experience with GemStone. It should not be too difficult I think. > Isn't there a lot of crypto stuff involved? Norbert > On Wed, Feb 16, 2011 at 1:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > On 16.02.2011, at 13:09, Jan van de Sandt wrote: > >> Hi Janko, >> >> CloudforkSSO has its own small portability layer. The library is already ported to VA Smalltalk. A VisualWorks version will be available within a few days. >> >> CloudforkSSO uses an abstract HttpClient class that has a different concrete subclass for each platform. So no need for socket level portability. For future versions we were thinking about using Grease. The main reason for this is portable UTF-8 support. >> > That would be great! I would like to have these on gemstone. Did you take any effort in supporting this? > > Norbert >> >> 2011/2/16 Janko MivÅ¡ek <janko.mivsek(a)eranova.si> >> Hi Jan, >> >> On 16. 02. 2011 12:18, Jan van de Sandt wrote: >> >> > Porting CloudforkSSO to AIDA should be pretty easy. The OAuth and OpenID >> > base classes use WAUrl and the JSON classes of Seaside. AIDA probably >> > has good alternatives for these. >> >> Good to know that! Another issue could be a portability. Aida is always >> up-to-date on Squeak/Pharo and VisualWorks thanks to a big care that all >> code is portable upfront. >> >> How is CloudFork portable, do you use or plan to use libraries like >> Sport for socket level portability? >> >> Best regards >> Janko >> >> > >> > Jan. >> > >> > On Wed, Feb 16, 2011 at 11:22 AM, Geert Claes <geert.wl.claes(a)gmail.com >> > <mailto:geert.wl.claes@gmail.com>> wrote: >> > >> > >> > >> > Janko MivÅ¡ek wrote: >> > > >> > > It would be nice to rebirth back past Squeak People into something >> > like >> > > Smalltalk People on http://people.world.st and use account there for >> > > single sign-on on all other Smalltalk websites, what do you think? >> > > >> > > We'd need that for our GSoC site for instance, to avoid that painful >> > > registration process needed to differentiate real Smalltalkers from >> > > spammers... >> > > >> > >> > I'm in favor of not have all these different accounts everywhere >> > hence why I >> > was excited to see Seaside supporting OAuth/OpenID so people can sign-up >> > with their Google/Yahoo/Twitter/Facebook etc accounts they already have. >> > Maybe the sso can be ported to AIDA as well? >> > >> > -- >> > View this message in context: >> > http://forum.world.st/New-Squeaksource-tp3308305p3308534.html >> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >> > >> >> -- >> Janko MivÅ¡ek >> AIDA/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> >> > >

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Jan van de Sandt

Hi Norbert, No, there is no GemStone port yet and I don't have any experience with GemStone. It should not be too difficult I think. Jan. On Wed, Feb 16, 2011 at 1:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > On 16.02.2011, at 13:09, Jan van de Sandt wrote: > > Hi Janko, > > CloudforkSSO has its own small portability layer. The library is already > ported to VA Smalltalk. A VisualWorks version will be available within a few > days. > > CloudforkSSO uses an abstract HttpClient class that has a different > concrete subclass for each platform. So no need for socket level > portability. For future versions we were thinking about using Grease. The > main reason for this is portable UTF-8 support. > > That would be great! I would like to have these on gemstone. Did you take > any effort in supporting this? > > Norbert > > > 2011/2/16 Janko MivÅ¡ek <janko.mivsek(a)eranova.si> > >> Hi Jan, >> >> On 16. 02. 2011 12:18, Jan van de Sandt wrote: >> >> > Porting CloudforkSSO to AIDA should be pretty easy. The OAuth and OpenID >> > base classes use WAUrl and the JSON classes of Seaside. AIDA probably >> > has good alternatives for these. >> >> Good to know that! Another issue could be a portability. Aida is always >> up-to-date on Squeak/Pharo and VisualWorks thanks to a big care that all >> code is portable upfront. >> >> How is CloudFork portable, do you use or plan to use libraries like >> Sport for socket level portability? >> >> Best regards >> Janko >> >> > >> > Jan. >> > >> > On Wed, Feb 16, 2011 at 11:22 AM, Geert Claes <geert.wl.claes(a)gmail.com >> > <mailto:geert.wl.claes@gmail.com>> wrote: >> > >> > >> > >> > Janko MivÅ¡ek wrote: >> > > >> > > It would be nice to rebirth back past Squeak People into something >> > like >> > > Smalltalk People on http://people.world.st and use account there >> for >> > > single sign-on on all other Smalltalk websites, what do you think? >> > > >> > > We'd need that for our GSoC site for instance, to avoid that >> painful >> > > registration process needed to differentiate real Smalltalkers >> from >> > > spammers... >> > > >> > >> > I'm in favor of not have all these different accounts everywhere >> > hence why I >> > was excited to see Seaside supporting OAuth/OpenID so people can >> sign-up >> > with their Google/Yahoo/Twitter/Facebook etc accounts they already >> have. >> > Maybe the sso can be ported to AIDA as well? >> > >> > -- >> > View this message in context: >> > http://forum.world.st/New-Squeaksource-tp3308305p3308534.html >> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >> > >> >> -- >> Janko MivÅ¡ek >> AIDA/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> >> > >

Feb. 16, 2011

Re: [Pharo-project] Pharo 1.2 broken on Hudson

by StÃ©phane Ducasse

Thanks I'm fixing some sound menu stuff rigth now.because I want 1.2 out. On Feb 16, 2011, at 1:32 PM, Torsten Bergmann wrote: > Pharo 1.2. is broken on Hudson. > > The ConfigurationOfPharo is not loadable on a core image due > to changes on OmniBrowser. > > Reason: > ======= > ConfigurationOfOmniBrowser-GuillermoPolito.102.mcz in http://www.squeaksource.com/MetacelloRepository > references "OB-Shout-JohanBrichau.13" in spec for: #pharo in its > version 1.2.4 > > But OB-Shout-JohanBrichau.13 is not in http://www.squeaksource.com/PharoOB > Should we use "OB-Shout-GuillermoPolito.13.mcz" instead? > > Guillermo: can you give me access to PharoOB too? > > Thx > T. > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >

Feb. 16, 2011

Re: [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

On Feb 16, 2011, at 12:59 PM, Schwab,Wilhelm K wrote: > Stef, > > The revised language is much improved. tx > I too am curious about what you have in mind on the conditions. We do not know. :) just fuzzy ideas. We will decide with the community. Because the point is that this is not our stuff but a tool that should serve the community. We were thinking - individual memberships - company memberships - institution memberships or/and a moral license so that you can buy pharo and a guy like igor/esteban can get pay to improve the infrastructure. or a bounty (but a moral license is good since it does not bind the task). > Are you looking for support from institutions or individuals? I assume both, but the thresholds would be different for UF than for me by myself. Yes both. This would be excellent. Recently I was asking myself three essential questions beside having a market: ok we have a client so what - how do you control quality/process? - how do you control that your runtime engine is ok/safe/longlasting (else better take java vms there are plenty) - how do you reduce risk like truck factor in your community. Our main point is how can we minimize risk: I'm thinking to participate to a startup around a pharo software and here is a simple simple scenario: imagine that eliot gets hired by XXAS to do javascript/ruby whatever and andreas (which does not reply to my mails because I'm probably too insignificant) goes waco and that ian only shows up every three years instead of every year. do you think that it is wise for companies to invest in an open-source smalltalk? I would not. Now if we have a consortium, a build process, a quality process and one or two guys payed by the community to improve continously the system more than we can. Then this is a message I can understand as an investor. Since we want to make sure that you all can do business we want to reduce risk and provide a good case for process, quality and the rest. Stef > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Wednesday, February 16, 2011 5:00 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Call for Pharo Support **important** >

Feb. 16, 2011

Re: [Pharo-project] Issue 3710 in pharo: Get Rid of PluggableShoutMorph References

by pharo＠googlecode.com

Comment #2 on issue 3710 by laurent....(a)gmail.com: Get Rid of PluggableShoutMorph References http://code.google.com/p/pharo/issues/detail?id=3710 Funny, I removed them yesterday in ProfStef ;)

Feb. 16, 2011

Re: [Pharo-project] Issue 3716 in pharo: Different return value for adoptInstance: depending on VM

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3716 by ryd...(a)gmail.com: Different return value for adoptInstance: depending on VM http://code.google.com/p/pharo/issues/detail?id=3716 SLICE-Issue-3716-adoptInstanceReturn-13-HenrikSperreJohansen.1 for 1.3 added.

Feb. 16, 2011