3 ms·

(1) is definitely by convention and not technical limitation, I definitely stated that during our last conversation. Audio & video mixing is done via "Cortex".

(1) is definitely by convention and not technical limitation, I definitely stated that during our last conversation. Audio & video mixing is done via "Cortex". Looks like we don't have great documentation for it yet, but here's an old screenshot: http://maurice.kaldience.com/wp-content/uploads/2008/03/haikucortex.jpeg http://maurice.kaldience.com/wp-content/uploads/2008/03/haik... Regarding scripting on Haiku, here's a basic introduction to the main CLI tool: https://www.haiku-os.org/blog/humdinger/2017-11-05_scripting_the_gui_with_hey/ https://www.haiku-os.org/blog/humdinger/2017-11-05_scripting...

AnIdiotOnTheNet 6y ago
> (1) is definitely by convention and not technical limitation, I definitely stated that during our last conversation. Indeed, now that I think back I believe that was ultimately what you clarified about my misunderstandings of Haiku and package management. What still baffles me somewhat that it seems normal (non-ported) Haiku applications are actually made less flexible by packaging them because they 1) have no non-base-system dependencies and 2) hpkgs only work from certain locations (IIRC currently hardcoded but could potentially be configurable). Cortex does look a lot like the kind of system I'm thinking of. That's wicked cool. When Haiku supports hardware accelerated video one imagines they could stick arbitrary shaders in the video pipeline to accomplish some useful, or at least really neat, things. I know built-in audio routing functionality would save me a lot of time on the Halloween display each year, maybe I should look at doing that with Haiku next time. I see this quote in the comments about 'hey': "hey is not a tool to send generic BMessages", which seems like a missed opportunity from way out here at 100ft. Otherwise the only thing that seems needed for GUI exposure is a script editor with 'record' functionality and perhaps some kind of manager for how scripts are tied to system events.

AnIdiotOnTheNet 6y ago

> (1) is definitely by convention and not technical limitation, I definitely stated that during our last conversation. Indeed, now that I think back I believe that was ultimately what you clarified about my misunderstandings of Haiku and package management. What still baffles me somewhat that it seems normal (non-ported) Haiku applications are actually made less flexible by packaging them because they 1) have no non-base-system dependencies and 2) hpkgs only work from certain locations (IIRC currently hardcoded but could potentially be configurable). Cortex does look a lot like the kind of system I'm thinking of. That's wicked cool. When Haiku supports hardware accelerated video one imagines they could stick arbitrary shaders in the video pipeline to accomplish some useful, or at least really neat, things. I know built-in audio routing functionality would save me a lot of time on the Halloween display each year, maybe I should look at doing that with Haiku next time. I see this quote in the comments about 'hey': "hey is not a tool to send generic BMessages", which seems like a missed opportunity from way out here at 100ft. Otherwise the only thing that seems needed for GUI exposure is a script editor with 'record' functionality and perhaps some kind of manager for how scripts are tied to system events.