Chris Cannam writes:
> The procedural difficulty I suppose is that you're trying to get
Yes the goal is to have simple to implement state save "message" that
does not require additional libraries. Whether app developers will
implement it is of course their own decision. If their users want it
they will have to choose whether to please them or not. If their users
don't want it, and they don't like level 1, there is no reason to
implement support for it.
> The problem I have always had with most of the proposed LA session
I dislike the LASH API too. But most importantly LASH requires apps to
link to liblash just to restore their connections. This is something
that I find... suboptimal.
> But, I have never tried using ladish and frankly the time taken to
Maybe you can watch the video, it is less than 5 minutes long.
> (One idle thought is that any proper "desktop" application is going to
Desktop session handler traditionally relies on X11. The trend in
freedesktop (KDE, GNOME) is to use D-Bus as IPC instead. I'm not aware
of D-Bus desktop session manager. Probably, in future, ladish could act
as a desktop session manager (via D-Bus or X11) as it is not really
limited to JACK apps, it just has some nice features for
them. Interracting with the X11 window manager is within the scope of
the ladish project. In future, ladish aims to save/restore window
properties like window position, virtual desktop and screen
(multimonitor). That said, some window managers remember window
positions and their virtual desktop out of the box. Some have
configurable set of rules for positioning windows isntead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----