Releases: Adasha/proximity-effect
Releases · Adasha/proximity-effect
The nearly serious release
- Developed event model with
ready,redrawandreflowevents - Improved extended syntax to be more flexible (slight change to API as a result)
nearandfarargs inaddEffectcan take an object with extra parameters- Added / made public
getNodeDatamethod - Internal improvements give greater flexibility and plays nicer with other instances
- Squashed bugs, obviously
First beta release
- API stuff - hasEffect() & removeEffect()
- target property works properly
- Jitter not recalculated every time offsetX or offsetY is changed
- Multiple ProximityEffects can be applied to the same nodes, but will override repeated style rules for now.
- Internal architecture improvements
r3
Minor release to sync with npm publication. Not meant for production, but it's hardly going to screw much up if you do.
A few additions:
- Basic event model ('redraw' on each update)
- Rudimentary API efforts (don't get too attached)
- Simplified constructor
- Can optionally track arbitrary page element instead of mouse
Issues
- Uses JS features not supported in some browsers
- Tracking loses it in certain browsers under certain setups
- Gets very slow when working with sufficient elements
2nd public release
Updated version number to reflect history of project. API still not locked.
Lots of new features:
- Over 20 built-in effects
- Can optionally add any CSS rule using extended syntax
- Global and local offset properties
- Jitter property
- Invert property
- Direction property
- Accuracy property for performance boost
- Now using proper workflows like a real developer
- plus some other tweaks I've forgotten
Known issues:
- Elements can disappear if transitioned off-screen
- Accuracy not quite working as intended
- Resizing page breaks centres
- Slows down dramatically when elements>100 (Chrome is smoothest)
First public alpha
This is the first public alpha release. It has fully implemented effect handling but is lacking trigger types and some other intended features. Also bugs, probably. The API is not yet locked down and there is no proper documentation.