Date: Tue, 18 Sep 2012 04:57:53 -0500 From: Mike Meyer <mwm@mired.org> To: Zhihao Yuan <lichray@gmail.com>,Guido Falsi <mad@madpilot.net> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: My explanation to "a default DE" (was "Providing a default graphical environment on FreeBSD") Message-ID: <9f2044aa-1413-40d2-966f-b9f0294b4210@email.android.com> In-Reply-To: <CAGsORuDv50eU2JAMZ_kaKjzvHZAComtDd%2BSyfUZPAHPrJpZOYw@mail.gmail.com> References: <CAGsORuAmWBKUZFHu74ZLBWt=wESWKtk7tv4-e6CqmK9szrAL6w@mail.gmail.com> <5057906C.9090002@madpilot.net> <CAGsORuDv50eU2JAMZ_kaKjzvHZAComtDd%2BSyfUZPAHPrJpZOYw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Zhihao Yuan <lichray@gmail.com> wrote:
>As u can see, it's a stand alone app. But the most widely used wifi
>managers are always taskbar applets -- something bound to a specific
>DE. --
There are a number of taskbar applications not bound to a DE (dzen2, mobar, gkrellm2) which have plugins for managing the kinds of things you're talking about. The X protocols provide a way for such applications to declare themselves as "bars", and for other interested applications (usually WM's) to discover the screen geometry both with and without bars.
>we must standardize a ${DE}!
Why? So far, the only advantage you've cited is that users can get a supported, documented desktop on FreeBSD (except there's nobody to support or document it) and developers could get a documented desktop to write apps for (except there's again nobody to document it, and you're the only developer asking for it), and you haven't said anything bad would happen if this doesn't happen.
<mike
--
Sent from my Android tablet with K-9 Mail. Please excuse my swyping.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9f2044aa-1413-40d2-966f-b9f0294b4210>