On 3/5/14, 5:14, Dima Pasechnik wrote:
nowadays these things are normally done using higher level interfaces to WebGL,
such as tree.js
Do you mean three.js?
Just FYI, we are developing a low-level three.js<->python bridge that we
plan to integrate into the sage 3d plotting system. Our (rough) work is
here: https://github.com/jasongrout/pythreejs, and I've been posting
examples to the sage-cell google group.
Regardless of whether you use pythree.js or not, I think using the
IPython comm/widget architecture would maybe be a good idea---changes to
the knot editor could easily be reflected in the python world, and vice
versa.
Thanks,
Jason
--
You received this message because you are subscribed to the Google Groups
"sage-gsoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-gsoc.
For more options, visit https://groups.google.com/groups/opt_out.
