I'm not at the stage yet where I can claim the API is stable. It simply won't do to have an rtk update break even a single script. Having a single installation that all scripts use imposes strict requirements on API stability. I have been and continue to be wrestling with this one. But I guess a scripter could have his own instance of rtk, used by all his script ? So how do we keep up to date version of rtk ? Does this means than any fix you made have to been pushed by other scripters too? I think centralized distribution like scythe or reaimgui are quite interesting cause if the extension got a fixed, than all script depending on them will got one. So head on over to rtk's website, sift through the tutorial, take rtk out for a spin, and let me know what you think. If you have a feature request, feel free to ask here or open an issue on GitHub (or both). ComboBox (text entry plus selection list).On the subject of widgets, these will be coming soon, mainly because I will need them for Reaticulate (and its infamous any-day-now-honest articulation map GUI editor): Your opinions will certainly help to influence rtk's direction.Īs of, the API is considered stable, and there is a documented process that allows for introducing breaking API changes while also not impacting existing scripts. LuaDox is available as a separate project.įirst and foremost, I am very interested to hear from you folks what you think. Like Lokasenna, I wrote my own Lua API doc generation tool (clearly we both recognized how terrible the state of the union was ). rtk supports both installation by ReaPack or integration and redistribution by script authors.rtk supports both light and dark themes, and auto-selects based on REAPER's theme to provide a more integrated aesthetic.rtk has significantly better documentation.rtk has more core features, such as enhanced window management (via js_ReaScriptAPI), drag-and-drop, animation, and a rich widget API and event system.Scythe has more widgets (rtk will develop more as the project matures, but Scythe is further ahead).Due to the above, Scythe is smaller and probably performs better (as dynamically calculating layouts obviously brings some overhead).Scythe uses a fixed coordinate system, while rtk uses dynamic and scalable layouts via containers and a CSS-like box model.But based on my perusal of Scythe's documentation, I see these key differences: The core of rtk was written for Reaticulate many years ago so I'm afraid I've not actually used Scythe before. I suspect this will be a FAQ, so I'll address it here. How does it differ from Scythe (Lokasenna GUI v3)? And of course various widgets (buttons, text inputs, option menus, checkboxes, etc.).This short screen capture demonstrates several of rtk's features, including: Rtk was originally written for Reaticulate, which is shown below to serve as a demonstration of rtk's capabilities. Visit the project website for documentation and download instructions: I had invested so much time into it that I felt it deserved to be released as an independent library. Rtk is born out of the underlying GUI code that powers Reaticulate. I'm happy to announce a new library called the REAPER Toolkit ( rtk), a GUI and utility library for REAPER Lua scripts, which leverages REAPER's native GFX API without any external dependencies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |