[03:14] <OvenWerks> systray, appliaction indicator, and panel applets are all different.
[03:15] <OvenWerks> It seems that panel applets are panel(therefore DE) specific
[03:17] <OvenWerks> systray works everywhere? Or used to. and application indicators are supposed to replace systray stuff sometime.
[03:38] <OvenWerks> The stuff I read seems to be a few years old.. but seems to indicate that gnome 3 (shell and classic) hide the systray.
[03:45] <OvenWerks> They do seem to have indicators... I need to install it again and check.
[06:05] <DalekSec> OvenWerks: I *think* the Gnome3 indicators are different than the Ubuntu indicators.  Unity also doesn't do systray, while LXDE and tint2 don't do indicators.
[09:10] <zequence> OvenWerks: Gnome3 has its own thing, but can support both indicator and systray apps with plugins
[09:11] <zequence> falktx has some code that makes his app be either systay or indicator, depending on the platform
[14:46] <OvenWerks> zequence: I am also reading that unity _can_ turn a systray on... but that may be old info. It would be nice rather than looking for the platform to look for an indicator box and use it if it is there... if not then look for systray... which should cover the flavours we have to deal with. It would also be possible to "iconize to desktop" which used to be very common in the early days of X.
[14:54] <OvenWerks> Reading things at free desktop org, it appears that the application indicators are meant to be a replacement for systray. So it is possible that LXqt will include app-indicators in the future.
[15:01] <OvenWerks> Gnome as you say has it's own thing, but I expect ubuntu gnome will include the plugins needed anyway. (I don't know about debian)
[15:05] <OvenWerks> As to freedesktop.org, I will also note that the systray in inthe section called: Draft specifications that are new and not yet widely used.  Yet I think you can get systray support for almost any wm/de out there. The application indicator is called: Specifications currently in the planning/requirements-gathering stages
[15:06] <OvenWerks> even though they have been in use as a standard for a number of years.
[15:16] <OvenWerks> anyway, gui is maybe not so important just yet.
[15:19] <OvenWerks> I did wnt to throw some things out about security though. Editing of system files should require a password, but switching system modes should not. That is setting CPU governor on the fly should not require a password. Turning off some system services that have been pre selected with a password should not require a password either.
[15:22] <OvenWerks> I expect that most people will not require turning system services off (cron for example), however, there are some systems where removing the wireless kernel module is the only way to get lowlatency audio without xruns. (these would be laptops)
[15:38] <zequence> OvenWerks: Ubuntu Gnome, to my knowledge, does not have those plugins by default. Haven't seen them packaged even. One needs to get them at extensions.gnome.org
[15:45] <zequence> OvenWerks: On monday and onwards I will have more time. It's time to wrap up feature specs, and so I will do that during the week for everything.
[15:46] <zequence> I'll also wrap up what has been discussed about -controls, and update/re-organize the wiki page, and make sure there is a relevant blueprint
[15:47] <zequence> Nice work on the mail list, btw. 
[15:49] <zequence> Feature Definition Freeze is on Thursday, I think. 
[15:50] <zequence> Not a big deal for most of our work, but it's good to be firm about the stuff that Ubuntu devs need to be apart of, like our new ISO
[15:50] <zequence> Also, that date is a good time to wrap up planning anyway, I think.
[15:51] <zequence> So, from there on, we can just focus on doing the work
[23:54] <OvenWerks> zequence: Are we going to get to pulling in code from the ubiquity plugin to -installer this cycle? If not we should get the current updates uploaded at least. The main thing is that it deals with install errors properly. The one released so far fails silently and just says complete.
[23:58] <OvenWerks> zequence: Can we create an -audio-setting or -system-settings package?
[23:59] <OvenWerks> This would not make doing system settings in -controls go away, but it would load settings that are done by installing files.