public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Session/.desktop WM compatibility, DM unification
Date: Wed, 29 Mar 2006 19:45:44 +0200	[thread overview]
Message-ID: <200603291945.48697.danarmak@gentoo.org> (raw)
In-Reply-To: <1143498427.22350.14.camel@rivendell>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Tuesday 28 March 2006 00:27, foser wrote:
> I'm aware of the issues surrounding menus, but the spec gives a lot of
> options. As said, we haven't dealt with it, because it is not a snag
> that we hit currently.
>
> I think we can basically have several menu setups fit for different
> tasks/DEs and either let loginmanagers choose on startup or users choose
> on install.
>
> I don't know what the future plans are of KDE regarding it's slotting,
> but if it intends to use syswide (fdo) specs like mime/icons the install
> alternate root is going to be the main hurdle to tackle.
If we make a system for selecting menu items. etc on a per-session basis, like 
you describe above, then I think we can easily support arbitrary additional 
install locations, specified in env.d or session files.

I like the idea, now we need to actually design and build such a system :-)

Do you think all fdo items should be controlled by it and not just menu items? 
Or should some things always be available (at least by default)? I'm in favor 
of making everything else available by default (services and so on) because 
1) I think it's easier using fdo specs - menu files already support filtering 
and 2) the main complaint against having everything in the menus is clutter, 
and that's not as big a problem with e.g. filemanager context menus.

-- 
Dan Armak
Gentoo Linux developer (KDE)
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-03-29 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 22:03 [gentoo-dev] Session/.desktop WM compatibility, DM unification Dan Armak
2006-03-27  9:02 ` Paul de Vrieze
2006-03-27 14:55 ` foser
2006-03-27 15:01   ` Paul de Vrieze
2006-03-27 16:23   ` Donnie Berkholz
2006-03-27 20:25   ` Dan Armak
2006-03-27 22:27     ` foser
2006-03-29 17:45       ` Dan Armak [this message]
2006-03-28  5:04     ` Aron Griffis
2006-03-28  9:51     ` Jakub Moc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200603291945.48697.danarmak@gentoo.org \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox