ICEfaces
  1. ICEfaces
  2. ICE-7208

Re-implement ace:animation using jQuery Effect component

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 2.1-Beta, 3.0
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            ICEfaces 2.1, ace:animation component
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration

            Description

            To provide a more robust animation / effect capability we will be re-implementing the ace:animation component using the jQuery effect library.

            Need to keep ace:animation as backwards compatible as possible. However, dropping support for predefined custom effect types is okay. Instead, we will just use the simpler approach offered by jquery effects going forward.

              Issue Links

              blocks

              Task - A task that needs to be done. ICE-7176 Revert ace: library to YUI 2.8.x library only (remove YUI 3.x dependencies)

              • Major - Major loss of function.
              • Closed

              Improvement - An improvement or enhancement to an existing feature or task. ICE-6961 Re-enable animations for ace:tabSet

              • Major - Major loss of function.
              • Closed

                Activity

                Hide
                Permalink
                Arturo Zambrano added a comment -

                Committed major changes at revision 25579.

                Basically, the re-implementation is made. The only thing missing at the moment is support for the tab transition event. All the standard jQuery-ui effects are now supported, as well as arbitrary animations, using the same API.

                It seems that the initial aim of the animation framework was to support custom, non-standard events. The only place where we ended up using this framework was in the TabSet component, with the custom 'transition' event.

                Adding support for custom events will take additional effort. Most of the code of the animation framework has to do with supporting custom events, specifically the TabSet 'transition' event. This is one of those cases where 20% of the code solves 80% of the cases, and 80% of the code solves the remaining 20% of the cases.

                Show
                Arturo Zambrano added a comment - Committed major changes at revision 25579. Basically, the re-implementation is made. The only thing missing at the moment is support for the tab transition event. All the standard jQuery-ui effects are now supported, as well as arbitrary animations, using the same API. It seems that the initial aim of the animation framework was to support custom, non-standard events. The only place where we ended up using this framework was in the TabSet component, with the custom 'transition' event. Adding support for custom events will take additional effort. Most of the code of the animation framework has to do with supporting custom events, specifically the TabSet 'transition' event. This is one of those cases where 20% of the code solves 80% of the cases, and 80% of the code solves the remaining 20% of the cases.

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: