ICEmobile
  1. ICEmobile
  2. MOBI-400

container progress bar / upload notifier should be moved

          Details

          • Type: Bug Bug
          • Status: Resolved
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.1 Final
          • Fix Version/s: 1.3 Beta
          • Component/s: Containers
          • Labels:
            None
          • Environment:
            n/a

            Description


            The positioning of the container's svg progress icon/bar is problematic. Being placed in the top right corner prevents developers from using a button or link in the top right hand corner, which is a common mobile layout pattern.

              Activity

              Ascending order - Click to sort in descending order
              Migration created issue -
              Migration made changes -
              Field Original Value New Value
              Reporter Migration [ remote ] User Philip.breau [ philip.breau ]
              Ted Goddard made changes -
              Fix Version/s 1.3 Beta [ 10373 ]
              Hide
              Permalink
              Ted Goddard added a comment -

              Worth considering for 1.3 if time permits.

              Show
              Ted Goddard added a comment - Worth considering for 1.3 if time permits.
              Hide
              Permalink
              Steve Maryka added a comment -

              The attached APK contains a prototype of a status bar overlay for Android container. It seems pretty effective, but there are some obvious questions:

              Where should we put it? Should its position be configurable from the page?

              I tried making it disappear after the page loaded, but that seemed more distracting.

              I have not checked anything in at this point, as we should decide where to go with this.

              Show
              Steve Maryka added a comment - The attached APK contains a prototype of a status bar overlay for Android container. It seems pretty effective, but there are some obvious questions: Where should we put it? Should its position be configurable from the page? I tried making it disappear after the page loaded, but that seemed more distracting. I have not checked anything in at this point, as we should decide where to go with this.
              Steve Maryka made changes -
              Attachment ICEmobileContainer-debug.apk [ 15780 ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #34370 Thu Apr 11 16:39:37 MDT 2013 steve.maryka mobi-400: Added new overlay progress bar to android container. Removed old JS-based progress wheel, and preferences-based progress dialog.
              Files Changed
              Commit graph MODIFY /icemobile/trunk/icemobile/client/android/container/res/xml/preferences.xml
              Commit graph ADD /icemobile/trunk/icemobile/client/android/integration/util/src/org/icemobile/client/android/util/SubmitProgressListener.java
              Commit graph MODIFY /icemobile/trunk/icemobile/client/android/integration/util/src/org/icemobile/client/android/util/UtilInterface.java
              Commit graph MODIFY /icemobile/trunk/icemobile/client/android/container/assets/icefaces/native-interface.js
              Commit graph ADD /icemobile/trunk/icemobile/client/android/container/res/drawable/blue_progress.xml
              Commit graph ADD /icemobile/trunk/icemobile/client/android/container/res/values/colors.xml
              Commit graph ADD /icemobile/trunk/icemobile/client/android/container/res/drawable
              Commit graph MODIFY /icemobile/trunk/icemobile/client/android/container/src/org/icemobile/client/android/ICEmobileContainer.java
              Commit graph MODIFY /icemobile/trunk/icemobile/client/android/container/res/layout/main.xml
              Hide
              Permalink
              Steve Maryka added a comment -

              Android implementation complete, so passing along for iOS work. Android uses an overlay progress bar at the bottom of the header area to show progress for all network interactions.

              Changes are checked in to r34370.

              Show
              Steve Maryka added a comment - Android implementation complete, so passing along for iOS work. Android uses an overlay progress bar at the bottom of the header area to show progress for all network interactions. Changes are checked in to r34370.
              Steve Maryka made changes -
              Assignee Steve Maryka [ steve.maryka ] Ted Goddard [ ted.goddard ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #34408 Mon Apr 15 14:08:33 MDT 2013 ted.goddard progress bar for iOS container (MOBI-400)
              Files Changed
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/iPad/MainWindow_iPad.xib
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/iPhone/MainWindow_iPhone.xib
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/ICEmobile-SX/en.lproj/ViewController_iPhone.xib
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/Container/MainViewController.mm
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/Container/MainViewController.h
              Commit graph MODIFY /icemobile/trunk/icemobile/client/ios/icemobile/Container/native-interface.js
              Hide
              Permalink
              Ted Goddard added a comment -

              iOS implementation is complete, making use of a thin progress bar just below the status icons. To override this implementation and customize via ice.progress, return true from a custom ice.progress implementation.

              Show
              Ted Goddard added a comment - iOS implementation is complete, making use of a thin progress bar just below the status icons. To override this implementation and customize via ice.progress, return true from a custom ice.progress implementation.
              Ted Goddard made changes -
              Assignee Ted Goddard [ ted.goddard ] Greg Dick [ greg.dick ]
              Hide
              Permalink
              Greg Dick added a comment -

              Blackberry OS6 version will not be completed.

              • Navigation and connection management in the existing container are handled through the BrowserFieldConnectionManager and BrowserFieldCookieManager classes. These objects do not expose any IO stream for the purposes of duplicating the Android writing or reading input stream.
              • It is possible to duplicate this structure if you take over handling the socket connections, but that exposes you to the inane world of Blackberry connection management which is beyond the scope of this container.

              A document describing this world can be found here: http://supportforums.blackberry.com/t5/Java-Development/Different-ways-to-make-an-HTTP-or-socket-connection/ta-p/445879

              • There is a BrowserField onDocumentProgress callback, but it is poorly behaved in an Ajax environment. Progress events are received, but no onDocumentLoaded event to conclude the download is received. If an updated region contains multiple resources, the progress events are impossible to consolidate into any meaningful 'update'
              Show
              Greg Dick added a comment - Blackberry OS6 version will not be completed. Navigation and connection management in the existing container are handled through the BrowserFieldConnectionManager and BrowserFieldCookieManager classes. These objects do not expose any IO stream for the purposes of duplicating the Android writing or reading input stream. It is possible to duplicate this structure if you take over handling the socket connections, but that exposes you to the inane world of Blackberry connection management which is beyond the scope of this container. A document describing this world can be found here: http://supportforums.blackberry.com/t5/Java-Development/Different-ways-to-make-an-HTTP-or-socket-connection/ta-p/445879 There is a BrowserField onDocumentProgress callback, but it is poorly behaved in an Ajax environment. Progress events are received, but no onDocumentLoaded event to conclude the download is received. If an updated region contains multiple resources, the progress events are impossible to consolidate into any meaningful 'update'
              Greg Dick made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]

                People

                • Assignee:
                  Greg Dick
                  Reporter:
                  Philip Breau
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: