Hi, all
Continuing the announcements on Facebook API ME, yesterday, I released Facebook API ME v1.0 for Android. This version uses WebView component from Android API to display the authentication page. As I explained in this tutorial, to use the API for other platforms, you just need to work with the respective wrapper class for the target platform. Regarding Android, you will have to use WebViewAuthDialogWrapper.
...
WebView webView = ...;
AuthDialogWrapper pageWrapper =
new WebViewAuthDialogWrapper(webView);
pageWrapper.setAppId("App Id goes here");
pageWrapper.setAppSecret("App Secret goes here");
pageWrapper.setRedirectUri("Redirect Uri goes here");
pageWrapper.setPermissions(new String[] {Permission.OFFLINE_ACCESS, Permission.PUBLISH_STREAM});
pageWrapper.addAuthenticationListener(this);
pageWrapper.login();
...
Besides the release package, there is also a sample app demonstrating how to implement the authentication process for this platform. Here it goes the download link.
I hope you guys enjoy it.
See you in the next post...
Showing posts with label facebook api me. Show all posts
Showing posts with label facebook api me. Show all posts
Jun 20, 2011
Jun 18, 2011
Facebook API ME for Blackberry
Hi, all
This afternoon, I released Facebook API ME v1.0 for Blackberry. This version uses BrowserField component from RIM API to display the authentication page. As I explained in this tutorial, to use the API for other platforms, you just need to work with the respective wrapper class for the target platform. Regarding Blackberry, you will have to use BrowserFieldAuthDialogWrapper.
...
BrowserField browserField = ...;
AuthDialogWrapper pageWrapper =
new BrowserFieldAuthDialogWrapper(browserField);
pageWrapper.setAppId("App Id goes here");
pageWrapper.setAppSecret("App Secret goes here");
pageWrapper.setRedirectUri("Redirect Uri goes here");
pageWrapper.setPermissions(new String[] {Permission.OFFLINE_ACCESS, Permission.PUBLISH_STREAM});
pageWrapper.addAuthenticationListener(this);
pageWrapper.login();
...
Besides the release package, there is also a sample app demonstrating how to implement the authentication process for this platform. Here it goes the download link.
I hope you guys enjoy it.
See you in the next post...
This afternoon, I released Facebook API ME v1.0 for Blackberry. This version uses BrowserField component from RIM API to display the authentication page. As I explained in this tutorial, to use the API for other platforms, you just need to work with the respective wrapper class for the target platform. Regarding Blackberry, you will have to use BrowserFieldAuthDialogWrapper.
...
BrowserField browserField = ...;
AuthDialogWrapper pageWrapper =
new BrowserFieldAuthDialogWrapper(browserField);
pageWrapper.setAppId("App Id goes here");
pageWrapper.setAppSecret("App Secret goes here");
pageWrapper.setRedirectUri("Redirect Uri goes here");
pageWrapper.setPermissions(new String[] {Permission.OFFLINE_ACCESS, Permission.PUBLISH_STREAM});
pageWrapper.addAuthenticationListener(this);
pageWrapper.login();
...
Besides the release package, there is also a sample app demonstrating how to implement the authentication process for this platform. Here it goes the download link.
I hope you guys enjoy it.
See you in the next post...
Jun 5, 2011
Facebook API ME 1.0: Tutorial
Hi, all
As I announced yesterday on Twitter, the first release of Facebook API ME is now available for download. Besides the release package, there is also a sample app, demonstrating how to implement the authentication process.
For while, only the version for eSWT is released. So, if your target device supports eSWT, you will be able to use this package in your Java ME app right away. I am also working on other versions targeted to Blackberry, LWUIT and Android. All of them are now under test phase. I hope to release them very soon. On the other hand, if you cant't wait, check out the source code from the project's repository. You need to add yourself to the project as an Observer member to be able to check out.
Let's start the tutorial!
Registering an App
You need to register an app on Facebook's Developer page. The process is pretty simple and straightforward. The goal of this registration is to obtain some keys that are required by authentication process: App Id, App Secret and Redirect Uri. This process is very similar to Twitter's app registration process.
Once you have the keys, let get to the API itself.
Browser Component
In your app, you need to display Facebook's Login page, so your user can enter his credentials and then grant access to your app. This process is implemented by the API. You just need to provide a browser component instance and then the API takes care of the rest. Considering the eSWT version, you need to provide an instance of Browser class.
Wrapper Class
Once the browser instance is created, you have to wrap it with an instance of AuthDialogWrapper class. This class is responsible for managing the authentication and delegates the events to your app. Considering the eSWT version, you have to instantiate the BrowserAuthDialogWrapper subclass.
Setting Up the Keys
The wrapper object must be set up, so it can handle the authentication process properly for you app. There are some "set" methods that can be used to inform your App Id, App Secret and Redirect Uri. If you prefer, you can enter the keys in the constructor.
...
Browser browser = new Browser(browserComp, SWT.TOP);
AuthDialogWrapper pageWrapper = new BrowserAuthDialogWrapper(browser);
pageWrapper.setAppId("App Id goes here");
pageWrapper.setAppSecret("App Secret goes here");
pageWrapper.setRedirectUri("Redirect Uri goes here");
...
Permissions
Most services provided by Facebook API requires explicit authorization by user. So, during the authentication process you must inform which permissions the services that you intend to work with, must be granted by user.
...
pageWrapper.setPermissions(new String[] {Permission.OFFLINE_ACCESS, Permission.PUBLISH_STREAM});
...
This code snippet says the app will request permission to perform authorized requests on behalf of the user at any time (OFFLINE_ACCESS) and publish content to a user's feed at any time PUBLISH_STREAM. For the full list of permissions provided by Facebook API, click here.
Authentication Events
In order to know if the user granted or denied permission to the app, you need to register a listener of the type AuthenticationListener. This interface has three methods:
- onAuthorize(String token)
- onAccessDenied(String message)
- onFail(String error, String message)
onAuthorize() means the user has granted permission to the app along with the Access Token. Keep this token, since you will use it to sign all your requests to Facebook API. This token works to identify your app. So, from this point on, you can dismiss the login page and start publishing links, comments, etc.
onAccessDenied() means the user has denied access to his Facebook account. It does not mean the user can change his mind later and then authorize your app.
onFail() means that something went wrong during the authentication process. Just try again!
...
pageWrapper.addAuthenticationListener(this);
...
public void onAuthorize(String token) {
System.out.println("onAuthorize: " + token);
}
public void onAccessDenied(String message) {
System.out.println("access_denied: " + message);
}
public void onFail(String error, String message) {
System.out.println("error: " + error + " message: " + message);
}
...
Displaying Login Page
The Facebook's Login page will just be requested and displayed, as soon as the method login() be called.
...
pageWrapper.login();
...
Dispatching Requests
The API also provides a helper class, called Dispatcher, responsible for dispatching the requests, synchronously or asynchronously, to Facebook API. Each Dispatcher instance must be associated to an access token, so all requests dispatched be signed automatically.
...
Dispatcher dispatcher = Dispatcher.getInstance("Access Token goes here");
...
Dispatcher Events
When you work with asynchronous requests, it is recommended to register a listener in order to know whether they were successfully processed. This listener is defined by DispatcherListener interface. This interface has two methods:
- onComplete(Request request, Response response)
- onFail(Request request, Throwable error)
onComplete() means the request was processed successfully and returns the result (response).
onFail() means the request failed, returning the cause.
...
dispatcher.addDispatcherListener(this);
...
public void onComplete(Request request, Response response) {
...
}
public void onFail(Request request, Throwable error) {
...
}
...
Posting on User's Wall
To publish a text on user's wall is pretty simple. Just instantiate an object of Status class, informing the text in the constructor. The other constructor allows you to post a text on a friend's wall.
...
Status status = new Status("Text goes here");
dispatcher.dispatch(status); //synchronously
//or dispatcher.addToQueue(status); //asynchronously
...
Status status = new Status("Text goes here", "Friend's Id goes here");
dispatcher.dispatch(status);
...
Sharing Link
To share a link is as easy as posting on wall. Just instantiate an object of Link class, informing the URL in the constructor. The other constructor allows you to define how the link will be displayed.
...
Link link = new Link("Link's URL goes here");
dispatcher.dispatch(link);
...
Link link = new Link("Link'URL goes here", "Link's Picture Uri goes here", "Link's Name goes here", "Link's Caption goes here", "Link's Description goes here", "Link's Message goes here", "Friend's Id goes here");
dispatcher.dispatch(link);
...
Retrieving Friends List
To retrieve the user's friends list just instantiate an object of Friends class. This request returns an instance of Friends.Response, which is Enumeration.
...
Friends friends = new Friends();
Friends.Response friendsEnum = (Friends.Response) dispatcher.dispatch(friends);
while (friendsEnum.hasMoreElements()) {
Friends.Response friend = (Friends.Response)friendsEnum.nextElement();
String friendId = friend.getId();
String friendName = friend.getName();
...
}
...
Profile Picture
To retrieve a friend's profile picture, create an instance of Picture class, informing the friend's Id in the constructor. This request returns an instance of Picture.Response.
...
Picture picture = new Picture("Friend's Id goes here");
Picture.Response pictureResp = (Picture.Response)dispatcher.dispatch(picture);
byte[] imageBytes = pictureResp.getData();
...
Revoking Authorization
Just in case an user decides to remove your app's authorization to access his Facebook account. For that, use the request defined by RevokeAuthorization class, informing the access token in the constructor. Once this request is processed, the access token is expired and you app will no longer be able to access the user's account. To access it again, the entire authentication process must be redone.
...
RevokeAuthorization revoke = new RevokeAuthorization("Access Token goes here");
dispatcher.dispatch(revoke);
...
Log out
The wrapper class AuthDialogWrapper has a method called logout(). Call this method in order to remove any cookie or logged user's data left by Facebook's Login page in our browser component. It is recommend to call this method when the user removes the app's authorization.
It is important to point out that all items presented here are valid for all versions of Facebook API ME. It does matter if you are working on Blackberry, LWUIT or Android. The steps are all the same, except at item 3, regarding the type of subclass. Each platform has its own subclass of AuthDialogWrapper.
So, I hope this tutorial has been useful for you guys, as well as the API itself.
As soon as the release of the other platforms are released, I will let everybody knwos.
See you in the next post...
As I announced yesterday on Twitter, the first release of Facebook API ME is now available for download. Besides the release package, there is also a sample app, demonstrating how to implement the authentication process.
For while, only the version for eSWT is released. So, if your target device supports eSWT, you will be able to use this package in your Java ME app right away. I am also working on other versions targeted to Blackberry, LWUIT and Android. All of them are now under test phase. I hope to release them very soon. On the other hand, if you cant't wait, check out the source code from the project's repository. You need to add yourself to the project as an Observer member to be able to check out.
Let's start the tutorial!
Registering an App
You need to register an app on Facebook's Developer page. The process is pretty simple and straightforward. The goal of this registration is to obtain some keys that are required by authentication process: App Id, App Secret and Redirect Uri. This process is very similar to Twitter's app registration process.
Once you have the keys, let get to the API itself.
Browser Component
In your app, you need to display Facebook's Login page, so your user can enter his credentials and then grant access to your app. This process is implemented by the API. You just need to provide a browser component instance and then the API takes care of the rest. Considering the eSWT version, you need to provide an instance of Browser class.
Wrapper Class
Once the browser instance is created, you have to wrap it with an instance of AuthDialogWrapper class. This class is responsible for managing the authentication and delegates the events to your app. Considering the eSWT version, you have to instantiate the BrowserAuthDialogWrapper subclass.
Setting Up the Keys
The wrapper object must be set up, so it can handle the authentication process properly for you app. There are some "set" methods that can be used to inform your App Id, App Secret and Redirect Uri. If you prefer, you can enter the keys in the constructor.
...
Browser browser = new Browser(browserComp, SWT.TOP);
AuthDialogWrapper pageWrapper = new BrowserAuthDialogWrapper(browser);
pageWrapper.setAppId("App Id goes here");
pageWrapper.setAppSecret("App Secret goes here");
pageWrapper.setRedirectUri("Redirect Uri goes here");
...
Permissions
Most services provided by Facebook API requires explicit authorization by user. So, during the authentication process you must inform which permissions the services that you intend to work with, must be granted by user.
...
pageWrapper.setPermissions(new String[] {Permission.OFFLINE_ACCESS, Permission.PUBLISH_STREAM});
...
This code snippet says the app will request permission to perform authorized requests on behalf of the user at any time (OFFLINE_ACCESS) and publish content to a user's feed at any time PUBLISH_STREAM. For the full list of permissions provided by Facebook API, click here.
Authentication Events
In order to know if the user granted or denied permission to the app, you need to register a listener of the type AuthenticationListener. This interface has three methods:
- onAuthorize(String token)
- onAccessDenied(String message)
- onFail(String error, String message)
onAuthorize() means the user has granted permission to the app along with the Access Token. Keep this token, since you will use it to sign all your requests to Facebook API. This token works to identify your app. So, from this point on, you can dismiss the login page and start publishing links, comments, etc.
onAccessDenied() means the user has denied access to his Facebook account. It does not mean the user can change his mind later and then authorize your app.
onFail() means that something went wrong during the authentication process. Just try again!
...
pageWrapper.addAuthenticationListener(this);
...
public void onAuthorize(String token) {
System.out.println("onAuthorize: " + token);
}
public void onAccessDenied(String message) {
System.out.println("access_denied: " + message);
}
public void onFail(String error, String message) {
System.out.println("error: " + error + " message: " + message);
}
...
Displaying Login Page
The Facebook's Login page will just be requested and displayed, as soon as the method login() be called.
...
pageWrapper.login();
...
Dispatching Requests
The API also provides a helper class, called Dispatcher, responsible for dispatching the requests, synchronously or asynchronously, to Facebook API. Each Dispatcher instance must be associated to an access token, so all requests dispatched be signed automatically.
...
Dispatcher dispatcher = Dispatcher.getInstance("Access Token goes here");
...
Dispatcher Events
When you work with asynchronous requests, it is recommended to register a listener in order to know whether they were successfully processed. This listener is defined by DispatcherListener interface. This interface has two methods:
- onComplete(Request request, Response response)
- onFail(Request request, Throwable error)
onComplete() means the request was processed successfully and returns the result (response).
onFail() means the request failed, returning the cause.
...
dispatcher.addDispatcherListener(this);
...
public void onComplete(Request request, Response response) {
...
}
public void onFail(Request request, Throwable error) {
...
}
...
Posting on User's Wall
To publish a text on user's wall is pretty simple. Just instantiate an object of Status class, informing the text in the constructor. The other constructor allows you to post a text on a friend's wall.
...
Status status = new Status("Text goes here");
dispatcher.dispatch(status); //synchronously
//or dispatcher.addToQueue(status); //asynchronously
...
Status status = new Status("Text goes here", "Friend's Id goes here");
dispatcher.dispatch(status);
...
Sharing Link
To share a link is as easy as posting on wall. Just instantiate an object of Link class, informing the URL in the constructor. The other constructor allows you to define how the link will be displayed.
...
Link link = new Link("Link's URL goes here");
dispatcher.dispatch(link);
...
Link link = new Link("Link'URL goes here", "Link's Picture Uri goes here", "Link's Name goes here", "Link's Caption goes here", "Link's Description goes here", "Link's Message goes here", "Friend's Id goes here");
dispatcher.dispatch(link);
...
Retrieving Friends List
To retrieve the user's friends list just instantiate an object of Friends class. This request returns an instance of Friends.Response, which is Enumeration.
...
Friends friends = new Friends();
Friends.Response friendsEnum = (Friends.Response) dispatcher.dispatch(friends);
while (friendsEnum.hasMoreElements()) {
Friends.Response friend = (Friends.Response)friendsEnum.nextElement();
String friendId = friend.getId();
String friendName = friend.getName();
...
}
...
Profile Picture
To retrieve a friend's profile picture, create an instance of Picture class, informing the friend's Id in the constructor. This request returns an instance of Picture.Response.
...
Picture picture = new Picture("Friend's Id goes here");
Picture.Response pictureResp = (Picture.Response)dispatcher.dispatch(picture);
byte[] imageBytes = pictureResp.getData();
...
Revoking Authorization
Just in case an user decides to remove your app's authorization to access his Facebook account. For that, use the request defined by RevokeAuthorization class, informing the access token in the constructor. Once this request is processed, the access token is expired and you app will no longer be able to access the user's account. To access it again, the entire authentication process must be redone.
...
RevokeAuthorization revoke = new RevokeAuthorization("Access Token goes here");
dispatcher.dispatch(revoke);
...
Log out
The wrapper class AuthDialogWrapper has a method called logout(). Call this method in order to remove any cookie or logged user's data left by Facebook's Login page in our browser component. It is recommend to call this method when the user removes the app's authorization.
It is important to point out that all items presented here are valid for all versions of Facebook API ME. It does matter if you are working on Blackberry, LWUIT or Android. The steps are all the same, except at item 3, regarding the type of subclass. Each platform has its own subclass of AuthDialogWrapper.
So, I hope this tutorial has been useful for you guys, as well as the API itself.
As soon as the release of the other platforms are released, I will let everybody knwos.
See you in the next post...
May 23, 2011
Facebook API ME & HTMLComponent: Not going well.
Hi, all
Yesterday, I took the day to work on my new project: Facebook API ME. The development is going well, btw. As I explained in the previous posts, the great challenge of this project is the authentication process, since it requires certain browser integration, which is not a trivial thing considering Java ME.
Anyway, the API is now working properly using Browser component from eSWT library. eSWT is available in most Nokia and Sony Ericsson devices. I intend to release it for developers this week. I will let you guys know.
Regarding LWUIT integration, using HTMLComponent, the work is not going so well. HTMLComponent is not working well with Facebook's authentication pages. Actually, it works well on login page, where the username/password are informed. On the other hand, the page where the user authorizes the app to access his account is not displayed properly. HTMLComponent is not able to display the "Accept" and "Deny" submit buttons. Because of that, the authentication process is not complete.
I tried to check out LWUIT's latest source code from SVN repository, but it seems they are refactoring the code for some reason. There is an error in one of the classes. Because of that, I was not able to generate a jar file. Is there anybody here that could help with that?
I also intend to work on Blackberry integration, using BrowserField component. But as I am not a Blackberry expert, I have to study a little bit to understand how it works so I can work with it.
I let you guys posted.
See you in the next post...
Yesterday, I took the day to work on my new project: Facebook API ME. The development is going well, btw. As I explained in the previous posts, the great challenge of this project is the authentication process, since it requires certain browser integration, which is not a trivial thing considering Java ME.
Anyway, the API is now working properly using Browser component from eSWT library. eSWT is available in most Nokia and Sony Ericsson devices. I intend to release it for developers this week. I will let you guys know.
Regarding LWUIT integration, using HTMLComponent, the work is not going so well. HTMLComponent is not working well with Facebook's authentication pages. Actually, it works well on login page, where the username/password are informed. On the other hand, the page where the user authorizes the app to access his account is not displayed properly. HTMLComponent is not able to display the "Accept" and "Deny" submit buttons. Because of that, the authentication process is not complete.
I tried to check out LWUIT's latest source code from SVN repository, but it seems they are refactoring the code for some reason. There is an error in one of the classes. Because of that, I was not able to generate a jar file. Is there anybody here that could help with that?
I also intend to work on Blackberry integration, using BrowserField component. But as I am not a Blackberry expert, I have to study a little bit to understand how it works so I can work with it.
I let you guys posted.
See you in the next post...
Apr 14, 2011
Facebook API for Java ME: In the works
Hi, all
Let's make it different this time. I use to announce my new projects just when they are ready to go, but let's change the paradigm.
Early this week, I checked in to Kenai, the alpha source code of my Facebook API ME project. The name stands for itself, it is API that allows Java ME apps to access Facebook. In fact, I had already commented on this project in the last post.
The code is in alpha version, but most features are already done and tested. I am stating it is still as alpha, since I need to retest the authentication feature using eSWT
, besides implementing support to LWUIT
, by using HTMLComponent.
Currently, besides authentication, Facebook API ME also supports the following features:
As soon as I have time, I will complete the tests, so I can officially release the API's version 1.0. The source code is already available for check out, just in case you are very curious.
I hope you guys also enjoy this new project.
See you in the next post...
Let's make it different this time. I use to announce my new projects just when they are ready to go, but let's change the paradigm.
Early this week, I checked in to Kenai, the alpha source code of my Facebook API ME project. The name stands for itself, it is API that allows Java ME apps to access Facebook. In fact, I had already commented on this project in the last post.
The code is in alpha version, but most features are already done and tested. I am stating it is still as alpha, since I need to retest the authentication feature using eSWT
, besides implementing support to LWUIT, by using HTMLComponent.Currently, besides authentication, Facebook API ME also supports the following features:
- Post status
- Share link
- Get list of friends
- Get friend's profile picture
As soon as I have time, I will complete the tests, so I can officially release the API's version 1.0. The source code is already available for check out, just in case you are very curious.
I hope you guys also enjoy this new project.
See you in the next post...
Subscribe to:
Posts (Atom)