nope nope nope is it "then" in written matrix order (A * B) or in transformation order ("apply A first then B", i.e. B * A)
-
-
Replying to @ManishEarth
imho reading .then() as anything but transformation order doesn't make much sense- the abstraction it implies we're working with is transformations not matrices
1 reply 0 retweets 1 like -
Replying to @XMPPwocky
Until you start using the transforms library as a matrix library (since there's no need to have a different matrix type) and have variables named `matrix`
1 reply 0 retweets 0 likes -
Replying to @ManishEarth
maybe, but I still feel like I'd read horse_matrix.then(bee_matrix).then(squirrel_matrix) as producing a matrix representing "transform by horse, then bee, then squirrel". But obviously if you disagree there exists a person for whom this isn't true :P
1 reply 0 retweets 1 like -
-
Replying to @Gankra_ @XMPPwocky
.PreScale has the same problem as .pre_mul, there are two possible ways of reading it (as an active or passive sentence) furthermore the connotation with pre/post multiplication of matrices further confuses things
1 reply 0 retweets 0 likes -
Replying to @ManishEarth @XMPPwocky
if you've been writing code with this for a while it's fine because the assumptions ("we never talk in terms of matrices") are implicit but as someone who has only dabbled in Firefox graphics code, this shit confused me every. time.
1 reply 0 retweets 0 likes -
I’m on the gfx team-is and I prefer to think in terms of matrices?
1 reply 0 retweets 1 like
“team-ish”, damn autocorrect
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.