You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix some flicker that snuck back (use Engine.nextTick instead of .defer)
(not yet; was in some of the .rc releases)
Introduce FView.registerTransition(name, func), which stores the transition
func in FView.transitions[name] and may be used by other parts of this
package and plugins. Func(modifier, done) acts on modifier and calls done when the animation is finished. this will be the fview, if
available.
The special direction="X" (taking a string instead of integer) now works
on reactive updates too. (#170)
Docs: updated Scrollview to reflect reactive properties.
Generally using {{#famousContext}} in <body> these days is considered
safe and reliable. However, as a precaution for weird situations, we now
insert a wrapper view and only roll once FView.ready() is true.
famousIf, previously, was used to maintain the correct position inside
of a sequence. Now, it can be used inside of a regular renderNode too,
and cleans up children when the condition changes (#179)
Speed increase. Do our own materialization of non-Surface templates to
avoid some unnecessary DOM stuff. (And cleaned-up lib/famous.js)
For registerables, add an onDestroy() callback to be fired just before
the fview is completely destroyed.
Add support for watchSize=true on Surfaces. Document Surfaces.
Document pattern to retrigger true-sized Surface size calculations.
(#163)
Registerables: onRenderTree() callback (not used for anything yet)
Views: postRender() callback (was only available for modifiers until now) Surfaces: Template.x.onDocumentDom() callback, but this is now the
default behaviour for .rendered() - so rather use that
Internal: when called with inclusion, store a link to the used template
in fview.template.
FView.from() and FView.fromBlazeView() now return an fview on the
given blazeView if it exists, and not only from it's ancestors.
Surfaces now store a fview.surfaceBlazeView for the blazeView used
to render the Surface's contents.
For Surfaces, Template.x.rendered now runs after the template has
been rendered and added to the document. This is later than before,
but more in line with how Meteor does things and allows for more
intuitive use. E.g. jQuery plugins work better. Note, even though $() will work here now, you should always use this.$() when
possible, for performance. (#192)
Start recording ChangeLog on View pages too (e.g. Surfaces, Views README)
Bugfix: don't try "decode" the id attribute (#100)