Changes between Version 10 and Version 11 of BluePrint/CAPMobileApp


Ignore:
Timestamp:
01/17/16 21:57:03 (6 years ago)
Author:
Lutz Frommberger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CAPMobileApp

    v10 v11  
    6767
    6868== Current Implementation ==
     69{{{#!comment
    6970<Leave open for a list of existing implementation of this solution in Sahana Eden:>
    7071<*a brief description of the implementation (date/time, name, design options chosen)>
     
    7374<*links to case studies>
    7475<*short analysis of achievements/problems>
     76}}}
    7577
    76 Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile
    77 handhelds. If necessary suggest some GUI tweaks to harmonize the
    78 desktop version with the mobile screens.
     78Currently, there is no implementation within Sahana Eden.
    7979
    80 Step 2. Design hazard specific alert authoring and issuing GUIs. For
    81 example, Alerting Authorities, in a local area (Barangay,
    82 Gramaniladari, Thaluk, etc) do not need the full CAP message but a few
    83 attributes like the area and water level. We will target on delivering
    84 3-5 mobile GUIs for Landslide, Flood, Accident,
    85 
    86 Step 3. Develop the requirements/design for using the concept of
    87 Pictographs in Alerting and other features such as a wake up function
    88 to sound an Audible Alarm etc. I think we should do the same with the
    89 web GUI such that we can set a siren audio to sound for a specific
    90 warning_priority threshold.
    91 
    92 We may have to look for funding outside of the ESCAP project for step 3.
    9380
    9481== Planned Implementation ==