ICEfaces
  1. ICEfaces
  2. ICE-9873

New mobi:viewManager, mobi:view components

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.BETA, 4.0
    • Component/s: MOBI-Components
    • Labels:
      None
    • Environment:
      ICEfaces 4
    • Assignee Priority:
      P1
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      A View Manager component would aim at making standard mobile UIs easier for enterprise developers. The developer would define the contentPanes, which could be nested, their titles, the navigation pattern for different layouts, and the component would create the UI. The component would automatically handle navigation, and would not require the developer to write any backing bean code for navigation, or view switching.

      <mobi:viewManager mobileNavigation="swipe" tabletNavigation="menu" appLabel="My App">
         <mobi:contentPane id="a" title="Page A">
             //content
         </mobi:contentPane>
         <mobi:contentPane id="b" title="Page B">
             //content
         </mobi:contentPane>
         <mobi:contentPane id="b1" title="Page B1" childOf="b">
             //content
         </mobi:contentPane>
          <mobi:contentPane id="c" title="Page C">
             //content
         </mobi:contentPane>
      </mobi:viewManager>

      In a mobile layout set to navigation='swipe' this would generate the following:
      A <-- swipe to--> B <-- swipe to -->C
                                                    <--or click to --> B1

      -------------------------- -------------------------- -------------------------- --------------------------
      | A | | B <B1>| | <back> B1 | | C |
      | | | | | | | |
      | | | | | | | |
      | | | | | | | |
      | | | | | | | |
      ------------------------- ------------------------- ------------------------- -------------------------

      In a mobile layout set to navigation='menu' this would generate the following:

      -------------------------- -------------------------- -------------------------- -------------------------- --------------------------
      | My App | | A | | B <B1>| | <back> B1 | | C |
      |------------------------| | | | | | | | |
      | A > | | | | | | | | |
      | B V | | | | | | | | |
      | B1 > | | | | | | | | |
      | C V | | | | | | | | |
      ------------------------- ------------------------- ------------------------- ------------------------- -------------------------

      In a tablet layout this would generate the following:
      ____________________________________________
      | My App |
      |---------------------------------------------------------------------------|
      | A > | |
      | B V | |
      | B1 > | Current Page |
      | C V | |
      | | |
      | | |
      | | |
      |---------------------------------------------------------------------------|

        Issue Links

          Activity

          Ken Fyten created issue -
          Ken Fyten made changes -
          Field Original Value New Value
          Description The mobi:flipswitch component provides a control that toggles between on and off states (boolean). A View Manager component would aim at making standard mobile UIs easier for enterprise developers. The developer would define the contentPanes, which could be nested, their titles, the navigation pattern for different layouts, and the component would create the UI. The component would automatically handle navigation, and would not require the developer to write any backing bean code for navigation, or view switching.

          <mobi:viewManager mobileNavigation="swipe" tabletNavigation="menu" appLabel="My App">
             <mobi:contentPane id="a" title="Page A">
                 //content
             </mobi:contentPane>
             <mobi:contentPane id="b" title="Page B">
                 //content
             </mobi:contentPane>
             <mobi:contentPane id="b1" title="Page B1" childOf="b">
                 //content
             </mobi:contentPane>
              <mobi:contentPane id="c" title="Page C">
                 //content
             </mobi:contentPane>
          </mobi:viewManager>

          In a mobile layout set to navigation='swipe' this would generate the following:
          A <-- swipe to--> B <-- swipe to -->C
                                                        <--or click to --> B1

          -------------------------- -------------------------- -------------------------- --------------------------
          | A | | B <B1>| | <back> B1 | | C |
          | | | | | | | |
          | | | | | | | |
          | | | | | | | |
          | | | | | | | |
          ------------------------- ------------------------- ------------------------- -------------------------

          In a mobile layout set to navigation='menu' this would generate the following:

          -------------------------- -------------------------- -------------------------- -------------------------- --------------------------
          | My App | | A | | B <B1>| | <back> B1 | | C |
          |------------------------| | | | | | | | |
          | A > | | | | | | | | |
          | B V | | | | | | | | |
          | B1 > | | | | | | | | |
          | C V | | | | | | | | |
          ------------------------- ------------------------- ------------------------- ------------------------- -------------------------

          In a tablet layout this would generate the following:
          ____________________________________________
          | My App |
          |---------------------------------------------------------------------------|
          | A > | |
          | B V | |
          | B1 > | Current Page |
          | C V | |
          | | |
          | | |
          | | |
          |---------------------------------------------------------------------------|
          Component/s MOBI-Components [ 10270 ]
          Component/s ACE-Components [ 10050 ]
          Ken Fyten made changes -
          Link This issue depends on MOBI-342 [ MOBI-342 ]
          Ken Fyten made changes -
          Summary New mobi:viewManager component New mobi:viewManager, mobi:view components
          Ken Fyten made changes -
          Assignee Priority P1 [ 10010 ]
          Arturo Zambrano made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Ken Fyten made changes -
          Fix Version/s 4.0 [ 11382 ]
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Arturo Zambrano
              Reporter:
              Ken Fyten
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: