All Things R&D
GSoC 2012 Weekly Report on OI WebIntents Agent (Aug 14-Aug 20)
August 20, 2012Posted by on
This is the last report for GSoC 2012.
Now OI WebIntents can do three major tasks as specified in the application proposal:
- Invoke both Web applications and Android Applications from a Web page
- Invoke both Web applications and Android Applications from an external Android application
- Web application management
Now OI WebIntents can work well on both handsets and tablets with different screen design.
Another blog post describe the user guidelines to use OI WebIntents Agent with screenshots.
Data Structure and Class Implementation
1. Main activities
There are two activity classes which are important for this part:
WebIntentsAgentActivity is the main activity for this application and launched when the app takes off. It creates the navigation menu items and if necessary starts off the WebAppManagementActivity for Web application management.
2. Data Storage and Content Provider
Two classes are important for this part:
Each database table is represented by an internal class of WebIntentsProvider with its column fields and CONTENT_URI. For example, the database table ‘web_intents’ is represented by WebIntentsProvider.WebIntents.
3. Web page parsing, revising and loading
4. Web application Registration
Since most available Web applications for Web Intents are implemented as Chrome Extensions. I modified four sample applications and included them in this application. They are:
- Web Intents Debugger
- Share Link to Twitter
- Shorten with Goo.gl
- Chromerly URL-shortener
As a result, a procedure (FileReaderThread) for registering and loading local applications was also developed. However, this application also support online app registration. webintents.org now supports some online applications. Our project is applicable for the following online application:
They can be discovered by browsing the following Web pages:
5. Web application management
The following classes are important for this part:
WebAppListFragment is for displaying a list of Web application and WebIntentsByAppListFragment shows web intents for a specific web application. For a tablet, both WebAppListFragment and WebIntentsByAppListFragment will be added into WebAppManagementActivity. However, for a handset, WebAppListFragment is contained in WebAppManagementActivity while WebIntentsByAppListFragment is loaded into WebIntentsByAppActivity. The purpose is for supporting multiple screens.
6. Invoke Web applications from external Android apps
A helper class named WebIntentsHelper is for this requirement. Any external Android application can invoke Web applications by the following step:
Install OI WebIntents Agent -> Import webintents-helper.jar into libs -> Create a application chooser by invoke WebIntentsHelper.createChooserWithWebActivities()
This method will create a chooser dialog in the context of the calling application now.
Failure method to report