¶ C# Scripting Engine V3 - added Blazor/Razor support
Major upgrade in the scripting engine - it can now compile Razor components. Blazor (Razor components are part of Blazor infrastructure) is one of the best (my opinion - for desktop apps just the best) UI technology which allows to have full power of C# and at the same time great performance/convenience of Web (HTML/CSS/JS) world.
EyeAuras is also using it under the hood since 2023 and is gradually being rewritten from WPF to Blazor. At some point in the future is expected to become full Blazor-driven app. Parts which are using it - BT editor, Macro editor, EventLog, Bindings, AuraTree. If some part of the program feels snappy you can bet it is using Blazor.
Previously, if you wanted to develop your own user interface for your bot, the only viable option
was to use WebUI Overlay which at this point is using very dated text editor and, more importantly, uses older version of the scripting engine (V2) back from April 2023(!). Of course, you could load up the project in your IDE of choice (like Visual Studio or Rider), but that was definitely not very convenient and took some extra steps.
At the same time, BTs, Macros and C# Action/Trigger have been using the newer iteration of scripting engine since Jan 2024, but they newer really had Razor support as it was technically challenging task to add it there without preparing some other systems first.
And, finally, today we're getting the first prototype. This is not just new feature - allowing users to create windows straight from the code makes it possible to develop full-blown standalone bots.
¶ What it already can do:
- you can create custom UI components right there in that same text editor
- full auto-completion for C# part of Razor component and partial - for Razor part
- API which allows to create windows and manage with your components right from your code
- thread-safety - in contrast with WPF/WinForms and even official MS Blazor integration, EA API is thread-safe, meaning you can update properties of the window from any thread and it is expected to be able to properly process those. No longer you have to worry about deadlocks and UI marshalling using Invoke/BeginInvoke.
- API mimics native WPF API to make it easier to code something using ChatGPT
¶ What it cannot do (yet):
- custom CSS/JS - in November
- No integration with IDE like in V2 - in December
- no hot-reload like in WebUI - there will be a next iteration of WebUI which will be using this new script engine somewhere in Dec/Jan or maybe even earlier
¶ Bugfixes/Improvements
- [SendInput] Improved performance of Windows Message API in multi-window scenarios
- [UI] Fixed crash which happened when Offset+Anchor were used at the same time
- [UI] Added SendText node, available in both BTs and Macros
- [Scripting] Improved Log.Info/Debug/Warn formatting - now UI properly renders line breakes
- [SendInput] Improved how keypresses/mousemove logs look like
¶ Some UI examples which are created in EA
