Solve transition and generic client-side problems. (MGNLUI-1200)

[MGNLUI-1204] The transition delegates are complex and hard to trace and understand. Created: 25/Apr/13  Updated: 29/Apr/13  Resolved: 29/Apr/13

Status: Closed
Project: Magnolia UI
Component/s: design
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Sub-task Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: apiteam
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:
Sprint: Iteration 2013-16, Iteration 2013-17

 Description   

Transition delegates that are used to handle the viewport and their content animations are complex due to non-obvious condition logic and callback hell produced by usage of raw JQueryWrapper.



 Comments   
Comment by Espen Jervidalo [ 29/Apr/13 ]

info.magnolia.ui.vaadin.gwt.client.magnoliashell.viewport.animation.JQueryAnimation#JQueryAnimation
creating callbacks in this class and setting them in the constructor is not needed, they are already instantiated in the info.magnolia.ui.vaadin.gwt.client.jquerywrapper.AnimationSettings
delegate the adding of callbacks to the settings.addCallback()

info.magnolia.ui.vaadin.gwt.client.magnoliashell.viewport.AppsTransitionDelegate#removeWidget
info.magnolia.ui.vaadin.gwt.client.magnoliashell.viewport.AppsTransitionDelegate#setVisibleChild
use constants for the 500 ms passed into the run methods

Generated at Mon Feb 12 08:44:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.