closes #10 using  Jason Davies word cloud instead of writing the layout engine our selves

http://www.jasondavies.com/wordcloud/
Upgraded to Android 18 and fragments.
Moved web view into a fragment.
Fixing package name import.
New cloud icon (from official Android files)
Making layout changes and adding menus. Also adding new activity for creating/editing clouds.
Added action bar and menu entries for both the activities and the fragments, in the proper order so that they are called as needed depending on the device using the application. Also started working on a new activity (CloudEditActivity) that will also need a corresponding fragment for tablets. This will be used for both creating new and editing existing wordcloud entries.
Added manifest_version: 2 for chrome extension compatibility.
Reverting the newly added Edit activity, and instead will reuse the detail activity container for a new fragment for editing/creating.
Deleted leftover file.
Added new packages (database and contentprovider). Added new classes (sqlite helper, table class, content provider, and edit activity). Decided to move the editing/creating of records to their own activity. It's just SO much easier in the end vs. one fragment container that would hold not only the new/edit regular fragment, but also a webview fragment.

CloudDetailFragment needs to be able to change the dummy mItem variable to something real that will then be passable to the javascript so that the JS will be aware of the text from the sqlite db.

CloudEditActivity needs to be fixed so that not only will it create new records, but that it also takes the proper call to edit records.
It's working!
Removed all dummy data. Added new function to Android/JS interface.
Removed console.log
Added a default "sample entry" for new users so they have something to view right away when the app launches for the first time. Added database connectivity, so the wordcloud text and user-selected font from the database show up properly in the detail view.

TODO: (1) Fix onconfigurationchange crash (new entry with screen rotate) and onsaveinstancestate crash (new entry with home button pressed). (2) Relaunch detail view fragment when user edits so the change is visible immediately. (3) Perhaps make simplelistview something a bit more nice looking, as well as a UI improvement to the new/edit activity layout.
Enlarged confirm button. Added ability to make new cloud entry while already viewing the details of a different entry.
Small bug fixes, and new code to try SVG and PNG export.
Merge pull request #15 from iLanguage/d3wordcloud

D3wordcloud