| Version | Change log |
| Praxis LIVE 6.1.0 Feb 12, 2025 |
PraxisLIVE IDE: Enhanced graph editor: New UI for showing exposed controls and watches underneath components. Which features are exposed can be controlled by the Expose option in the popup menu. The default exposed features is controlled by @Config.Expose in component code. Updated minimize function to keep visible only connected ports. The minimize toggle now controls all selected components. Added Select All and Select None actions with keyboard control. Improved zoom function to snap to 100%, and added keyboard control (CTRL-PLUS and CTRL-MINUS or equivalents) Removed legacy exposed properties support. Various other graph enhancements and performance improvements. Added tab grouping to keep code editors and root editors in separate tab groups where appropriate. Added support for opening a new tab group automatically when the first code editor tab is opened. Behaviour can be controlled via Tools / Options / Editors. Added support for changing to other FlatLaf look and feels, including light (as seen below), as well as customizing and accent colours. Support for light look and feels is mostly there but there are still a few issues to address. Improved consistency of various icons and displays. Updated to Apache NetBeans 24 platform. Various bug fixes. PraxisCORE runtime: Added support for watch functions. A watch function is a function control for accessing data about a component. They are somewhat similar to read-only properties, but for data that should only be calculated on demand, and perhaps asynchronously. Watch functions have a mime type and other metadata, and may support an optional query map as input to control the returned data. They are defined in code using the @FN.Watch annotation. Added support for defining image watches in video components, and added watch implementations to video:composite, video:still and video:xfader. Enhanced Async API and allowed it as a return for standard functions (@FN), as well as for watch functions. Async should be used w |
| Praxis LIVE 6.0.0 Nov 15, 2024 |
Built in non-recodeable roots for MIDI, OSC and TinkerForge have been removed. These can now be replicated using custom roots. Basic implementations will be added as custom root templates when installing custom components. A migration path might be looked at for a later (post 6.0) release of the IDE. Most deprecated functions and types have been removed. eg. lower case casting functions like d(..) must use D(..); Property values() linking must now use doubles(); PVector is only available from video:gl:p2d and video:gl:p3d components, etc. Make sure to migrate all deprecated functionality from inside the latest PraxisLIVE v5 before attempting to migrate a project to PraxisLIVE v6. |
| Praxis LIVE 5.7.0 Aug 4, 2023 | |
| Praxis LIVE 5.6.0 Jun 6, 2023 | |
| Praxis LIVE 5.5.0 Jan 28, 2023 | |
| Praxis LIVE 5.4.0 Jan 28, 2022 | |
| Praxis LIVE 5.3.0 Sep 27, 2021 | |
| Praxis LIVE 5.2.0 Apr 26, 2021 |
PraxisCORE runtime Support shared, rewritable code across components within a single root. Sources for shared code are stored as a map property on the root component. All code is in the SHARED package. Any component that imports shared code will be automatically recompiled whenever shared code changes. Breaking changes or deletions of shared code in use will fail. Data ports can pass shared types between components. NB. As part of this change, the full class name of component code has changed to accommodate compiling multiple components at a time. This shouldn't cause major problems. NB. As part of this change, the module providing audio and video root components changed. This shouldn't cause major problems. |
| Praxis LIVE 4.4.0 Sep 3, 2019 |
Changes: PraxisCORE runtime: Core: New base module providing simpler and more robust base root class and other utility classes. The new root implementation is currently used by generic data patches root:data and internal services. These changes will allow for removal and replacement of a lot of remaining legacy v1 code in v5. The container component (core:container) now allows for exposing ports of any child component via its ports property (see IDE improvements below too). This is a map of IDs to relative port addresses. All specific input / output components (eg. audio:container:in) are now deprecated. Known issue - removing a mapped port will disconnect all connections to the port, including those inside the container (the API is missing the ability to find only outside connections at present). Known issue - deleting a container will sometimes leave child components connected. Always delete connections first. Workaround is to save and reload. |
