On Tue, Feb 8, 2011 at 10:55 AM, Thiago Macieira <[email protected]> wrote: > Em terça-feira, 8 de fevereiro de 2011, às 07:21:55, Wichmann, Mats D > escreveu: >> [email protected] wrote: >> > Freedesktop.org has some specifications that are relevant to >> > developers: >> > >> > http://www.freedesktop.org/wiki/Specifications >> > >> > Does being MeeGo include a promise to follow some of these >> > specifications, or is it left entirely up to the vendor to implement >> > whatever they deem fit? >> > >> > My primary interest at this point is the autostart spec: >> > http://www.freedesktop.org/wiki/Specifications/autostart-spec >> >> I've been assuming that the ones mentioned in LSB can be >> considered a given (Base Directory, Desktop Entry, Desktop >> Menu, Icon Theme) although it's possible nothing says so >> explicitly. The rest... it sure seems like Autostart >> is being followed, should this and others be added to the >> compliance spec? > > Then we should list the ones that implementations are required to obey, even > if "by reference" and included anyway by the requirement of the packages. > > For example, the Icon Naming Convention, which I'm not sure we're following, > we should be. > > By the way, has XDG fixed the problem of discovering the active icon theme? > > Which in turn reminds me: some of the X-based specs will require a replacement > once we move to Wayland, like XSETTINGS or XDND, whereas others won't make > sense, like NETWM.
Wayland has a drag and drop protocol, and I've been thinking that an XSETTINGS-type protocol may make sense. It would be a pretty simple mechanism, but I've been debating whether the functionality needs to be in the display server. There is a considerable overlap with native configuration systems such as gconf or dconf and toolkit themes. Parts of ICCCM/EWMH/NETWM still makes sense - clients still need to communicate window titles, icons, window types and such to the compositor, but we'll only need a subset. Kristian Kristian _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
