Bob Ham <rah@email-addr-hidden> writes:
>> * lash does not preserve X11 related properties of apps, like on what
>> screen (dual-head) they were.
>
> Nor should it. The X11 system is nothing whatsoever to do with LASH,
> intentionally. From LASH's perspective, anything to do with X11 is
> entirely the client's responsibility. Adding X11-specific functionality
> into the protocol, the server and the library should not happen.
>
> Providing convenience functions to clients is a solution, eg
> lash_x11_get_state_configs() and that returns a set of LASH configs
> containing the state of the X11 system. And, of course, functions to
> restore the state. But it should be separate from LASH itself, eg, in
> some liblash-x11.
>
>> * Supporting connections for things other than JACK (read ALSA seq)
>
> LASH already does support ALSA seq. Future support would be connecting
> via netjack, or firewire, or $next_big_thing.
Oh, sure, LASH should support network multimachine sessions but it has
nothing to do with X11? I find this funny :)
You want to use firewire for what exactly?
-- Nedko Arnaudov <GnuPG KeyID: DE1716B0>
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
This archive was generated by hypermail 2.1.8 : Wed Jan 23 2008 - 04:15:23 EET