Hey, Sorry for the delayed response. My thought about using DBUS to do the detection is that doesn't that run for every instance of the user's login shell? The use case I'm thinking of here is if hildon-desktop is running on X on the computer's monitor, and you're also running X GUI apps via X forwarding over SSH. Then conceivably the app would detect that hildon was running, and enable/disable features accordingly... which would not be the desired behavior, especially if you were running your remote X sessions on OSX or Windows. Or, do I have a misconception about how that works? Thanks.
Dustin Loïc Minier wrote: > On Mon, Apr 21, 2008, Spencer, Bob wrote: > >> For moblin-media they used a --disable-hildon cmd-line. This assumed >> that non-Hildon use was relatively unused. >> >> A gconf key could be defined and set on startup if Hildon environment >> active (\desktop\hildon\...?) >> > > Why would you need a gconf key? Why not simply detect whether the > hildon-desktop name is registered on the session bus and use that > information to decide to enable hildon UI or not? > > Usually GConf keys are for settings, but I'm not sure any user would > want the software to run in non-hildon mode when hildon-desktop is > running or vice-versa. > > -- Innovation is just a problem away -- Ubuntu-mobile mailing list Ubuntu-mobile@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
