| | 9 | The project plan is now different from the one in the proposal in that, I will be implementing CAP Alert creation then CAP template and then CAP profile. |
| | 10 | ||= Component =||= Stage =|| |
| | 11 | ||CAP alert creation interface || Started || |
| | 12 | The data model is in place. I am now creating the various UI widgets necessary for the same, namely: |
| | 13 | * -KeyValue widget: for cap fileds such as Codes and Parameters: this is a widget will help in input of key-value pair data.- |
| | 14 | * CAP alert selection widget: for selecting a previous CAP alert (for referencing in a new one) |
| | 15 | * CAP multiple info widget: for input of multiple <info> sections. |
| | 16 | * CAPResourceWidget: for uploading one or more files for distribution in the CAP alert, or pick a resource previously uploaded (tabbed view) |
| | 17 | * CAP Area selection widget: This will be for selection of a polygon from the map and encoding it in wkt and WGS84 formats |
| | 18 | ||= Component =||= Stage =|| |
| | 19 | || CAP Alert import/export || Not started || |
| | 20 | * Plan: |
| | 21 | ||= Component =||= Stage =|| |
| | 22 | || CAP template creation interface || Not started || |
| | 23 | * Plan: set a flag in the alert table and all the children (has a) tables to denote a row belongs to a template. |
| | 24 | ||= Component =||= Stage =|| |
| | 25 | || CAP Profile creation interface || Not started || |
