openmw.org

Status update: ptmikheev and I have agreed on a query builder implementation, and it is now included in his Lua MR. It also includes a temporary proof of concept implementation of queries written in Lua, so you can see them in action in his example mod here https://gitlab.com/ptmikheev/openmw/-/tree...

sorry to fuel more flames, but I wanted to point out there is a secure, standalone 1 file JavaScript runtime environment called Deno https://github.com/denoland/deno to quote their readme: * Secure by default. No file, network, or environment access, unless explicitly enabled. * Supports TypeScript...

There is already a refactor MR to get things usable for VR... not sure if that will cause conflicts. From what I know about that one, it doesn't really touch the same things I'm talking about. The main change there is the ability to render parts of the UI into separate buffers. It would, of course,...

We already have a concept of script interfaces in the Lua API. Essentially, it allows a script to assign a table to a string, which is then available to all other scripts attached to the same object. In that case, we could have every UI element be a script attached to the player, and smaller UI elem...

With the Lua MR taking form, it's probably time to consider how to implement various parts of the Lua API. This thread is meant to be a discussion on how to best approach it for the in-game GUI. Current state of UI in OpenMW: OpenMW uses MyGUI to render in-game UI. The implementation consits of XML ...

I've updated the script example to feature the current syntax (stll here https://gitlab.com/uramer/openmw/-/snippets/2072751).
Now the relations and fields are nicely read from pre-generated tables, rather than constructed manually from Lua.

I think it would be beneficial to make use example-suite assets when writing tests so that we don't need to rely on Morrowind itself, if that's necessary. When I said "actual OpenMW records", I meant the structs in the esm component, not necessarily actual Morrowind data. I was planning t...

I guess it's time for a progress update. Current status: 1. Support models with one-to-one relations of any depth. 2. Constructing queries with SQL-like features: filters ("where"), sorting ("orderBy"), taking one of a group ("groupBy"), limit, offset, including relatio...

Minor feedback on the second menu concept: the dot from the checker pattern is interfering with the menu buttons somewhat. Maybe shift it one checker to the side?

Why does OpenMW need an ORM to query database? It's possilbe to write SQL for every query required. I don't see where you considered this approach. Pros for this approach: * No need to fight with ORM on how queries are generated * Use all SQL features without cost of C++ code in ORM * It's more cle...