the exe usage in plugins is for non-gpl code a proven way to stay compliant with GPL code. They went so far (and take the rules about gpl serious) to even host the exe and GPL code on different servers. Another method which is also popular is to build custom Blender builds which indeed would talk to a local server. Octane…
Mostly, yeah. Only the 'More features' page falls into the previous levels of inadequacy. Is that the new format, or is it just for the summer coding project?
Not yet, it's currently referencing a hard coded blend path + materlal names + world name. I'll need to somehow make that customizeable if I want to release it.
Hi @Peris, really great tool ! Why not use a github account ? More simply to update the code and share it. I'm try it this week, thanks for your job :) .
The issue of whether Blender add-ons(or any other GPL work) constitute a derivative work is not as clear-cut as you make it out to be. Some argue that dynamically linked libraries are okay, as long as they don't contain source code from the original work. Some would say it doesn't even matter, and that things like plugins…
@PolyHertz, No worries, mate. They changed the UI and added BMesh because the software couldn't progress without the changes. The UI was cramped and the old mesh code was 15 years old. ;)