Raylux 0.29.0: the built-in script editor

Scripts are written in a real editor now, and every small code box in the product grew up.

Scripting

• A built-in Python editor, instead of shelling out to whatever text editor happened to be installed. Saving goes through the same automatic project save as every other editor, so there is no separate "save script" step to get out of step.
• Completion fed by the gateway itself. The gateway reports what a script can actually call, so the suggestions cannot disagree with reality the first time Studio and the gateway are different versions. Your own project scripts and a tag-path search are included.
• Highlighting that knows what is real — a valid call renders as a known call and a typo renders plain, as you type it, before you save.
• Every code box gained Expand, and an external-editor option where it makes sense. Binding scripts, expressions, transforms, event scripts and query SQL were all authored in boxes a few lines tall wedged into a form.

Workspaces

A Workspaces screen in the gateway interface, so "why is this module missing from Studio" has an answer you can read. Switching one off reaches a connected Studio immediately rather than at its next reconnect.

Fixes

• A view's "Kind" setting is gone. It decided nothing — popups are ordinary screens — but it had a real casualty: the popup settings that do govern behaviour were greyed out unless a view was flagged as a popup, while the runtime read them regardless. They are always editable now. Existing projects are carried through untouched.
• The designer ignored the root container's type, so a view laid out as a row or column was drawn stacked in the designer while the running HMI laid it out properly. The view you designed and the view you shipped were different.

Upgrading

Drop-in. A row or column view will look different in the designer after this upgrade — it will now look like what your operators have been seeing all along.