ICEfaces
  1. ICEfaces
  2. ICE-9871

New mobi:dateSpinner component

    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: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 4
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      The mobi:dateSpinner is an input component used for choosing a date.

      Supports both native device date selection components, or optionally its' own date selection UI, consistent on all devices.

        Activity

        Hide
        Arturo Zambrano added a comment -

        Fixed issue #3 at revision 40075, by applying styleClass to root element and style to input element.

        Show
        Arturo Zambrano added a comment - Fixed issue #3 at revision 40075, by applying styleClass to root element and style to input element.
        Hide
        Arturo Zambrano added a comment -

        Fixed issue #4 by adding some logic in encodeClientBehaviors() to avoid rendering the behavior label/key in the behaviors object when there are no non-disabled ajax behaviors for that event.

        Show
        Arturo Zambrano added a comment - Fixed issue #4 by adding some logic in encodeClientBehaviors() to avoid rendering the behavior label/key in the behaviors object when there are no non-disabled ajax behaviors for that event.
        Hide
        Arturo Zambrano added a comment -

        Issue #6 is only due to the fact that the Employee and Note classes do not override the equals() and hashCode() methods with their own implementations, which is a requirement to work with ace:dataTable. So, as soon as those classes have their own equals() and hashCode() methods, things should work fine on ace:dataTable.

        Show
        Arturo Zambrano added a comment - Issue #6 is only due to the fact that the Employee and Note classes do not override the equals() and hashCode() methods with their own implementations, which is a requirement to work with ace:dataTable. So, as soon as those classes have their own equals() and hashCode() methods, things should work fine on ace:dataTable.
        Hide
        Cruz Miraback added a comment -

        ICEfaces4 trunk revision# 40082

        Confirmed issue #1 fixed.
        Confirmed issue #2 fixed. However, when clicking 'Set' the selected date still gets submitted to the server when not using ace:ajax. In this scenario I would expect the value to get set in the input of the component but not sent to the server (like when using ajax disabled=true).
        Confirmed issue #3 fixed.
        Confirmed issue #4 fixed.
        For issue #6 I implemented equals() and hashCode() methods but I'm getting the same results.

        Show
        Cruz Miraback added a comment - ICEfaces4 trunk revision# 40082 Confirmed issue #1 fixed. Confirmed issue #2 fixed. However, when clicking 'Set' the selected date still gets submitted to the server when not using ace:ajax. In this scenario I would expect the value to get set in the input of the component but not sent to the server (like when using ajax disabled=true). Confirmed issue #3 fixed. Confirmed issue #4 fixed. For issue #6 I implemented equals() and hashCode() methods but I'm getting the same results.
        Hide
        Ken Fyten added a comment -

        Remaining issue #6 with nested ace:dataTables has been spun off to ICE-9895.

        Resolved.

        Show
        Ken Fyten added a comment - Remaining issue #6 with nested ace:dataTables has been spun off to ICE-9895 . Resolved.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: