Details

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

      Description

      The Scan component captures a barcode or QR code value by scanning the barcode using the mobile device camera.

      ** Only supported on mobile devices supported by the native BridgeIt app. **

        Activity

        Hide
        Cruz Miraback added a comment - - edited

        ICEfaces4 revision# 40103 Test Results
        Test app located at: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/scan

        1) When disabled=true the scan button can still be clicked on and the QR code scanned, however, the QR code value cannot be submitted. Just wanted to check if this is correct behaviour.

        2) style and styleClass attributes are not getting applied to the component

        3) tabindex attribute is not functioning (probably not important since it's a mobile component)

        4) The button doesn't change to it's captured message label after scanning a QR code - only after there is a submit on the page. Furthermore, the captured message label isn't displayed at all when the component is inside dataTables or ui:repeats.

        5) The value attribute is missing from the tlddoc.

        Show
        Cruz Miraback added a comment - - edited ICEfaces4 revision# 40103 Test Results Test app located at: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/scan 1) When disabled=true the scan button can still be clicked on and the QR code scanned, however, the QR code value cannot be submitted. Just wanted to check if this is correct behaviour. 2) style and styleClass attributes are not getting applied to the component 3) tabindex attribute is not functioning (probably not important since it's a mobile component) 4) The button doesn't change to it's captured message label after scanning a QR code - only after there is a submit on the page. Furthermore, the captured message label isn't displayed at all when the component is inside dataTables or ui:repeats. 5) The value attribute is missing from the tlddoc.
        Hide
        Arturo Zambrano added a comment -

        Committed fixes for issues 1, 2, 3, and 5 at revision 40305.

        I couldn't reproduce issue #4 on my device. The captured label always changed after scanning a qr code, even when inside tables and ui:repeats.

        Show
        Arturo Zambrano added a comment - Committed fixes for issues 1, 2, 3, and 5 at revision 40305. I couldn't reproduce issue #4 on my device. The captured label always changed after scanning a qr code, even when inside tables and ui:repeats.
        Hide
        Liana Munroe added a comment -

        Button text changes as expected but now the submitted qrCode does not return its value.
        See test application - mobi:scan inside ui:repeat
        http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/scan.

        Scan a qrCode and submit. Value does not update.

        Show
        Liana Munroe added a comment - Button text changes as expected but now the submitted qrCode does not return its value. See test application - mobi:scan inside ui:repeat http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/scan . Scan a qrCode and submit. Value does not update.
        Hide
        Arturo Zambrano added a comment -

        r41428: changed mobi:scan component superclass to UIInput (from UIComponentBase), as it was expected by other parts of the code, in order to properly support processing multiple inputs in iterative containers.

        This fixes the issue in the comment above.

        Show
        Arturo Zambrano added a comment - r41428: changed mobi:scan component superclass to UIInput (from UIComponentBase), as it was expected by other parts of the code, in order to properly support processing multiple inputs in iterative containers. This fixes the issue in the comment above.
        Hide
        Ken Fyten added a comment -

        Re-opened to add support for an optional "fallback" facet that will be rendered by the component if the BridgeIt app. cannot be used, either due to running on an unsupported platform (such as desktop OS), or the BridgeIt app. not being installed on the device.

        Show
        Ken Fyten added a comment - Re-opened to add support for an optional "fallback" facet that will be rendered by the component if the BridgeIt app. cannot be used, either due to running on an unsupported platform (such as desktop OS), or the BridgeIt app. not being installed on the device.
        Hide
        Arturo Zambrano added a comment -

        Added fallback facet to component at revision 41596.

        Show
        Arturo Zambrano added a comment - Added fallback facet to component at revision 41596.
        Hide
        Liana Munroe added a comment -

        Verified for Issues 1, 2, 3 and 5 from description, and fallback facet. Icefaces 4 trunk r41775. Tomcat 7, FF 30, Chrome 35, IE 11, ios 7 and android 4.1.1.
        Issue 4 has been spun off to a new JIRA - ICE-10126.

        Show
        Liana Munroe added a comment - Verified for Issues 1, 2, 3 and 5 from description, and fallback facet. Icefaces 4 trunk r41775. Tomcat 7, FF 30, Chrome 35, IE 11, ios 7 and android 4.1.1. Issue 4 has been spun off to a new JIRA - ICE-10126 .
        Hide
        Arturo Zambrano added a comment -

        r41782: modified fallback approach to determine in the client whether to display fallback contents.

        Note: the HTML structure of the component changed, so it might be necessary to modify existing tests.

        Show
        Arturo Zambrano added a comment - r41782: modified fallback approach to determine in the client whether to display fallback contents. Note: the HTML structure of the component changed, so it might be necessary to modify existing tests.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: