Re: Only one sc.texture.rotate: SC Texture Rotation objects

This is an interesting challenge for Max.  The scaled coordinates is interesting — after all, jit.matrix objects cast cell values  0..255 to 0.0..1.0.   But at this point it seems like we are doing Live/Cycling74’s job.  If I set up a conversation with Live / Zicarelli, can one of Todd or Brandon carry it on?  Maybe it’s time to show this to Luke first for an opinion.  He may simply ignore matrices and just go to GL, but then again he doesn’t seem to teach his students  very much (Mas, Swift) media processing compared to DC/

 I don’t know how we can get around the differences that Todd points out without re-writing every sc.texture object with some pre-processor…— which seems infeasible, or prohibitively costly in execution.

Mathematica uses its elegant pattern-rewrite  (LISP-like) , late-binding semantics to define objects by concept rather than implementation.  For example one big different between Maple and Mathematica is that 

Maple has ugly and confusing synonyms based on implementation rather than function, e.g. sin(x) was a numerical operator vs Sin)x) was symbolic (could be symbolically differentiated or integrated.).   In  Mathematica, we have 
Sin(x)
and an operator N[_] which tries to numerically evaluate down the parse tree whatever expression is inside it.  E.g. 

Sin[x] ~ Sin(x)
N[Sin[x]]  ~  sin(x)

Good language design relieves programmer having to keep track of numerical efficiency implementations at the function or variables level.


On Feb 27, 2019, at 2:40 PM, Todd Ingalls <TestCase@asu.edu> wrote:

i think instead of simple we could use another term but it is not possible to decide which one to use  based on arguments. we could put it in one and have  a switched called accelerated or something but not sure how confusing that would be 




Todd Ingalls
Research Professor
Assistant Director
School of Arts, Media and Engineering - ame.asu.edu
Synthesis Center - synthesiscenter.net
Arizona State University
Stauffer B 245
ame.asu.edu/faculty/todd

On Feb 27, 2019, at 12:20 PM, sxw asu <sxwasu@gmail.com> wrote:

In general can we please name objects
using full words (no abbreviations!)

and with descriptions of what they do.

Also instead of * and *.simple

can we please fold them into one object named
sc.texture.rotate

let’s  NOT clutter up our name space w synonyms.

If you insist on optimization, find a way  hide both versions under the hood and invoke the appropriate version by scanning the arguments
typed in by the programmer.

Xin Wei