Couple of questions about slalom HOT 1 OPEN

Hi!

1. I wanted to have multiple manipulators for scale/rotate/etc since there are multiple touch points. I'm not sure if it's possible to express the constraints for that (because the solver probably needs to figure out euclidian distance which is obviously non-linear from touch points).

If you look at the source to createManipulator then you'll see it's a fairly simple helper function. Currently Manipulator understands the Hammer.js pan event stream, but it'd be OK to actually pull that out into the createManipulator helper. Then we could have other variants of createManipulator for handling some of the multitouch gestures you mention, since I don't think it can be done with linear constraints.

1. Yup, Box is the current (incredibly minimal) binding between constrained variables and the DOM. You can bind any property in the same way, it's just glue code between Cassowary and DOM (and so it'd be completely replaced for any native port, or for targeting geometry in a webgl app, etc).
2. It'll be something like telling a Manipulator to go to a given value, and then the Manipulator will create an animation using some physics simulation.
3. Interesting! I haven't used angular before (I've used Vue which does a similar cross-cutting via directives). The piece I'm worried about it how it interacts with existing CSS layout, since Slalom/Cassowary operate in a global coordinate space whereas "position absolute" is a more traditional parent-relative/local setup.

Thanks for writing these questions/ideas up. I think Slalom is going to be pretty fun for a while as these issues get figured out!

from slalom.