Or we abandon ship on the DSL idea and make functions for all of this stuff
var c = cube(10);
c.edges().lines().sort(function(a, b) {
return a.x1() < b.x1() ? 1 : -1;
});
or something like that. In other words, allow the api to be written in javascript
this might actually have the potential to break batching in it's current form. Mostly because selection can be done at any point in the process against any object in the scene. So dependency tracking is a must to ensure the scene is ready before running the selection.
So this is going to have to start as a RFC to define the api for this
My initial thought is a sort of spin on http://parametricparts.com/docs/selectors.html#selector-reference although the DSL proposed there could probably be expanded on.
Or we abandon ship on the DSL idea and make functions for all of this stuff
or something like that. In other words, allow the api to be written in javascript
this might actually have the potential to break batching in it's current form. Mostly because selection can be done at any point in the process against any object in the scene. So dependency tracking is a must to ensure the scene is ready before running the selection.