WebViewTwitter

This example application is a simple Twitter client that shows tweets by selected users. Users can be added to a Favorites List stored on the device. The app uses the jQuery JavaScript library and its jQtouch plug-in, and the MoSync Wormhole C++ Library.

Tweet Reader screen (Android)	User tweets screen (Android)

This example is included in the MoSync SDK installation in the /examples folder. For information on importing the examples into your workspace, see Importing the Examples.

Behavior

When started, this example application displays the main application screen headed "Tweet Reader". On this screen the user can enter the username of a Twitter user. On tapping View Tweets by this user, a second screen is displayed showing that Twitter user's recent tweets.

On the main application screen the user can also add the Twitter user's username to a Favourites List, or tap on an entry in the Favourites List to go straight to that person's tweets.

In the Code

The following technologies are used in this application:

• HTML5, Javascript, and jQtouch for the design the main user-interface elements and handling of UI events.

• The JQuery getJSON function to call the Twitter API and parse the JSON document that is returned as a result.

• The MoSync Wormhole Library is used for bi-directional communication between MoSync C++ code and JavaScript.

• MoSync File API (C++) to write to and read from the device's file system.

Included in the example is a set of wrapper functions for accessing the MoSync File API from Javascript.

WebViewTwitter.cpp is the main file. It includes an implementation of WebAppMoblet. The example application uses class MessageStreamJSON to process and respond to messages coming from JavaScript.

Note that this example doesn't make use of the full wormhole.js library, it uses a subset of that library, the file mosync-bridge.js, which is used to send messages between JavaScript and C++. For an example that uses the full Wormhole JavaScript library, check out the WormholeDemo program.

All of the HTML5 and JavaScript-related files and libraries are located in the LocalFiles directory, and bundled with the application and extracted to the local file system of teh device the first time the application launches

The Resources.lst file has a default entry for the bundled files that should not be removed unless you want to remove all of the HTML5 functionality.