Fireclaw

> The main problem that I see here is that whatever is put in place might then clash with the developer's control-scheme. :/ Right, it could of course be enabled...

> Even then, if the developer has, say, movement mapped to the numpad and DirectGUI responds to the arrow keys, but _not_ to the numpad, then the developer may end...

> a developer might come up with some way of controller the UI that's very different. Yes, that's what I thought too and indeed there do exist very exotic UIs...

Alright, most of the topics should be covered with dedicated issues now: 1 & 2 Property usage - #1350 3 Property return values - #1353 6 UI Navigation - #1351...

> Sounds like we could also use some doc improvements and some samples. I totally agree on that, those things are probably somewhere in the manual but I also sometimes...

While I do agree with JSON not being the most readable format, having my visual designer for it is probably remedies for the readability since you won't usually look inside...

python, while easy to use and maybe even viable for some designers, it is not that easy to use in editors as compared to the other types since they usually...

Right, the data behind the editor doesn't matter that much since it will only be viewed in case of an error, editing files that are created by an editor is...

> My argument is less that we should go with binary blobs, and more than what DirectGUI Designer currently does might be okay. That's what I understood too, just mentioned...

> (I think that I may have taken the "a" in "I'd prefer to have a open standardized format" to indicate just one such format.) Ah, my bad then, sorry....