Sunday, July 27, 2008
What's Where...
As we approach the magic moment of Facebook users being able to experiment with the new interface, here's a recap of where things are with the book examples:
1. JF Example (the code from the end of the book in Chapter 15--the complete example), is running with old libraries and code that matches the book. So far it seems to be OK--the libraries on the Facebook end work as promised in letting old apps run. For production, the desire is obviously to move to the new interface, but to follow the book, we're keeping the code the same. If you find an issue, please email me.
2. ChamplainArtsQA (apps.facebook.com/developmentqa) temporarily points to the experimental version of Chapter 15 that you can download. The only two changes since that download was created was the removal of the two require_add lines of code. This app is running with the new UI libraries. Again, send email with an issues. (The only change to the libraries is commenting out the inclusion of jsonwrapper--our server is running PHP 5.2.6 which includes it.)
Jesse
1. JF Example (the code from the end of the book in Chapter 15--the complete example), is running with old libraries and code that matches the book. So far it seems to be OK--the libraries on the Facebook end work as promised in letting old apps run. For production, the desire is obviously to move to the new interface, but to follow the book, we're keeping the code the same. If you find an issue, please email me.
2. ChamplainArtsQA (apps.facebook.com/developmentqa) temporarily points to the experimental version of Chapter 15 that you can download. The only two changes since that download was created was the removal of the two require_add lines of code. This app is running with the new UI libraries. Again, send email with an issues. (The only change to the libraries is commenting out the inclusion of jsonwrapper--our server is running PHP 5.2.6 which includes it.)
Jesse
Monday, July 21, 2008
Very Important New Facebook App Procedure
As Facebook moves to the launch of the revised interface, the application adding/authorizing procedure is becoming more refined. New code is due to roll out today (Monday, 7/21).
As we knew, users will no longer add applications. Now, they will authorize applications to access their user data. The former post-add URL on the app setup page is now the post-authorization URL and behaves in the same way so you can use the callback at that URL to store allowable information.
Users can opt out of sharing their data either globally in their profile (for all apps) or by not authorizing an individual application.
The change is a simplification for the user; for apps it's pretty much the same except that the once ubiquitous require_add calls need to be removed. (This is discussed in the book because it's been known for a long time--require_login is the preferred code.)
The require_add call will remain because in the case of Facebook Pages (not users), the Page (via its administrators) will be able to add apps.
As we knew, users will no longer add applications. Now, they will authorize applications to access their user data. The former post-add URL on the app setup page is now the post-authorization URL and behaves in the same way so you can use the callback at that URL to store allowable information.
Users can opt out of sharing their data either globally in their profile (for all apps) or by not authorizing an individual application.
The change is a simplification for the user; for apps it's pretty much the same except that the once ubiquitous require_add calls need to be removed. (This is discussed in the book because it's been known for a long time--require_login is the preferred code.)
The require_add call will remain because in the case of Facebook Pages (not users), the Page (via its administrators) will be able to add apps.
Subscribe to Posts [Atom]
