Update DOM.md
This commit is contained in:
parent
533a276100
commit
78a7dd0d21
1 changed files with 3 additions and 4 deletions
7
DOM.md
7
DOM.md
|
@ -1,7 +1,6 @@
|
|||
# freactive
|
||||
*pronounced "F-reactive". This library should be considered experimental - it has not been widely tested.*
|
||||
|
||||
|
||||
freactive is a high-performance, pure Clojurescript, declarative DOM library. It uses [hiccup](https://github.com/weavejester/hiccup)-style syntax and Clojure's built-in deref and atom patterns. It is inspired by work done in [reagent](https://github.com/reagent-project/reagent), [om](https://github.com/swannodette/om) and [reflex](https://github.com/lynaghk/reflex) (as well as my experience with desktop GUI frameworks such as QML, JavaFX and WPF). [See it in action](http://aaronc.github.io/freactive/).
|
||||
|
||||
**Goals:**
|
||||
|
@ -72,7 +71,7 @@ When you're observing the example you can view the calculated FPS rate as well a
|
|||
|
||||
Here is the example:
|
||||
|
||||
All of this is done declaritively with only the syntax described above, [easers](#easers) and [transitions](#transitions).
|
||||
All of this is done declaritively with only the syntax described [above](#two-minute-tutorial), [easers](#easers) and [transitions](#transitions).
|
||||
|
||||
Here is the source for the example:
|
||||
|
||||
|
@ -136,11 +135,11 @@ An easer is designed to be used as a dependency in a reactive computation, like
|
|||
easing/quad-in on-complete)}))
|
||||
```
|
||||
|
||||
**Easing functions:** an easing function, `f`, is a function that is designed to take an input `t` parameter that ranges from `0.0` to `1.0` that has the property `(= (f 0) 0)` and `(= (f 1) 1)`. Basically the easer is supposed to smoothly transition from `0` to `1`. The easer, takes care of scaling the values based on `duration` and `from` and `to` values. A selection of easing functions from Dan Kersten's [ominate](https://github.com/danielytics/ominate) (thank you!) is currently included in this library, but this is subject to change.
|
||||
**Easing functions:** an easing function, `f`, is a function that is designed to take an input `t` parameter that ranges from `0.0` to `1.0` that has the property `(= (f 0) 0)` and `(= (f 1) 1)`. Basically the easing function is supposed to smoothly transition from `0` to `1`. The easer itself takes care of properly scaling the values based on `duration` and `from` and `to` values. A selection of easing functions from Dan Kersten's [ominate](https://github.com/danielytics/ominate) (thank you!) is currently included in this library, but this is subject to change.
|
||||
|
||||
**Optional `from` parameter:** the optional `from` parameter to `start-easing!` has a special behavior - if the current value of the easer is different from `from`, the `duration` of easing will be adjusted (linearly for now) based on the difference bettween `from` and the current value. This is to keep the speed of easing somewhat consistent. If you, don't want this behavior and always want the same `duration` regardless of the current value of the easer, don't specify a `from` value.
|
||||
|
||||
**Interupting easings in progress:** if `start-easing!` is called on an easer that is already in an easing transition that hasn't completed, it is equivalent to cancelling the current easing and sending the easer in a different direction starting from the current value. If there was on `on-complete` callback to the easing that was in progress it won't be called and is effectively "cancelled".
|
||||
**Interupting in progress easings:** if `start-easing!` is called on an easer that is already in an easing transition that hasn't completed, it is equivalent to cancelling the current easing and sending the easer in a different direction starting from the current value. If there was on `on-complete` callback to the easing that was in progress it won't be called and is effectively "cancelled".
|
||||
|
||||
## Items View
|
||||
|
||||
|
|
Loading…
Reference in a new issue