January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sven Van Caekenberghe

On 30 Jan 2013, at 17:21, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Sven, hi Jan, > > thank you. > I am one step further now but there must be something else missing to load. > I failed with my current image, so I tried the following: > > I took a fresh image - the Pharo 1.4. one click app from the pharo homepage > (http://gforge.inria.fr/frs/download.php/31258/Pharo-1.4-14557-OneClick.zip) > > Then I loaded seaside 3.0 (from the welcome screen - MetacelloConfigurationBrowser open). > > After that, I loaded > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > And then the bleeding Edge version > ConfigurationOfZincHTTPComponents project bleedingEdge load: 'SSO'. > > Then this was possible: > (ZnServer startDefaultOn: 8100) > logToTranscript; > debugMode: true; > delegate: (ZnSSOServerDelegate new > dropboxData: (ZnOAuth1ConsumerData newForDropbox > consumer: 'my appdata'; > consumerSecret: 'my appdata'; > yourself); > yourself). > > No I tried in my browser > localhost:8100/sso-dropbox > > Then I got a walkback in my Image: No secure socket stream class set or available Well, the error says it all: you need TLS/SSL support. As is noted in https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md#installat… You can get Zodiac to work in 1.4 http://zdc.stfx.eu Don't forget that you also need the plugin next to your VM ! In Pharo 2.0 Zodiac is included by default the latest VM's there should have the plugin. But in 2.0 it will be slightly more difficult to load Seaside, but it does work. Sorry, but all this is still a bit in motion, hopefully you will keep trying. > ==>> I do not have the class ZdcSecureSocketStream in my Image > self secureSocketStreamClass is Nil in > > streamClassForScheme: scheme > (#(http ws) includes: scheme) ifTrue: [ > ^ self socketStreamClass ]. > (#(https wss) includes: scheme) ifTrue: [ > ^ self secureSocketStreamClass ifNil: [ > self error: 'No secure socket stream class set or available' ] ]. > (ZnUnknownScheme scheme: scheme) signal > > Can you tell me what is missing to load? > > Greetings > Sabine > > > 30 January 2013 5:14:22.402 pm > > ZnNetworkingUtils(Object)>>error: > Receiver: a ZnNetworkingUtils > Arguments and temporary variables: > aString: 'No secure socket stream class set or available' > Receiver's instance variables: > socketStreamClass: SocketStream > secureSocketStreamClass: nil > > ZnNetworkingUtils>>streamClassForScheme: > Receiver: a ZnNetworkingUtils > Arguments and temporary variables: > scheme: #https > Receiver's instance variables: > socketStreamClass: SocketStream > secureSocketStreamClass: nil > > ZnNetworkingUtils>>socketStreamToUrlDirectly: > Receiver: a ZnNetworkingUtils > Arguments and temporary variables: > url: https://api.dropbox.com/1/oauth/request_token > stream: nil > address: #[199 47 218 158] > Receiver's instance variables: > socketStreamClass: SocketStream > secureSocketStreamClass: nil > > ZnNetworkingUtils>>socketStreamToUrl: > Receiver: a ZnNetworkingUtils > Arguments and temporary variables: > url: https://api.dropbox.com/1/oauth/request_token > Receiver's instance variables: > socketStreamClass: SocketStream > secureSocketStreamClass: nil > > > > > On Wed, Jan 30, 2013 at 4:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Sabine, > > On 30 Jan 2013, at 16:24, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > > > Hi Sven, > > > > after loading: > > > > Gofer it > > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > > package: 'ConfigurationOfZincHTTPComponents'; > > load. > > > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > > The ZnOAuth1ConsumerData does not have a method called >>newForDropbox (but >>newForGoogle and >>newForTwitter). > > Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but facebook, twittter and google) > > > > Did I miss something? > > Yes and no. The latest stable version of the configuration does not yet include the Dropbox code. > The following will load what is called bleedingEdge, the very latest version of everything, regardless of its release status. > > ConfigurationOfZincHTTPComponents project bleedingEdge load: 'SSO'. > > Sorry about that. > > Sven > > > Greetings > > Sabine > > > > > > On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > If anyone is interested, I can write another email explaining how you can run this demo for yourself on your own account. > > > > How to run the Dropbox code yourself: > > > > 1. Get yourself a free Dropbox account at http://www.dropbox.com > > > > 2. Install some client software on one or more of your computers (Mac, Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, Kindle Fire) and move some files around to get a feel for the service. > > > > 3. When you give other applications access to (part of) your Dropbox files, you can check that at https://www.dropbox.com/account#applications > > > > 4. Define your own app that will try to access Dropbox files. Go to https://www.dropbox.com/developers (Developer home) and start defining a new app by clicking the 'Create an app' button at https://www.dropbox.com/developers/apps - start with the access type 'App folder'. > > > > 5. The two important elements you need are the 'App key' and 'App secret', make sure to copy them correctly. > > > > 6. Get the very latest code in your image (we develop in Pharo 2.0, but 1.4 or even 1.3 should work - SSL has to be fully operational). > > > > Gofer it > > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > > package: 'ConfigurationOfZincHTTPComponents'; > > load. > > > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > > 7. Start a Zn server with an appropriate delegate, configured for your app > > > > (ZnServer startDefaultOn: 8100) > > logToTranscript; > > debugMode: true; > > delegate: (ZnSSOServerDelegate new > > dropboxData: (ZnOAuth1ConsumerData newForDropbox > > consumer: 'vqz-app-key-zoca'; > > consumerSecret: '13u-app-secret-8l006'; > > yourself); > > yourself). > > > > (The above is a demo setup limited to Dropbox, the other demos are not configured and won't work). > > > > 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in - you will be transferred to Dropbox to log in (if you aren't already) and asked to authorise your demo app, after which Dropbox will redirect you back to your app. > > > > 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) will access your account info and list the app root folder, which will then be shown. > > > > 10. For the rest of the API, (currently not yet implemented), see https://www.dropbox.com/developers/reference/api - you don't have to worry about the whole authentication thanks to Zinc-SSO. > > > > We would love for others to try this (as well as the other Zinc-SSO options, Google, Facebook, Twitter) out, in their own projects, and to provide actual feedback and generally help improve the code and documentation. > > > > As always, May the Source be with you! > > > > Sven > > > > PS: The demo app is not (yet) a production app: only you and up to 5 explicitly listed users can use it. You have to apply for production status later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual project, it would be best to extract the necessary parts out of it, reusing the underlying Zinc-SSO-OAuth1-Core framework. > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > > > > > > >

Jan. 30, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sabine KnÃ¶fel

Hi Sven, hi Jan, thank you. I am one step further now but there must be something else missing to load. I failed with my current image, so I tried the following: I took a fresh image - the Pharo 1.4. one click app from the pharo homepage (http://gforge.inria.fr/frs/download.php/31258/Pharo-1.4-14557-OneClick.zip) Then I loaded seaside 3.0 (from the welcome screen - MetacelloConfigurationBrowser open). After that, I loaded Gofer it url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. And then the bleeding Edge version ConfigurationOfZincHTTPComponents project bleedingEdge load: 'SSO'. Then this was possible: (ZnServer startDefaultOn: 8100) logToTranscript; debugMode: true; delegate: (ZnSSOServerDelegate new dropboxData: (ZnOAuth1ConsumerData newForDropbox consumer: 'my appdata'; consumerSecret: 'my appdata'; yourself); yourself). No I tried in my browser localhost:8100/sso-dropbox Then I got a walkback in my Image: No secure socket stream class set or available ==>> I do not have the class ZdcSecureSocketStream in my Image self secureSocketStreamClass is Nil in streamClassForScheme: scheme (#(http ws) includes: scheme) ifTrue: [ ^ self socketStreamClass ]. (#(https wss) includes: scheme) ifTrue: [ ^ self secureSocketStreamClass ifNil: [ self error: 'No secure socket stream class set or available' ] ]. (ZnUnknownScheme scheme: scheme) signal Can you tell me what is missing to load? Greetings Sabine 30 January 2013 5:14:22.402 pm ZnNetworkingUtils(Object)>>error: Receiver: a ZnNetworkingUtils Arguments and temporary variables: aString: 'No secure socket stream class set or available' Receiver's instance variables: socketStreamClass: SocketStream secureSocketStreamClass: nil ZnNetworkingUtils>>streamClassForScheme: Receiver: a ZnNetworkingUtils Arguments and temporary variables: scheme: #https Receiver's instance variables: socketStreamClass: SocketStream secureSocketStreamClass: nil ZnNetworkingUtils>>socketStreamToUrlDirectly: Receiver: a ZnNetworkingUtils Arguments and temporary variables: url: https://api.dropbox.com/1/oauth/request_token stream: nil address: #[199 47 218 158] Receiver's instance variables: socketStreamClass: SocketStream secureSocketStreamClass: nil ZnNetworkingUtils>>socketStreamToUrl: Receiver: a ZnNetworkingUtils Arguments and temporary variables: url: https://api.dropbox.com/1/oauth/request_token Receiver's instance variables: socketStreamClass: SocketStream secureSocketStreamClass: nil On Wed, Jan 30, 2013 at 4:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Sabine, > > On 30 Jan 2013, at 16:24, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > > > Hi Sven, > > > > after loading: > > > > Gofer it > > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > > package: 'ConfigurationOfZincHTTPComponents'; > > load. > > > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > > The ZnOAuth1ConsumerData does not have a method called >>newForDropbox > (but >>newForGoogle and >>newForTwitter). > > Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but > facebook, twittter and google) > > > > Did I miss something? > > Yes and no. The latest stable version of the configuration does not yet > include the Dropbox code. > The following will load what is called bleedingEdge, the very latest > version of everything, regardless of its release status. > > ConfigurationOfZincHTTPComponents project bleedingEdge load: 'SSO'. > > Sorry about that. > > Sven > > > Greetings > > Sabine > > > > > > On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > > > On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > If anyone is interested, I can write another email explaining how you > can run this demo for yourself on your own account. > > > > How to run the Dropbox code yourself: > > > > 1. Get yourself a free Dropbox account at http://www.dropbox.com > > > > 2. Install some client software on one or more of your computers (Mac, > Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, > Kindle Fire) and move some files around to get a feel for the service. > > > > 3. When you give other applications access to (part of) your Dropbox > files, you can check that at https://www.dropbox.com/account#applications > > > > 4. Define your own app that will try to access Dropbox files. Go to > https://www.dropbox.com/developers (Developer home) and start defining a > new app by clicking the 'Create an app' button at > https://www.dropbox.com/developers/apps - start with the access type 'App > folder'. > > > > 5. The two important elements you need are the 'App key' and 'App > secret', make sure to copy them correctly. > > > > 6. Get the very latest code in your image (we develop in Pharo 2.0, but > 1.4 or even 1.3 should work - SSL has to be fully operational). > > > > Gofer it > > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > > package: 'ConfigurationOfZincHTTPComponents'; > > load. > > > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > > 7. Start a Zn server with an appropriate delegate, configured for your > app > > > > (ZnServer startDefaultOn: 8100) > > logToTranscript; > > debugMode: true; > > delegate: (ZnSSOServerDelegate new > > dropboxData: (ZnOAuth1ConsumerData newForDropbox > > > consumer: 'vqz-app-key-zoca'; > > > consumerSecret: '13u-app-secret-8l006'; > > > yourself); > > yourself). > > > > (The above is a demo setup limited to Dropbox, the other demos are not > configured and won't work). > > > > 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in > - you will be transferred to Dropbox to log in (if you aren't already) and > asked to authorise your demo app, after which Dropbox will redirect you > back to your app. > > > > 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) > will access your account info and list the app root folder, which will then > be shown. > > > > 10. For the rest of the API, (currently not yet implemented), see > https://www.dropbox.com/developers/reference/api - you don't have to > worry about the whole authentication thanks to Zinc-SSO. > > > > We would love for others to try this (as well as the other Zinc-SSO > options, Google, Facebook, Twitter) out, in their own projects, and to > provide actual feedback and generally help improve the code and > documentation. > > > > As always, May the Source be with you! > > > > Sven > > > > PS: The demo app is not (yet) a production app: only you and up to 5 > explicitly listed users can use it. You have to apply for production status > later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual > project, it would be best to extract the necessary parts out of it, reusing > the underlying Zinc-SSO-OAuth1-Core framework. > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > > > > > > >

Jan. 30, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sven Van Caekenberghe

Sabine, On 30 Jan 2013, at 16:24, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Sven, > > after loading: > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > The ZnOAuth1ConsumerData does not have a method called >>newForDropbox (but >>newForGoogle and >>newForTwitter). > Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but facebook, twittter and google) > > Did I miss something? Yes and no. The latest stable version of the configuration does not yet include the Dropbox code. The following will load what is called bleedingEdge, the very latest version of everything, regardless of its release status. ConfigurationOfZincHTTPComponents project bleedingEdge load: 'SSO'. Sorry about that. Sven > Greetings > Sabine > > > On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > If anyone is interested, I can write another email explaining how you can run this demo for yourself on your own account. > > How to run the Dropbox code yourself: > > 1. Get yourself a free Dropbox account at http://www.dropbox.com > > 2. Install some client software on one or more of your computers (Mac, Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, Kindle Fire) and move some files around to get a feel for the service. > > 3. When you give other applications access to (part of) your Dropbox files, you can check that at https://www.dropbox.com/account#applications > > 4. Define your own app that will try to access Dropbox files. Go to https://www.dropbox.com/developers (Developer home) and start defining a new app by clicking the 'Create an app' button at https://www.dropbox.com/developers/apps - start with the access type 'App folder'. > > 5. The two important elements you need are the 'App key' and 'App secret', make sure to copy them correctly. > > 6. Get the very latest code in your image (we develop in Pharo 2.0, but 1.4 or even 1.3 should work - SSL has to be fully operational). > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > 7. Start a Zn server with an appropriate delegate, configured for your app > > (ZnServer startDefaultOn: 8100) > logToTranscript; > debugMode: true; > delegate: (ZnSSOServerDelegate new > dropboxData: (ZnOAuth1ConsumerData newForDropbox > consumer: 'vqz-app-key-zoca'; > consumerSecret: '13u-app-secret-8l006'; > yourself); > yourself). > > (The above is a demo setup limited to Dropbox, the other demos are not configured and won't work). > > 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in - you will be transferred to Dropbox to log in (if you aren't already) and asked to authorise your demo app, after which Dropbox will redirect you back to your app. > > 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) will access your account info and list the app root folder, which will then be shown. > > 10. For the rest of the API, (currently not yet implemented), see https://www.dropbox.com/developers/reference/api - you don't have to worry about the whole authentication thanks to Zinc-SSO. > > We would love for others to try this (as well as the other Zinc-SSO options, Google, Facebook, Twitter) out, in their own projects, and to provide actual feedback and generally help improve the code and documentation. > > As always, May the Source be with you! > > Sven > > PS: The demo app is not (yet) a production app: only you and up to 5 explicitly listed users can use it. You have to apply for production status later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual project, it would be best to extract the necessary parts out of it, reusing the underlying Zinc-SSO-OAuth1-Core framework. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

Jan. 30, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Jan van de Sandt

Hello Sabine, The package versions that support Dropbox are not yet part of ConfigurationOfZincHTTPComponent. If you load the latest versions of the Zinc-SSO packages using the Monticello browser it should work. Jan. On Wed, Jan 30, 2013 at 4:24 PM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com>wrote: > Hi Sven, > > after loading: > > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > The ZnOAuth1ConsumerData does not have a method called >>newForDropbox > (but >>newForGoogle and >>newForTwitter). > Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but > facebook, twittter and google) > > Did I miss something? > > Greetings > Sabine > > > On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> >> On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> > If anyone is interested, I can write another email explaining how you >> can run this demo for yourself on your own account. >> >> How to run the Dropbox code yourself: >> >> 1. Get yourself a free Dropbox account at http://www.dropbox.com >> >> 2. Install some client software on one or more of your computers (Mac, >> Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, >> Kindle Fire) and move some files around to get a feel for the service. >> >> 3. When you give other applications access to (part of) your Dropbox >> files, you can check that at https://www.dropbox.com/account#applications >> >> 4. Define your own app that will try to access Dropbox files. Go to >> https://www.dropbox.com/developers (Developer home) and start defining a >> new app by clicking the 'Create an app' button at >> https://www.dropbox.com/developers/apps - start with the access type >> 'App folder'. >> >> 5. The two important elements you need are the 'App key' and 'App >> secret', make sure to copy them correctly. >> >> 6. Get the very latest code in your image (we develop in Pharo 2.0, but >> 1.4 or even 1.3 should work - SSL has to be fully operational). >> >> Gofer it >> url: 'http://mc.stfx.eu/ZincHTTPComponents'; >> package: 'ConfigurationOfZincHTTPComponents'; >> load. >> >> ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. >> >> 7. Start a Zn server with an appropriate delegate, configured for your app >> >> (ZnServer startDefaultOn: 8100) >> logToTranscript; >> debugMode: true; >> delegate: (ZnSSOServerDelegate new >> dropboxData: (ZnOAuth1ConsumerData newForDropbox >> consumer: >> 'vqz-app-key-zoca'; >> >> consumerSecret: '13u-app-secret-8l006'; >> yourself); >> yourself). >> >> (The above is a demo setup limited to Dropbox, the other demos are not >> configured and won't work). >> >> 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in >> - you will be transferred to Dropbox to log in (if you aren't already) and >> asked to authorise your demo app, after which Dropbox will redirect you >> back to your app. >> >> 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) >> will access your account info and list the app root folder, which will then >> be shown. >> >> 10. For the rest of the API, (currently not yet implemented), see >> https://www.dropbox.com/developers/reference/api - you don't have to >> worry about the whole authentication thanks to Zinc-SSO. >> >> We would love for others to try this (as well as the other Zinc-SSO >> options, Google, Facebook, Twitter) out, in their own projects, and to >> provide actual feedback and generally help improve the code and >> documentation. >> >> As always, May the Source be with you! >> >> Sven >> >> PS: The demo app is not (yet) a production app: only you and up to 5 >> explicitly listed users can use it. You have to apply for production status >> later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual >> project, it would be best to extract the necessary parts out of it, reusing >> the underlying Zinc-SSO-OAuth1-Core framework. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >

Jan. 30, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sabine KnÃ¶fel

Hi Sven, after loading: Gofer it url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. The ZnOAuth1ConsumerData does not have a method called >>newForDropbox (but >>newForGoogle and >>newForTwitter). Also, ZnSSOServerDelegate does not have a method >>dropboxData: (but facebook, twittter and google) Did I miss something? Greetings Sabine On Sun, Jan 27, 2013 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 27 Jan 2013, at 13:32, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > If anyone is interested, I can write another email explaining how you > can run this demo for yourself on your own account. > > How to run the Dropbox code yourself: > > 1. Get yourself a free Dropbox account at http://www.dropbox.com > > 2. Install some client software on one or more of your computers (Mac, > Windows, Linux) or devices (iOS [iPhone, iPad, iPod], Android, BlackBerry, > Kindle Fire) and move some files around to get a feel for the service. > > 3. When you give other applications access to (part of) your Dropbox > files, you can check that at https://www.dropbox.com/account#applications > > 4. Define your own app that will try to access Dropbox files. Go to > https://www.dropbox.com/developers (Developer home) and start defining a > new app by clicking the 'Create an app' button at > https://www.dropbox.com/developers/apps - start with the access type 'App > folder'. > > 5. The two important elements you need are the 'App key' and 'App secret', > make sure to copy them correctly. > > 6. Get the very latest code in your image (we develop in Pharo 2.0, but > 1.4 or even 1.3 should work - SSL has to be fully operational). > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > 7. Start a Zn server with an appropriate delegate, configured for your app > > (ZnServer startDefaultOn: 8100) > logToTranscript; > debugMode: true; > delegate: (ZnSSOServerDelegate new > dropboxData: (ZnOAuth1ConsumerData newForDropbox > consumer: > 'vqz-app-key-zoca'; > > consumerSecret: '13u-app-secret-8l006'; > yourself); > yourself). > > (The above is a demo setup limited to Dropbox, the other demos are not > configured and won't work). > > 8. Go to http:://localhost:8100/sso-dropbox and click the link to log in - > you will be transferred to Dropbox to log in (if you aren't already) and > asked to authorise your demo app, after which Dropbox will redirect you > back to your app. > > 9. Once back in your app, sso-dropbox-callback (#ssoDropboxCallback:) will > access your account info and list the app root folder, which will then be > shown. > > 10. For the rest of the API, (currently not yet implemented), see > https://www.dropbox.com/developers/reference/api - you don't have to > worry about the whole authentication thanks to Zinc-SSO. > > We would love for others to try this (as well as the other Zinc-SSO > options, Google, Facebook, Twitter) out, in their own projects, and to > provide actual feedback and generally help improve the code and > documentation. > > As always, May the Source be with you! > > Sven > > PS: The demo app is not (yet) a production app: only you and up to 5 > explicitly listed users can use it. You have to apply for production status > later on. Also, the whole ZnSSOServerDelegate code is a demo, for an actual > project, it would be best to extract the necessary parts out of it, reusing > the underlying Zinc-SSO-OAuth1-Core framework. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > >

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Esteban A. Maringolo

2013/1/30 Norbert Hartl <norbert(a)hartl.name>: > (SNIP) > I would make the none categorized term weaker by naming it "uncategorizied" so at least I have the change to deliberately not categorizing my methods without being annoyed by someones opinion about what is essential. I agree with this, I'd fine if the method browser doesn't have any category pane at all. Most of the times the selectors are self describing, and a short list of them. I only used the categories to search methods in classes like String, where you try to find some specific behavior (most of the time under the "printing" or "converting" category). Regards,

Jan. 30, 2013

Re: [Pharo-project] [squeak-dev] Re: I hate 'as yet unclassified'

by David Corking

Thanks for taking a look at Squeak as well, Stephan. I think that Hernan Wilkinson suggested a smalllint script might be run as part of a CI job to report on uncategorized methods in commits. Could such a thing go on the requested features list for the Squeak and Pharo Jenkins servers? No big deal, but I think categories help me to understand large classes, at least when categories are somewhat standardized across classes. (Stephan posted his code to pharo-dev : http://forum.world.st/I-hate-as-yet-unclassified-tp4666245p4666620.html ) Have fun! David

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Ben Coman

Hernan Wilkinson wrote: > I think that classification is a matter of time and maturity of what you > are doing. > When I'm programming, using TDD or in the debugger, I don't care about > categorization, I don't want to be stopped or slowed down by that. > But before I commit the code, I run SmallLint and solve all the > uncategorized methods. That is the time when I have the whole picture and > can do a better categorization. > Interesting. My own standard practice with Monticello is to always first click the <Changes> button to help me summarize what this commit is about. Sometimes I see a leftover 'self halt' or Transcript and jump back to clean that up before saving. If Monticello had a <SmallLint> button, then I think I would make great use of it to clean up just prior committing a package revision. cheers -ben

Jan. 30, 2013

[Pharo-project] I hate 'as yet unclassified'

by Torsten Bergmann

>in the 4.3 one-click too >... >#unclassified methods by author >... >stephaneducasse 145 Interesting ;) As I wrote in http://markmail.org/message/oo4gsiyasoinkmol: <ownquote> "Removing packages or classes that are not documented is too hard ... but we should use Lint rules to check the "completeness/basic quality" of package. Similar to checkstyle for Java in Eclipse - if there are problems in a package then you have a different icon for the package and you work until it's clean because it hurts your eyes (see [10] for a screenshot)" http://www.ibm.com/developerworks/java/library/j-ap01117/checkstyle-eclipse… </ownquote> So we should have a "BAD/UGLY" icon for packages/classes that do not satisfy basic rules like "no unclassified methods", etc. Bye T.

Jan. 30, 2013

Re: [Pharo-project] I hate 'as yet unclassified'

by Norbert Hartl

Am 29.01.2013 um 16:57 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > I spend my time recategorizing methods. > > I would like the change the intention of 'as yet unclassified' because this is a PLAGUE. > It is like throwing papers on the floor. > So we should have a different name to indicate that it should be fixed. > > > Any ideas? > > 'you are a dirty programmer - change me' > To be honest I have problems understanding why method categorization is so important. Often I don't care a single bit about categories because I don't understand them. I often categorize just to make lint happy :) What is the use? Declaring usage patterns? Declaring visibility? Use as method extensions marker? anything you like just classify? I can understand that it can help making the access of certain methods of a class easier. But that is particular true for classes with a lot of methods. Most of the classes are rather small. In most of my own developments I would consider most huge classes a design problem in my code. So I would try to fix that. And finally it is not easy to learn about them because the browser is not helping. If you browse through the methods of a class the category pane doesn't get updated. So even if I want to learn by getting used to them it is hard. I would make the none categorized term weaker by naming it "uncategorizied" so at least I have the change to deliberately not categorizing my methods without being annoyed by someones opinion about what is essential. my 2 cents, Norbert

Jan. 30, 2013