How should multi-tabbed Uis represent events?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Events
    • Hide

      We will provide non-normative guidelines and best practices for multi-tabbed and single-tabbed applications, following the below philosophy and examples: 

      For a multi-tabbed application:

      Patient A is opened, Patient B is opened, without closing Patient A, is represented as: patient-open for Patient A, patient-open for Patient B, no patient-close

      For a single-tabbed application:

      Patient A is opened, Patient B is opened is represented as: patient-open for Patient A, patient-clos_e for Patient A, _patient-open for Patient B

      Generalized Rule:

      Apps shall assume that they are integrating with multi-tabbed applications and shall appropriately send *-close events when a context is closed within their system. 

      The integration may limit the number of tabs supported by app with the user:

      The user interacting in a single tab app: open A, open B: opening of B closes A. Fundamentally, the user working in a single-tabbed application limits the multi-tabbed application to a single tab.  

       

       

       

      Show
      We will provide non-normative guidelines and best practices for multi-tabbed and single-tabbed applications, following the below philosophy and examples:  For a multi-tabbed application: Patient A is opened, Patient B is opened, without closing Patient A, is represented as:  patient-open for Patient A, patient-open for Patient B, no patient-close For a single-tabbed application: Patient A is opened, Patient B is opened is represented as:  patient-open for Patient A, patient-clos_e for Patient A, _patient-open for Patient B Generalized Rule: Apps shall assume that they are integrating with multi-tabbed applications and shall appropriately send *-close events when a context is closed within their system.  The integration may limit the number of tabs supported by app with the user: The user interacting in a single tab app: open A, open B: opening of B closes A. Fundamentally, the user working in a single-tabbed application limits the multi-tabbed application to a single tab.        
    • Isaac Vetter / Bas van der Heuvel: 8-0-0
    • Clarification
    • Non-substantive

      Need to prescriptively describe how multi-tabbed applications should behave. For example, When a second patient's tab is opened and the original patient tab is moved to the background, is that original tab "closed" or is another simply opened? Answer: The original patient's tab is not closed.

            Assignee:
            William Maethner
            Reporter:
            Isaac Vetter
            Isaac Vetter
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: