opensocial-ruby-client - Project Hosting on Google Code

Earlier this year Nov 10, 2009 GettingStarted (Introduction to the Ruby Client Library) Wiki page commented on by toyosystem - >jcolag see http://d.hatena.ne.jp/willnet/20090316/1237212874 >jcolag see http://d.hatena.ne.jp/willnet/20090316/1237212874 Nov 05, 2009 r38 (Added new get_supported_fields method.) committed by zlu...@myspace.com - Added new get_supported_fields method. Added new get_supported_fields method. Nov 04, 2009 r37 (New objects for 0.9 spec.) committed by zlu...@myspace.com - New objects for 0.9 spec. New objects for 0.9 spec. Nov 04, 2009 r36 (Support for OpenSocial 0.9 spec + some MySpace specific clas...) committed by zlu...@myspace.com - Support for OpenSocial 0.9 spec + some MySpace specific classes. Support for OpenSocial 0.9 spec + some MySpace specific classes. Sep 21, 2009 r35 (Patches to ensure compatitbility with MySpace OpenSocial v0....) committed by jn...@myspace.com - Patches to ensure compatitbility with MySpace OpenSocial v0.9 REST API calls. Patches to ensure compatitbility with MySpace OpenSocial v0.9 REST API calls. Aug 13, 2009 GettingStarted (Introduction to the Ruby Client Library) Wiki page commented on by jcolag - I must be missing something, since everybody else is getting further than I am. After installing the gem (0.0.4) on an Ubuntu Linux server, though that shouldn't make a difference, with Ruby 1.8.6 and Rails 2.3.3, the MySpace example gives me this: ./opensocial.rb:10: uninitialized constant OpenSocial (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from opensocial.rb:2 Yes, I added "require 'rubygems'," figuring that might resolve it, but no go. It sounds like it didn't install correctly, but I found everything to make Brendan's suggested patch. Might anybody have any thoughts on this? I must be missing something, since everybody else is getting further than I am. After installing the gem (0.0.4) on an Ubuntu Linux server, though that shouldn't make a difference, with Ruby 1.8.6 and Rails 2.3.3, the MySpace example gives me this: ./opensocial.rb:10: uninitialized constant OpenSocial (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from opensocial.rb:2 Yes, I added "require 'rubygems'," figuring that might resolve it, but no go. It sounds like it didn't install correctly, but I found everything to make Brendan's suggested patch. Might anybody have any thoughts on this? Jul 09, 2009 GettingStarted (Introduction to the Ruby Client Library) Wiki page commented on by brendan.ribera - To work in both scenarios: proxies(defined?(ActionController::AbstractRequest) ? ActionController::AbstractRequest : ActionController::Request) To work in both scenarios: proxies(defined?(ActionController::AbstractRequest) ? ActionController::AbstractRequest : ActionController::Request) Jul 03, 2009 GettingStarted (Introduction to the Ruby Client Library) Wiki page commented on by LeonidShevtsov - so it seems latest plugin - 0.0.4 does NOT work with rails 2.3 can anyone confirm this? just find ActionController::AbstractRequest in the source code and replace it with ActionController::Request now opensocial-0.0.4 works with rails 2.3. so it seems latest plugin - 0.0.4 does NOT work with rails 2.3 can anyone confirm this? just find ActionController::AbstractRequest in the source code and replace it with ActionController::Request now opensocial-0.0.4 works with rails 2.3. Jun 05, 2009 issue 7 (Add Google FriendConnect container support to the gem) reported by sanoyce - What is the expected output? What do you see instead? I would like to be able to pass in :container => FCONN (or similar) to Connection.new and be able to set up a connection to Friend Connect that recognizes its fcauth= token format instead of the st= format used by other containers. What version of the product are you using? On what operating system? I'm on opensocial-0.0.4 in Linux with ruby 1.8.6 Please provide any additional information below. Please forgive me if this is totally off base. I'm new (as in days) to the OpenSocial. I have hacked up the gem in my local environment to work in the manner described and would be willing to submit a patch to that effect. What is the expected output? What do you see instead? I would like to be able to pass in :container => FCONN (or similar) to Connection.new and be able to set up a connection to Friend Connect that recognizes its fcauth= token format instead of the st= format used by other containers. What version of the product are you using? On what operating system? I'm on opensocial-0.0.4 in Linux with ruby 1.8.6 Please provide any additional information below. Please forgive me if this is totally off base. I'm new (as in days) to the OpenSocial. I have hacked up the gem in my local environment to work in the manner described and would be willing to submit a patch to that effect. Apr 02, 2009 opensocial-0.0.4.gem (Updates client with OAuth signing changes) file uploaded by api....@google.com - Labels: Featured Labels: Featured Apr 02, 2009 r34 (Removes oauth_token parameter from requests when it is not b...) committed by api....@google.com - Removes oauth_token parameter from requests when it is not being used (by updating the dependency on the oauth gem to 0.3.2). Updates docs. Removes oauth_token parameter from requests when it is not being used (by updating the dependency on the oauth gem to 0.3.2). Updates docs. Mar 23, 2009 opensocial-0.0.3.gem (Second release gem for opensocial-ruby-client) file uploaded by api....@google.com - Labels: Featured Labels: Featured Mar 23, 2009 r33 (Updates orkut/iGoogle configurations for upcoming change. Up...) committed by api....@google.com - Updates orkut/iGoogle configurations for upcoming change. Updates gem spec for new release. Updates orkut/iGoogle configurations for upcoming change. Updates gem spec for new release. Mar 20, 2009 r32 (Updates docs with latest changes.) committed by api....@google.com - Updates docs with latest changes. Updates docs with latest changes. Mar 20, 2009 r31 (Adds support for custom content-type, optional body signing ...) committed by api....@google.com - Adds support for custom content-type, optional body signing on requests, optional request body hash on requests, new default endpoints for iGoogle, and new default signing options for iGoogle and orkut (which take effect Monday). Adds support for custom content-type, optional body signing on requests, optional request body hash on requests, new default endpoints for iGoogle, and new default signing options for iGoogle and orkut (which take effect Monday). Older Dec 12, 2008 r30 (Updates the Connection::IGOOGLE hash to use the working sand...) committed by api....@google.com - Updates the Connection::IGOOGLE hash to use the working sandbox endpoint. Updates docs for this change. Updates the Connection::IGOOGLE hash to use the working sandbox endpoint. Updates docs for this change. Dec 11, 2008 opensocial-0.0.2.gem (First release gem version of opensocial-ruby-client) file uploaded by api....@google.com - Labels: Featured Labels: Featured Dec 11, 2008 r29 (Updates documentation for the most recent changes. Changes r...) committed by api....@google.com - Updates documentation for the most recent changes. Changes rakefile gem version to 0.0.2 for the newest release. Updates documentation for the most recent changes. Changes rakefile gem version to 0.0.2 for the newest release. Dec 11, 2008 gifts_sample_1.0.zip (Gifts sample application) file uploaded by api....@google.com - Labels: Featured Type-Source Labels: Featured Type-Source Dec 11, 2008 r28 (Updates gifts sample with boilerplate XML and instructions.) committed by api....@google.com - Updates gifts sample with boilerplate XML and instructions. Updates gifts sample with boilerplate XML and instructions. Dec 10, 2008 r27 (Adds a sample directory and a sample 'gifts' application usi...) committed by api....@google.com - Adds a sample directory and a sample 'gifts' application using 2-legged-OAuth Adds a sample directory and a sample 'gifts' application using 2-legged-OAuth Dec 10, 2008 issue 6 (Support standard query parameters in REST requests) reported by api....@google.com - REST requests should support the standard query parameters as outlined section 6.5 of the RESTful specification: http://www.opensocial.org/Technical-Resources/opensocial-spec-v08/restful-api-specification. REST requests should support the standard query parameters as outlined section 6.5 of the RESTful specification: http://www.opensocial.org/Technical-Resources/opensocial-spec-v08/restful-api-specification. Dec 10, 2008 issue 5 (Support PUT, POST, and DELETE actions for Group class) reported by api....@google.com - Add PUT, POST, and DELETE actions using both REST and RPC for the Group class, to fully support CRUD operations. Add PUT, POST, and DELETE actions using both REST and RPC for the Group class, to fully support CRUD operations. Dec 10, 2008 issue 4 (Support PUT, POST, and DELETE actions for AppData class) reported by api....@google.com - Add PUT, POST, and DELETE actions using both REST and RPC for the AppData class, to fully support CRUD operations. Add PUT, POST, and DELETE actions using both REST and RPC for the AppData class, to fully support CRUD operations. Dec 10, 2008 issue 3 (Support PUT, POST, and DELETE actions for Activity class) reported by api....@google.com - Add PUT, POST, and DELETE actions using both REST and RPC for the Activity class, to fully support CRUD operations. Add PUT, POST, and DELETE actions using both REST and RPC for the Activity class, to fully support CRUD operations. Dec 10, 2008 issue 2 (Support PUT, POST, and DELETE actions for Person class) changed by api....@google.com - Status: New Owner: --- Status: New Owner: --- Dec 10, 2008 issue 2 (Support PUT, POST, and DELETE actions for Person class) reported by api....@google.com - Add PUT, POST, and DELETE actions using both REST and RPC for the Person class, to fully support CRUD operations. Add PUT, POST, and DELETE actions using both REST and RPC for the Person class, to fully support CRUD operations. Dec 10, 2008 issue 1 (request should include ports) Status changed by api....@google.com - I've submitted your patch, and also adjusted the code in the Auth module to allow the same behavior. Thanks! Status: Fixed I've submitted your patch, and also adjusted the code in the Auth module to allow the same behavior. Thanks! Status: Fixed Dec 10, 2008 r26 (Modifies request and 3-legged-oauth signing to be able to ta...) committed by api....@google.com - Modifies request and 3-legged-oauth signing to be able to target an arbitrary port number. Modifies request and 3-legged-oauth signing to be able to target an arbitrary port number. Dec 10, 2008 r25 (Updates documentation on auth helpers.) committed by api....@google.com - Updates documentation on auth helpers. Updates documentation on auth helpers. Dec 09, 2008 r24 (Replaces validate.rb with the more-aptly-named auth/base.rb ...) committed by api....@google.com - Replaces validate.rb with the more-aptly-named auth/base.rb file. Adds helpers for requesting 3-legged OAuth request and access tokens. Replaces validate.rb with the more-aptly-named auth/base.rb file. Adds helpers for requesting 3-legged OAuth request and access tokens. Dec 09, 2008 r23 (Moves OAuth signing out of the request class and into the co...) committed by api....@google.com - Moves OAuth signing out of the request class and into the connection class (so it can be reused in other contexts). Moves OAuth signing out of the request class and into the connection class (so it can be reused in other contexts). Dec 09, 2008 issue 1 (request should include ports) reported by bobev...@google.com - The request.rb class created the Net::HTTP without looking at the uri.port. This means it is impossible to test against local servers running on different ports than 80. I have attached a patch. The request.rb class created the Net::HTTP without looking at the uri.port. This means it is impossible to test against local servers running on different ports than 80. I have attached a patch. Dec 09, 2008 r22 (Removes requirement that a Connection have an xoauth_request...) committed by api....@google.com - Removes requirement that a Connection have an xoauth_requestor_id to use HMAC. Removes requirement that a Connection have an xoauth_requestor_id to use HMAC. Dec 09, 2008 r21 (Updates mime-type on newer doc files.) committed by api....@google.com - Updates mime-type on newer doc files. Updates mime-type on newer doc files. Dec 08, 2008 GettingStarted (Introduction to the Ruby Client Library) Wiki page edited by api....@google.com Dec 08, 2008 r19 (Updates generated RDoc files to reflect the new documentatio...) committed by api....@google.com - Updates generated RDoc files to reflect the new documentation. Updates generated RDoc files to reflect the new documentation. Dec 08, 2008 r18 (Updates and adds documentation to classes and individual met...) committed by api....@google.com - Updates and adds documentation to classes and individual methods. Updates and adds documentation to classes and individual methods. Dec 08, 2008 r17 (Updates and adds documentation to classes and individual met...) committed by api....@google.com - Updates and adds documentation to classes and individual methods. Updates and adds documentation to classes and individual methods. Dec 05, 2008 r16 (Adds test coverage for the connection class.) committed by api....@google.com - Adds test coverage for the connection class. Adds test coverage for the connection class. Dec 04, 2008 r15 (Adds test coverage for generic requests and RPC requests as ...) committed by api....@google.com - Adds test coverage for generic requests and RPC requests as well as online tests. Adds test coverage for generic requests and RPC requests as well as online tests. Dec 04, 2008 r14 (Updates existing person tests to account for the display_nam...) committed by api....@google.com - Updates existing person tests to account for the display_name, long_name change. Updates existing person tests to account for the display_name, long_name change. Dec 04, 2008 r13 (Updates person class method display_name to long_name to avo...) committed by api....@google.com - Updates person class method display_name to long_name to avoid possible container conflict. Also, adds utilization of nickname field, when a complete name is not present. Adds a short_name method to utilize the first name or nickname where available. Updates person, appdata, activity, group, to return an empty object instead of throwing an error when no JSON is supplied (usually in the case of an RPC request where one or more items are unavailable.) Updates person class method display_name to long_name to avoid possible container conflict. Also, adds utilization of nickname field, when a complete name is not present. Adds a short_name method to utilize the first name or nickname where available. Updates person, appdata, activity, group, to return an empty object instead of throwing an error when no JSON is supplied (usually in the case of an RPC request where one or more items are unavailable.) Dec 04, 2008 r12 (Updates validate helper to accept a key and secret, or use C...) committed by api....@google.com - Updates validate helper to accept a key and secret, or use CONSTANT defaults if provided. Updates validate helper to accept a key and secret, or use CONSTANT defaults if provided. Nov 26, 2008 GettingStarted Wiki page edited by api....@google.com Nov 26, 2008 opensocial-0.0.1.gem (Pre-release gem version of opensocial-ruby-client) file uploaded by api....@google.com Nov 26, 2008 r10 (Updated docs to reflect changes to project layout.) committed by api....@google.com - Updated docs to reflect changes to project layout. Updated docs to reflect changes to project layout. Nov 26, 2008 r9 (Updated rakefile to generate a proper gem (which involved mo...) committed by api....@google.com - Updated rakefile to generate a proper gem (which involved moving opensocial under a lib directory to follow convention). Updated unit test code to run properly with 'gem check opensocial -t'. Updated rakefile to generate a proper gem (which involved moving opensocial under a lib directory to follow convention). Updated unit test code to run properly with 'gem check opensocial -t'. Nov 25, 2008 r8 (Updates mimetype on docs CSS to allow direct linking from SV...) committed by api....@google.com - Updates mimetype on docs CSS to allow direct linking from SVN repository. Updates mimetype on docs CSS to allow direct linking from SVN repository. Nov 25, 2008 r7 (Updates mimetype on docs to allow direct linking from SVN re...) committed by api....@google.com - Updates mimetype on docs to allow direct linking from SVN repository. Updates mimetype on docs to allow direct linking from SVN repository.

GettingStarted (Introduction to the Ruby Client Library) Wiki page commented on by jcolag - I must be missing something, since everybody else is getting further than I am. After installing the gem (0.0.4) on an Ubuntu Linux server, though that shouldn't make a difference, with Ruby 1.8.6 and Rails 2.3.3, the MySpace example gives me this: ./opensocial.rb:10: uninitialized constant OpenSocial (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from opensocial.rb:2 Yes, I added "require 'rubygems'," figuring that might resolve it, but no go. It sounds like it didn't install correctly, but I found everything to make Brendan's suggested patch. Might anybody have any thoughts on this?

I must be missing something, since everybody else is getting further than I am. After installing the gem (0.0.4) on an Ubuntu Linux server, though that shouldn't make a difference, with Ruby 1.8.6 and Rails 2.3.3, the MySpace example gives me this: ./opensocial.rb:10: uninitialized constant OpenSocial (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' from opensocial.rb:2 Yes, I added "require 'rubygems'," figuring that might resolve it, but no go. It sounds like it didn't install correctly, but I found everything to make Brendan's suggested patch. Might anybody have any thoughts on this?

Earlier this year

Older