[Mobile] Improved the breadcrumb navigation at the top of nested pages.
[Code Cleanup] Removed redundant header markup and moved the main one into a template.
[Code Cleanup]
[Mobile/Code Cleanup/Profiles] Cleaned up the mobile profile page so the spacing of the fields didn't have so much extra whitespace.
* [Mobile/Workspaces] Mobile worklists now display their current filters above the list.  Clicking a filter removes it.

* [Mobile/Workspaces] New filters can be added to mobile worklists using quick search functionality.  Clicking the filters button above the list opens a popup that displays all searchable fields.

* [Mobile/Workspaces] Mobile worklists can use existing filter presets.  After clicking on the filters button, all presets are displayed as buttons in a popup.  Clicking one of these buttons will instantly replace the filters.  This is particularly useful in a mobile environment, especially when performing ad-hoc searches rather than using prebuilt workspaces.

* [Mobile/Workspaces] Mobile worklists can be sorted in ascending or descending order on any available column.  The field currently being sorted by is displayed above the list, and the arrow next to the label indicates the sort direction (i.e. asc, desc).

* [Mobile/Workspaces] Mobile worklists can be paged forward and backward.  On subsequent pages, an option is provided to instantly jump back to the first page.  In a slight deviation from the full UI, paging displays the current and total pages along with the total number of results.  In the full UI, paging displays the current position in the results and the total number of results (i.e. no indication is given for the total number of pages).

* [Mobile/Workspaces] Mobile worklists can now display any number of fields for each row.  Since screen space is generally limited on mobile devices, these fields are not displayed as horizontal columns like in the full UI, but as smaller vertical rows beneath each result's heading.  At the moment, the displayed fields are based on useful defaults for each record type.  In the near future this feature will support the ability to decide which fields should be displayed per worklist or worklist type.  This functionality is actually more advanced than the main UI, since it uses the placeholders from Virtual Attendants and snippets instead of being confined by the results from the database.  In the main UI, only a limited amount of information from related records is available as columns (e.g. ticket -> organization).  With the placeholder approach, even content at the end of a long chain of related records can be displayed (e.g. ticket -> first message -> sender -> org -> custom field).
0.0.3