Opened 14 years ago
Closed 14 years ago
#6963 closed task (fixed)
Move dojox.fx.easing into Core
Reported by: | dante | Owned by: | dante |
---|---|---|---|
Priority: | high | Milestone: | 1.2 |
Component: | General | Version: | 1.1.1 |
Keywords: | Cc: | alex | |
Blocked By: | Blocking: |
Description
One really stable and much-used aspect of dojox.fx is the standalone dojox.fx.easing module. I suggest, based on it usage, dojox.fx.easing be moved to dojo.fx.easing. This would involve making a fx/ folder in dojo/, and either an API - shim in dojox, or a blanket update of easing references (mostly across dojox) ...
the only issue I see: some easing functions go "beyond" the endpoint, which if used in some scenario's will cause exceptions in the lesser browsers during onAnimate. (negative marginLeft?) Its not such a problem if we better expose the easing usage and document any potential shortcomings like that.
Attachments (1)
Change History (3)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
+1, assuming we keep an alias in dojox.fx.easing, at least for 1.2. Also, lets make sure we have a dojo.deprecated() message in there.