[haiku-development] Re: R1/a4 initial planning
- From: Ryan Leavengood <leavengood@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 2 Mar 2012 15:54:24 -0500
On Fri, Mar 2, 2012 at 3:41 PM, Stephan Aßmus <superstippi@xxxxxx> wrote:
>
> I haven't looked at the implementation in GIMP, but isn't there some kind of
> configuration interface for this? Where would that go? How could it be moved
> from the aplication to a generic place?
I find the concept of using MIDI devices (or other hardware) to
control applications quite interesting, but I agree with most of the
comments that making some sort of pluggable component system or
whatever for this is a bit overkill.
With Haiku it would not be terribly hard to make an input server
plugin which could listen for MIDI events from a device and then turn
those into keyboard or mouse actions. This could be used to control
all sorts of applications. It could even adapt based on the current
active application (and associated settings.)
Or another approach would be some background daemon that listens for
these MIDI messages and then sends out specific messages to configured
applications. So as long as an application exposes some messaging
protocol it could be controlled with this system. Like if Stephan
exposed the sliders in Wonderbrush with a messaging protocol they
could be controlled with such a system.
Overall this is a more flexible approach which fits in with the Haiku
philosophy and it could work right now.
As for color or font pickers, even on BeOS there were custom color
pickers applications like roColour, and the "BeOS way" was to just
have apps support colors being dragged into them from such apps. As
far as I know, Haiku still supports that (and if not, we can add it.)
I certainly appreciate your enthusiasm and ideas Julian, and I do
intend to read about fGUI, but overall I don't know if a
super-pluggable architecture is what we want for Haiku right now.
--
Regards,
Ryan
Other related posts:
