Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: JIRA Issue macro params updated with additional server info

In response to: 

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-25

Problem

Some modules are dependent on Sencha Touch (mobile/tablet) and others are dependent on ExtJS (desktop). These libraries are fairly large themselves and we do not want both of them to be loaded when deployed on modules that are only going to Touch-only or Desktop-only. 

...

  1. When opening application, we don't want load time to be more than a few seconds.
    1. One fundamental assumption is that the download time for both libraries is too slow. We should verify that this is true.
    2. Is it possible to use PhoneGap to compile a native app, which can include all the code and be installed (thus, launching and running faster)
  2. When using application, our model has a "home screen" where you can choose a module. This home screen includes all possible modules with a link to each (
    Jira Legacy
    serverJIRA (raxaemr.atlassian.net)
    serverId8276eef1-ac20-3511-8661-137e963e10ff
    keyRAXAJSS-118
    ). However, some of these modules are desktop-only or tablet-only.
    1. If on desktop, we might limit to showing only ExtJS modules (and equivalent for tablet).
    2. If on tablet or desktop, we might show all modules (and include their libraries), and realize that the functionality will be subpar for those which weren't intended for the device.
    3. We might show all in the list, but disable some of the icons, or note "PC Only" or "Tablet only" in small letters on the icon.
    4. We might require that all modules have both Desktop and Tablet versions.
  3. Which modules should be accessible when using Tablet? when using Desktop?
    1. User with desktop: If another module only has a Tablet Mode, you should still be able to view it. (Example: in case need to quickly screen someone while using a desktop)

    2. User with tablet: If another module only has Desktop Mode, you should not be able to view it. We don't want to download the heavyweight extJs on a tablet, due to performance and bandwidth concerns. We also think that the experience when using a Desktop Mode from a tablet will have poor UX (page dimensions, button size, interactions don't work nicely, etc).
  4. When using certain widgets, want their functionality shared as widely as posible (e.g. Search widget 
    Jira Legacy
    serverJIRA (raxaemr.atlassian.net)
    serverId8276eef1-ac20-3511-8661-137e963e10ff
    keyRAXAJSS-7
    ). Can this be shared across Sencha and ExtJS, or always specific to one?
    1. Is it possible to create a shared path at a higher directory structure 

...

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-26

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-27

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-28

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-29

Jira Legacy
serverJIRA (raxaemr.atlassian.net)
serverId8276eef1-ac20-3511-8661-137e963e10ff
keyTODO-30