Clojurians Log v2

@kephale: how's the mesh stuff going?

I'm getting the impression that toxi isn't terribly interested in having collaborators on his library.

Which is a shame, but I can't let that keep me from developing the tools that I need to meet my own needs.

well, it certainly has been a one-man army effort up to this point, so I suspect he has something in mind for his baby, probably even partially driven by the demands from the http://thi.ng workshops he has been giving

i’m under a journal revision deadline at the moment, so i’m still stuck in C++ land with my existing mesh simulations

that should change more around new years when the revisions get sent in

we’ve actually been playing a bit with @eggsyntax cljs-mathbox implementation as well

just to get a faster cycle of iterations during development

a thought that is floating around here is to take a pass at having the cljs-mathbox implement some of the protocols from http://thi.ng, and see how that experience goes

although that is most likely to be for graphing/plotting utilities first

so targeting the geom.viz namespaces first

My current focus is on the general area of "polygon mesh subdivision modeling" with an eye towards learning all the features of Wings3D and MeshLab and implementing similar functionality in Clojure. I'll keep building on the protocols provided by the http://thi.ng geom mesh as I have been. But at some point it might make sense to look at the underlying implementation to see if it can be improved. To the extent that that overlaps with your need for real-time mesh simulation and deformation I'd love to collaborate.

@kephale: ooh, interesting thought!

No hurry on any of this. Just trying to keep everyone that's interested in the loop.

Everything still going smoothly with cljs-mathbox, no hidden pain points as yet?

@eggsyntax: no pains at all, but i admit i’ve been nearly 24/7 on the simulations i’m dealing with

2 of us here are poking at it now though

Cool. Keep me posted :simple_smile:

@meow: btw, did you see http://www.meshlabjs.net/

& if you find any bad choices, I’m likely down to fix ‘em.

yes, i’ll be vocal if i run into anything, but i’m optimistic based on my read throughs

@kephale: haven't seen that before, and the web page won't load for me.

:thumbsup:

@meow: it might be a webgl verison thing, it works in chrome

its, if not all, most of meshlab in javascript

I'm on chrome and do a lot with webgl. Bummer.

i’ve had some slowdowns for meshes with millions of verts

but for more concise meshes its quite comfy

i’m a clojurescript neophyte at the moment, but i can’t help but to wonder if there is a way of using meshlabjs as a dependency

to avoid rewriting the meshops from MeshLab

I can see the code in their github repo.

i definitely need a lot of operations from meshlab, but need to get a better idea about which ones are useful by manually poking around, which is terribly slow

it would be a little annoying that it would restrict to clojurescript usage only

but that wouldn’t be the worst tradeoff

clearly pure clojure meshops are most ideal

I'm learning a lot about mesh ops by writing them myself, plus I usually end up not liking how others have implemented this stuff so I don't mind building it all up from scratch.

I'll have to look at how they structure their meshes and how it relates to the structure and protocols that toxi has defined.

mmm, what i really want though is to screen a handful of meshlab functions sampling a bunch of parameters, but it would be preferable to not have to write the functions that won’t be useful in the long run, etc..

that kind of thing

not really sure what you mean

i already have a bunch of ops from my c++ code to port already : X

so i want to avoid porting functions that i wont use

like vertex sampling for example

only some of those are useful for me, but i dont reallllly know which until i test with a range of sampling parameters

oh, I see

and sure one could write scripts to run meshlab with them

but if we can bind to an existing meshlab implementation and just call from clojure

then phew, all the better

I don't like the meshlab scripting stuff at all.

yes!

I'll look at the js version and see what it looks like.

cool, i’d be interested to hear your take on linking to it

Yep, the new Slack image viewer is way bigger. 😉

@kephale: So the majority of meshlabjs is C++ transcompiled to js

I don't have much interest in working with it.