sfncook/ictracker_angular

ictracker_angular's Issues

Push/pull updates to all clients

Incident Timer needs to use Incident createdAt

Currently using t0 which is set for each client. Need to get this from the Incident table createdAt or a new column which records the actual incident t0.

Implement OSR like v1

Copy the OSR dialog from v1 and convert it to the new v2 format. (use button tags, new dialog format, angular directives, etc.) You'll then need to create a new OSR table in Parse and add a bunch of boolean and string columns that correspond to all the toggle buttons and drop down lists (respectively) on the OSR dialog. Also make sure the black/green horizontal progress bar on the OSR button works correctly. For paired toggle buttons (e.g. Offensive/Defensive) there should be just one boolean column in the table.

Estimated Time: 2hours

Get Sector Benchmarks working

Just like ICT v1

Get Move units working

Just like ICT v1

(Future) Add all forms

Needs design work

Implement Reports

Just like ICT v1

(Future) Local datastore

Need a local datastore option for development and in case connection is lost to the server.

Finish Actions Dialog

Work is started on the Actions Dialog, it just needs to be finished it up. Look to ICT v1 for complete working example. Basically we need to get the v2 code formatted just like v1.

Parse table: ActionType
Code: app/js/incident_form_controller.js, app/incident_form.html
In both files search for "ActionsDlg"

Estimated time: 2.5 hours

Get PAR working

Make sector PAR work just like ICT v1

Increase Unit Options dialog buttons to match v1 format

Estimated time: 0.5 hour

Select new unit when selected unit is removed from tbar

Add several units to a tbar. Select a unit. Remove that unit from the tbar. Notice that the removed unit's actions remain visible. Need to simply detect this and select first unit in list.

Estimated time: 1.0 hour

Design Users, Rolls, and Departments

Need to design how users, rolls and departments are going to interact

Save strategy value to Parse

When user clicks the Strategy button (upper right corner of the screen) open a Strategy dialog, let the user pick a new strategy, update this and save to Parse. You'll need to look at v1 and copy the Strategy dialog (might be called "mode" in v1). You'll also need to convert the Strategy dialog to Angular format. This will involve changing buttons from div's with a 'button' class to HTML elements named 'button'. You'll need to convert the dialog formatting from the home-grown dialog box (v1) to the JQuery UI dialog box (v2). You can look at other dialogs in both to see the differences. In the dialog there are 2 buttons (not including the dialog Close button). If either the OFFENSIVE or DEFENSIVE button is clicked you will save the text of that button to the Incident object, it should be reflected on the Strategy button (just like v1) and should be saved to Parse. Also, notice that the color of the Strategy button needs to change. This is accomplished with the ng-class directive (look for examples elsewhere in the code or tutorials online). OFFENSIVE strategy should turn the button green and DEFENSIVE should turn it red. Upon refreshing or opening the incident again the chose strategy will then be repopulated from Parse and populate the Strategy button.

Estimated time: 1.0 hours

Save Upgrade to Parse

When user makes changes to the Upgrade dialog save these choices to the Upgrade table of Parse.

En Route and On Scene should toggle each other. They both save to the same column in the table, isEnRoute.

Balance To toggles true/false. If it's true then it's green and all the buttons in the right column is enabled.

All 5 of the right column buttons will save to their corresponding columns on the table. Also, only one of the 5 right column buttons is TRUE at a time - they all toggle each other. The right column button that is true is then listed on the bottom of the Upgrade button (right side of the screen).

Estimated time: 1.5 hours

Save sector direction and number to Parse.

Click on a Sector title to open the "Sector Names Dialog". At the top-left of that dialog there are round buttons that are the "directions" ("Sub", "N', 'S', 'W', 'E') and the "numbers" ('1' - '9'). These are updating on the sector when you chose them but the values need to be saved to the direction and number columns in the Sector table, respectively.

Estimated time: 1hour

Update timer values using JQuery

Updating timer values on the screen with Angular intervals seems to result in inefficient re-rendering of all scopes in the application. I think if we just save the t0's to Parse, then update the timer values on the screen using JQuery and DOM manipulation we'll be better off.

(Future) Branch and control

Needs design work.

Save inc_addy and inc_number

When user changes Incident Info (incident address or incident number) (button in the very upper left corner of the screen) save these to the inc_address and inc_number columns in the Incident table in Parse. You'll need to look at v1 and copy the Incident Info dialog. You'll also need to convert the Incident Info dialog to Angular format. This will involve changing buttons from div's with a 'button' class to HTML elements named 'button'. You'll need to convert the dialog formatting from the home-grown dialog box (v1) to the JQuery UI dialog box (v2). You can look at other dialogs in both to see the differences. In the dialog there are 2 input boxes and 4 buttons (not including the dialog Close button). The 2 Clear buttons will simply clear their corresponding input text box but not close the dialog. The Cancel button should close the dialog and not update anything. The OK button should close the dialog, update the incident info which should be reflected in the Incident Info button (upper left corner of screen), and save the info to Parse. Upon refreshing or opening the incident again this info (number and address) will then be repopulated from Parse and populate the Incident Info button.

Estimated time: 2.5 hours

Units Dialog - units need to turn green

When units have been added to any sector they should be a green color on the Units Dialog.

Implement IAP dialog just like v1

When user clicks the IAP button (right-side, middle of the screen) open a IAP dialog (title "Action Plan = Offensive or Defensive?"), let the user toggle buttons or write text into text boxes, save all choices to Parse. There is no other updates on the screen other than in the dialog itself. You'll need to look at v1 and copy the IAP dialog. You'll also need to convert the IAP dialog to Angular format. This will involve changing buttons from div's with a 'button' class to HTML elements named 'button'. You'll need to convert the dialog formatting from the home-grown dialog box (v1) to the JQuery UI dialog box (v2). You can look at other dialogs in both to see the differences.

In the dialog there are 11 buttons (not including the dialog Close button). The top 8 buttons ('Building', 'Fire', etc.) should toggle orange. The 2 right-side buttons ('Vent' and 'Sprinkler') should toggle green. And the third right-side button ('Show Evacuation Location') should not toggle in color, but instead should toggle what it says ('Show/Hide ...') and it should alternatively show or hide an extra text area for the event location.

The values of all these buttons should be saved to corresponding Boolean columns in the Iap table on Parse. The values of all the text areas should be saved to corresponding String columns on Parse. Upon refreshing or opening the incident again the chose strategy will then be repopulated from Parse and populate the Strategy button.

Note that you'll need to load the IAP row from the Iap table in Parse when the incident loads. Look at how we are loading sectors. There is a column in the Sector table and the Iap table for the incident. So you can just imitate how the sectors are loaded for the IAP row. (Hope this makes sense) If the IAP does not exist for the incident then you should create it and populate all the boolean values as FALSE.

Estimated time: 4.5 hours

Implement Mayday Dialog

Just like ICT v1

Add actions from Actions Dialog not working

Open Actions Dialog for a sector/unit. Click an action. It should add/remove (toggle) the action to the unit but instead we get an error message.

(Future) Messaging system? IRC?

Implement Objectives dialog just like v1

Copy the Objectives dialog from v1 and convert it to the new v2 format. (use button tags, new dialog format, angular directives, etc.) You'll then need to create a new Objectives table in Parse and add a bunch of boolean columns that correspond to all the toggle buttons on the Objectives dialog. Also make sure the black/green horizontal progress bar on the Objectives button works correctly.

Estimated Time: 2hours

(Future) List who is logged in an viewing current incident

Improve "Loading" graphic

While loading info from Parse need an animated spinner and then some nice fade-in/fade-out graphics for the results. Also, some error messages would be great.