Daniel P H Fox
Daniel P H Fox
Currently, Spring and Tween are two completely separate objects in Fusion, and don't share any code between them. However, both are conceptually special cases of a more general 'follower object'...
As mentioned in this Twitter thread (https://twitter.com/Elttob_/status/1432242081368530949): > [The downside of state objects] is that, when dealing with state objects, you still need to make a case for constants. In...
Currently, state objects are contractually required to disclose dependencies as part of their `:get()` process: ```Lua -- Computed.lua, for example function class:get(asDependency: boolean?): any if asDependency ~= false then useDependency(self)...
As we plan to move Fusion beyond depending on garbage collection for UI, we need to address more structural problems in Fusion which we currently rely on garbage collection to...
Oftentimes the same function will be used for initialising an observer and updating it in response to a change: ```Lua local theValue = Value(5) local function updateFoo() foo.Color = theValue:get()...
Alternate idea to #159 - since we're introducing `unwrap()` in v0.3, users will already have a great consistent way to get the value of any state object. There's no case...
Currently, systems built with Fusion do not generally depend on the previous state of the system, outside of animation primitives such as tweens and springs. While this is generally the...
If we're going ahead with #111, then we'll be changing the behaviour of `:get()` here to explicitly only return a value, without adding any dependencies whatsoever. However, this might not...
There are many cases where Fusion may be used for 3D UI and visualisations. for example placing SurfaceGuis on floating panels for VR games, draggers and adornments, viewport frame contents,...
I was getting some unexpected errors from inside Fusion recently, so I added a check to `setProperty` for nil references in the event of an error. What I found is...