2013/11/10 PCMan <pcman...@gmail.com>
I started a wiki page to discuss about lxsession redesign.
> https://github.com/lxde/lxsession/wiki/Proposals-about-the-session-manager
>
> The items listed in the page are just my own opinion without concensus.
> No code has been written for it so far.
> It's better to have some discussions before we really change anything.
>
> Here's a summary of my suggestions:
> 1. remove the legacy autostart file and use xdg autostart spec only.
>
+1
> 2. extend xdg autostart support to get additional features we want, such
> as auto-restart.
>
In theory, it sounds like a good idea. However, it's always difficult to
deal with those desktop files. You have 3 (and sometimes 4) levels in this
area : the ones installed by default by the application, the ones installed
by the distribution (and sometime, the one install by the derivated
distribution), and the one installed by the user. It means that each ones
need to have the extended support ... a lot of applications to patch /
contact ... However, this can "fix" the problem of the 2 levels settings in
[Session], the entry will be only the .desktop file.
> 3. remove the xsettings daemon. though it works very well for gtk+ 2, it
> becomes broken in a mixed gtk2 and gtk3 environment. With xsettings, gtk+ 2
> and 3 are forced to share the same set of settings, but actually, they need
> different config values. So it no longer works.
>
Ideally, the user should not deal with this mess. "Something" (session
manager or other) should do the bridge between all this. The key IMO is to
design a structure in the theme, so "something" knew what to do, load, set
... to apply correctly the theme.
Btw, xsettings could also just be optional (already in lxsession, by
playing with Session/xsettings_manager/command), turn off by default.
4. simplify dbus interface. Replace Set/Get/Supports with standard dbus
> properties. Drop the two-level design and use a namespaced one-level key.
>
That could end with unreadable keys. It's probably better to start with a
list of options we want to support, and see if it compatible with a
one-level key structure.
> 5. drop default applications support. In the future this will be done with
> "xdg intent spec" Jerome proposed. the spec is not finished yet, but we'll
> use it later when it's ready.
>
Fine, but the spec is still not here :-) Until this, the support in
lxsession is still optional (like most of the settings in lxsession).
About systemd/upstart integration, what do you exactly mean ? In my mind,
it's just that lxsession needs to disable some of its functionalities when
it's handle by systemd/upstart. So, it needs a way, by the settings, or by
a detection, to disable some of its components.
Regards,
Julien Lavergne
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
