A generalist applet to manage power, screen, resolution...

[FabriceV]

Hello,

Just to inform of a new device-power-screen-resolution management applet named Jupiter.
http://sourceforge.net/projects/jupiter/
A screenshot
http://netbooked.net/blog/jupiter-power ... r-netbooks

Apparently, seems to work fine with NC10 too.
The only drawbacks are :
- colored icon rather than an elementary style,
- slow responsiveness so that it is difficult to click immediately a second time to correct a wrong first click on a menu.

A software that can be integrated inside PPA?

[FabriceV]

I have finally find the author's blog.
I have posted a longer message to list the minor problems (with a lot of spelling mistakes, unfortunately...)

http://www.fewt.com/2010/02/meet-jupiter.html

[voria]

Thank you for reporting it, I will surely try it.

Anyway, I started a new project several days ago, called samsung-tools.
Code branch's description:

The successor of 'samsung-scripts'.

It uses D-Bus functionalities for providing a system service dedicated to the control of the various devices on Samsung netbooks (bluetooth, wireless, webcam, backlight, cpu fan) and a per-user session service dedicated to the control of the user-related aspects (hotkeys, notifications, etc). Scripts/GUIs will be provided to allow the control of both services.

I'm developing it in a way that allow easy expandibility in future.

It's structured into levels:

• Level 1: the system service.
  It runs with elevated privileges, it takes care of the physical control of the system's devices.
• Level 2: the session service.
  It runs with user privileges, it "talks" with the system service and it takes care of managing user's aspects (like showing bubble notifications, managing hotkeys, and so on). There can be more than one session service running at the same time (one for every logged user), all of them talking with the running system service.
• Level 3: end-user scripts/GUIs.
  They are used directly by the user, they "talk" with the user's session service.
  They can be anything coming in your mind: command line scripts, GUIs, applets, and so on.

Just to make an example: if at some point we change the way the bluetooth toggling is managed by the system service, the session service (and end-user scripts/GUIs, of course) will continue to work without problems.

At the moment, the system service is fairly complete, it already manages bluetooth, webcam, wireless, backlight, cpu fan.
The work on session service proceeds good too: notifications already work, but it lacks hotkeys support yet.
Today I start to work on an end-user command line script, so that the basic functionalities can be already used.

[euri]

@FabriceV
I think, you won't need the jupiter-applet. It is just a collection of scripts (like the samsung-scripts) with an applet written in mono. If you really want to have an applet, you can write your own applet. If you don't know how you could have a look at the easy-slow-down-manager applet
http://easy-slow-down-manager.googlecod ... manager.py
written in python. It shouldn't be too difficult to extend it with functions you want to have.

[FabriceV]

Hello,
Voria => Nice to see a new configuration manager dedicated to Samsung's models. Congratulation on your works.
Euri => I will continue to use Jupiter, nothing currently exists that competes. The major advantage is to resume many applets into one. It's not perfect, but quite efficient.