The goal of this section is to give an overview of the CloudCare system for developers who are new to CloudCare. It should allow one’s first foray into the system to be as painless as possible by giving him or her a high level overview of the system.
On the frontend, CloudCare is a single page backbone.js app. The app, module, form, and case selection parts of the interface are rendered by backbone while the representation of the form itself is controlled by touchforms (described below).
/a/<domain>/cloudcare/apps/<urlPath> into the browser, the cloudcare_main view is called. This page loads the backbone app and perhaps bootstraps it with the currently selected app and case.
The Backbone Views¶
The backbone app consists of several
Backbone.Views subclasses. What follows is a brief description of several of the most important classes used in the CloudCare backbone app.
Renders the list of apps in the current domain on the left hand side of the page.
Renders the list of modules in the currently selected app on the left hand side of the page.
Renders the list of forms in the currently selected module on the left hand side of the page.
Renders the list of cases for the selected form. Note that this list is populated asynchronously.
Renders the table displaying the currently selected case’s properties.
AppView holds the module and form list views. It is also responsible for inserting the form html into the DOM. This html is constructed using JSON returned by the touchforms process and several js libs found in the
/touchforms/formplayer/static/formplayer/script/directory. This is kicked off by the AppView’s
_playFormmethod. AppView also inserts
cloudCareCases.CaseMainViews as necessary.
AppMainView (not to be confused with AppView) holds all of the other views and is the entry point for the application. Most of the applications event handling is set up inside AppMainView’s
initializemethod. The AppMainView has a router. Event handlers are set on this router to modify the state of the backbone application when the browser’s back button is used, or when the user enters a link to a certain part of the app (like a particular form) directly.
The backbone app is not responsible for processing the XFrom. This is done instead by our XForms player, touchforms. Touchforms runs as a separate process on our servers, and sends JSON to the backbone application representing the structure of the XForm. Touchforms is written in jython, and serves as a wrapper around the JavaRosa that powers our mobile applications.