Full Version: V5 beta Sep-17-2025 available now (Sticky)

Show messages:  1-10  …  31-50  51-70  71-90  91-104

Hi Marco, welcome back!

re:
> 1. Do you have an estimated release date for the official V5, and what will the upgrade price be from V4?

I don't have a specific date set yet but hopefully pretty soon.

Upgrade price is expected to be the same as previous version upgrades, which is $100.


> 2. Where can I find complete and up-to-date API documentation for Moi? I’m especially interested
> in the JavaScript interface, as I’d like to experiment with developing some new scripts.

There is not any official documentation for MOI scripting available, but there is some collected by users here:
https://moi3d.com/wiki/Scripting


> 3. What are the main differences in Moi when using the “ACIS” libraries versus “Solid++” for
> creating fillets and chamfers?

Mostly that the ACIS libraries are far more robust and handle many cases that fail with Solids++.

- Michael

---

> I don't have a specific date set yet but hopefully pretty soon.

Approaching this question from a different angle: the current build expires in 4 weeks. Do you estimate that were would be a period where we have to revert back to the v4 while the v5 release is shaping up after expiration, or would there be a new build (even just an extension of the expiration date) to bridge the gap?

---

Hi summarity, I will make a new v5 beta build with an extended expiration soon. I'll make sure that there is a v5 beta that overlaps the v5 release.

- Michael

---

Thanks Micheal!

A separate question:

I'm working on a few plugins targeted at v5. Are there plans to update the embedded JS/web engine? AFAICT MoI 5 is using QtWebKit, which works, but has been deprecated for about 7 years and replaced by QtWebEngine. There was a fork for a while at qtwebkit/qtwebkit, which was abandoned 3 years ago, then MoveableInk picked up a new fork at https://github.com/movableink/webkit - no idea if this would be a viable upgrade path compared to moving to QtWebEngine.

This leads to some friction trying to use fairly standard development tools, e.g. TypeScript targeting ES6, even targeting very early 2016-ish syntax or styles using CSS grids or flexbox features which were standardized shortly after the cutoff when QtWebKit development ceased.

This is on macOS, so I don't know if this is different for the Windows builds.

---

Ok. Thanks Michael.

You wrote: "There is not any official documentation for MOI scripting available, but there is some collected by users here: https://moi3d.com/wiki/Scripting"

Thanks for your reply, Michael, I appreciate it :)

Alright, noted :)
I was hoping though that, as the developer of Moi, and therefore the person who knows the API specifications and the JavaScript interface better than anyone else, you might be able to provide some official documentation for these APIs.

I’m asking because, as a software developer myself, I think you can understand that this is a pretty reasonable request. When it comes to API specifications, there’s nothing worse than not knowing where to find them, or having to rely on unofficial documentation put together by various users, without any intention of disrespecting those who contributed to the scripting guide you mentioned.

Would it be possible for you to put together a complete and official documentation of Moi’s APIs and its JavaScript interface? I believe it could really be in the best interest of Moi and its community :)

Let me know, thanks!

---

Hi Marco,

re:
> I’m asking because, as a software developer myself, I think you can understand
> that this is a pretty reasonable request.

It would be if I had been marketing the script API as a core feature of the program.

But I have not done that.


> Would it be possible for you to put together a complete and official
> documentation of Moi’s APIs and its JavaScript interface?

No, it is not possible to generate complete and official documentation without expending a large amount of time and effort.

- Michael

---

Hi summarity,

re:
> Are there plans to update the embedded JS/web engine?

Not currently. That would probably also need to update Qt as well. That's a lot of work invovled and at the end of it there would be nothing gained by the average non-programmer MOI user. So it's difficult to justify scheduling that.


> styles using CSS grids or flexbox features which were standardized shortly after the cutoff when QtWebKit development ceased.

What are the flexbox features that you're missing?

= Michael

---

Hi Michael, and thanks for your reply.

After reading it, I’d just like to add one question and one consideration, and please believe me, I’m saying this with complete sincerity and without any hidden agenda or intention to start unnecessary debate.

My question is whether you’re genuinely interested in seeing Moi evolve from a scripting perspective, including more or less advanced scripts that could continue to be developed by Moi users, or at least by those who have some programming experience.

I’m asking because I’ve never heard of a software creator who provides APIs for users to develop scripts, but at the same time says that it’s not possible to provide documentation for those same APIs.

Without an authoritative source, like documentation written by the API creator, how is it possible to write high quality scripts for Moi? If people can only rely on the well intentioned documentation efforts of individual users, it’s clear that the result will always be partial and potentially inaccurate documentation.

I hope you don’t mind me saying this, Michael, but it does seem at least somewhat unusual that you, as the creator of Moi, would choose not to provide official API documentation.

At that point, it might make more sense to remove the API interface altogether and not allow anyone to write scripts or plugins for your software, rather than effectively forcing developers to work blindly, relying on one unofficial guide or another.

I hope I’ve explained myself clearly, and above all without coming across as disrespectful.

Take care, and I look forward to your reply.

All the best.

---

Hi Marco, the primary reason why MOI has a script API is to make a flexible environment that helps me to implement MOI and to help me create plugins for people with specialized tasks.


You wrote:
> My question is whether you’re genuinely interested in seeing Moi evolve from a scripting perspective,

I am interested in that but it's a low priority because that is outside of MOI's primary focus area.

The MOI home page says: "Streamlined UI", "Fast & fluid workflow", "Powerful yet easy to use".

Please consider that and then imagine adding "Complete and up-to-date API documentation for JavaScript programming" to that list, does that really seem to belong with the others?

- Michael

---

Hi Michael,

First of all, thank you for your reply, it was thorough and convincing. I completely understand your point of view as both a developer and an independent entrepreneur working on the Moi 3D project. These are business considerations that I fully respect.

Let me ask just one final question regarding the API topic. As always, this is a genuine question, I never ask questions, or “fake” questions, just to stir up debate or anything like that :)

Since there is no official documentation written by you for Moi’s APIs and its JavaScript interface, on what basis and how were some users able to write those partial API documentation pages for Moi? I’m referring to the web pages you mentioned in one of your previous replies.

How were they able to create that documentation, even if only partial, if you didn’t provide any official documentation? And how can I consider that user created documentation reliable, even if it is incomplete?

Thank you for your time, and I look forward, hopefully, to your reply, which will certainly be useful to me.

Take care :)

---

Hi Marco,

re:
> How were they able to create that documentation, even if only partial, if you
> didn’t provide any official documentation?

The primary method used to learn MOI scripting currently is by studying example scripts. Most functions in MOI use scripting to control the UI and logic flow and you can find them in the installation under the "commands" folder.

Also earlier versions of MOI were based off of a Windows scripting mechanism that needed the properties to be listed in a moi.idl file, so that was used as the main reference for creating that existing documentation.

I also will answer specific questions and try to make new examples.


> And how can I consider that user created documentation reliable, even if it is incomplete?

By studying other scripts that use it, testing it yourself and through trial and error.

- Michael

---

Hi Michael, and thanks for your reply :)

re: “I also will answer specific questions and try to make new examples.”

Alright! Thanks for letting me know, that’s definitely something that could be very helpful for me in certain situations.

Reading your last sentence made me smile, and I say that sincerely and in a friendly way: “By studying other scripts that use it, testing it yourself and through trial and error.”

That’s honestly one of the most “zen” answers I’ve ever read, especially considering it comes from one developer to another

---

Hi Marco,

& truly one of the best ways to learn about a particular tool--however I fear those that lean heavily on AI loose out.

Another helpful API resource is the release notes that Michael puts out as there are often many tidbits about the API, particularly those that have been inspired by forum conversations.

--Larry

---

If you're interested I did map out the entire API surface for MoI 5 over the xmas holidays and created comprehensive type definitions for all. I'm developing a script editor plugin which includes type checking and live execution, here's a quick preview: https://www.youtube.com/watch?v=Ru8p8kA54Mw

More to come. If this is something that interests you, you can reach me via email at turbo@code.tc (I don't want to hijack this thread for this project), would love to learn more about your use cases for scripting MoI.

(Though I wish I wasn't spending 60% of the time on this project fighting the ancient webkit version.)

---

Show messages:  1-10  …  31-50  51-70  71-90  91-104