Hi Marco, yes unfortunately there are only 24 hours in a day. I have to be careful in what I try to accomplish with MoI so that I can make it be a high quality tool. In general things that have a high amount of support time required are less practical for me to focus on.
Marco reminded me of another node that would have great utility: the LassoSel Node.
He has already done much of the coding required in his "Lasso Select and SelectCurveByContainer".
It can be found in this thread including PDF instructions for installation & operation: http://moi3d.com/forum/index.php?webtag=MOI&msg=8830.1
In essence, any planar shape (circle, polygon or closed curve) would serve as a selection mask.
It would ideally have 2 options:"overlap" (select all objects wholly within the mask only) and "overlay" (select all objects wholly & partially within the mask, like in image below).
"Hi Marco, yes unfortunately there are only 24 hours in a day..."
I understand and respect your choice because I know very well the hard life of a software developer and of a "one man" company :)
And unfortunately this is a big limitation in some situation.
It's a situation that have its strength and weakness.
I know very well...it's part of my life too.
I only wanted to say that it's really a pity that a MAGNIFICENT and AMAZING duo like Moi and Max's scripts (above all Node Editor) can't live a shared "story".
I always thought that bringing Node Editor and all Max's SUPERB scripts into the CORE of Moi it could have been a GAME CHANGER for Moi.
Something that could have been RAISED your excellent Moi to a greater, very unique, level.
I know that probably this situation never will and this is unfortunate for all Moi's community.
But , unfortunately or...fortunately, it depends on point of view :) as I've said some times here during the last two years, for the moment, the funny days when I had some good time to devote to Moi are gone.
From 2018 I never had really more enough spare free time to write something serious for Moi's scripting environment.
I'm always engaged in other different things regarding my "developer life" :)
But you reminds me the funny days when I had TONS of ideas for writing some cool and unique stuff, like for example the "LASSO" script (for what I know I was the very first to do a real (almost) working implementation of that), the "COMMAND FINDER", the "HOLES FINDER", and other useful stuff that I wanted to bring into Moi.
All the code I've written, although working, was nothing more than a "provocation" for someone more skilled than me in Javascript and Math related things, to bring some new cool stuff into Moi.
I had many other ideas into my mind that only waited to be translated into actual working code, but I never had time to do that and also never had the "math science" into my veins :)
Anyway...also I MISSED almost all the code I've written :)
I've found here and there only some stuff, for example the original post I've written related to the "final" version of the LASSO tool.
> I only wanted to say that it's really a pity that a MAGNIFICENT and AMAZING duo like Moi
> and Max's scripts (above all Node Editor) can't live a shared "story".
>
> I always thought that bringing Node Editor and all Max's SUPERB scripts into the CORE of Moi
> it could have been a GAME CHANGER for Moi.
>
> Something that could have been RAISED your excellent Moi to a greater, very unique, level.
Focusing my very limited time heavily on the node editor would be cool but it would probably be a product ending strategic error.
The reality is that the end result of what you're describing would not be very unique since Rhino/Grasshopper already exists in that role and has far more momentum and resources behind it than what I would be able to muster.
That's not meant to take anything away from Max's work, it's amazing what he has been able to accomplish and it's really cool that it's available. It's just not really feasible for me to focus on it myself.
Thank you for the project request. I am still feeling my way around the NE code. More practice is required before taking on more challenging nodes like the subdiv script. Currently working on a new node, but it is too early to publish any beta's. Hint: I am having difficulty placing an image on a node canvas. Yes, I have read all the API's and the basic Javascripts on how to do it. But Elephant is a different animal... :-).
"The reality is that the end result of what you're describing would not be very unique since Rhino/Grasshopper already exists in that role and has far more momentum and resources behind it than what I would be able to muster."
I understand your point of view. Clearly.
It's true...Rhino/Grasshopper is a super STRONG duo, but I anyway thing that Moi + Max's Node Editor with their "lightness" and easy of use could have been a great alternative.
Anyway...I don't want to bother you with these considerations.
I respect your choice...it's your job and you know what you need and what is good for you and your product.
I'm not sure if NodeEditor should be a default part of MoI, because IMHO most of MoI users NodeEditor don't use so often and I like that such excellent tool as like NE is, can be part of MoI as an "accessories", as well as all excellent scripts that are created by all MoI community. This is a marvellous example of people cooperation across the world.
I think that to MoI users would suit first more intuitive "grouping" instead of "style way" together with some form of primitive instancing like "copy/paste with adequate orientation of changed parts with same part name". In other words if I modified one part (solid, curve), so rest of parts with same name would be modified too with their own orientation in model. It would be great to have check box: "modify rest parts" in info panel :-)
In any case I respect for amazing work on nodes from James, Karsten and other Node experts.
I would like to know if it is possible to create node which respects law of reflection of light. It means to have point/flat light source (solid) with rays (curves) as an input and curved surface - reflector (rotate conic curve) with Rho as a variable. Rays impacted of surface would be reflected to the detector (plane) in specific distance. This would be very nice educative tool. 2D would be enough :-)
Thank you for the links. There is much to learn from all the code available. It might be a file security issue that is preventing the Base64 conversion. Looks like Max ran into the same issue four years ago. The code looks right, but nothing happens.
LassoSel.jpg
