From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] desktop
Date: Thu, 28 Aug 2003 10:10:56 -0400 [thread overview]
Message-ID: <20030828141056.GJ6635@enki.datanode.net> (raw)
In-Reply-To: <200308281600.13232.pauldv@gentoo.org>
Naively stepping into this fray, how does this menu system differ from
genmenu (x11-misc/genmenu) which has in my use generated some rather nice
menus for my not-big-boy wm's (*box, wmaker, etc)?
On Thu, Aug 28, 2003 at 04:00:13PM +0200, Paul de Vrieze wrote:
> The menu system is not about having the same menu in all windowmanagers as
> much as it is about having every application added to the menu of whatever
> windowmanager you are using. Independent of what kind of toolkit the
> application uses. A vanilla useflag would function like currently the foreign
> package flag does for the kdeadmin ebuild. That flag enables the compilation
> of a package manager that is standard but currently does not work well with
> gentoo (it being not an rpm based system).
>
> For the menu system it might be necessary to patch some windowmanagers to be
> able to use our menu's while keeping some compatibility with a situation
> where the menu manager is not installed. Those changes are normally small and
> localised, but generally change some part of the plumbing of such a program
> while keeping generally the same behaviour. If you want to hack with a
> windowmanager yourself those changes might be confusing and hence the
> "vanilla" flag.
>
>
--
-----o()o---------------------------------------------
| http://www.gentoo.org/
| #gentoo-dev on irc.freenode.net
Gentoo Dev | #gentoo-perl on irc.freenode.net
Perl Guy |
| GnuPG Key ID: AB5CED4E9E7F4E2E
-----o()o---------------------------------------------
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-28 14:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 22:22 [gentoo-dev] desktop dams
2003-08-27 22:58 ` Spider
2003-08-28 0:41 ` Brett I. Holcomb
2003-08-28 0:47 ` Jon Portnoy
2003-08-28 0:58 ` Cedric Veilleux
2003-08-28 1:29 ` Riyad Kalla
2003-08-28 1:48 ` Stuart Herbert
2003-08-28 8:08 ` dams
2003-08-28 10:25 ` Paul de Vrieze
2003-08-28 10:51 ` dams
2003-08-28 11:08 ` Paul de Vrieze
2003-08-28 11:28 ` dams
2003-08-28 13:37 ` Mike Frysinger
2003-08-29 5:22 ` Luke-Jr
2003-08-28 11:15 ` foser
2003-08-28 12:52 ` dams
2003-08-28 13:21 ` foser
2003-08-28 13:51 ` Stuart Herbert
2003-08-28 14:00 ` Paul de Vrieze
2003-08-28 14:10 ` Michael Cummings [this message]
2003-08-28 14:34 ` foser
2003-08-28 14:30 ` foser
2003-08-28 17:44 ` Spider
2003-08-28 19:14 ` Peter Ruskin
2003-08-28 19:24 ` foser
2003-08-28 22:07 ` Peter Ruskin
2003-08-28 20:46 ` dams
2003-08-28 21:34 ` Spider
2003-08-28 22:32 ` foser
2003-08-28 23:01 ` dams
2003-08-28 20:35 ` dams
2003-08-28 21:03 ` Spider
2003-08-28 21:21 ` dams
2003-08-28 22:40 ` foser
2003-08-28 21:07 ` Paul de Vrieze
2003-08-28 14:59 ` dams
2003-08-28 21:17 ` Paul de Vrieze
2003-08-28 23:24 ` Jason Stubbs
2003-08-28 13:54 ` Chris Gianelloni
2003-08-28 15:03 ` dams
2003-08-28 15:09 ` Stuart Herbert
2003-08-28 15:36 ` dams
2003-08-28 15:48 ` jonah benton
2003-08-28 14:04 ` Paul de Vrieze
2003-08-28 14:48 ` foser
2003-08-28 23:30 ` Seemant Kulleen
2003-08-29 1:32 ` Luke-Jr
2003-08-29 14:06 ` dams
2003-08-29 14:18 ` Luke-Jr
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=20030828141056.GJ6635@enki.datanode.net \
--to=mcummings@gentoo.org \
--cc=gentoo-dev@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