View Single Post
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#49
Originally Posted by Mitrandir View Post
Actually, i don't expect that GTK can add much memory requirements because all its libs are already in RAM on Maemo.
asui-settings displays 10-15 buttons on start and uses 5.5meg. ASUI loads in a lot of data, opens numerous descriptors, launches a dbus thread and so much more and uses less than 3meg. Telescope has is the same way with all of its icons and window thumbnails and uses less than 5meg. And raw dbus handling is easy.

Oh well, try to keep it around 7meg like xmms.

Originally Posted by Mitrandir View Post
By the way, does anybody has ready solution for how to react on headset button press? I think it could be figured out from 'headphoned' (right?) sources, but may be someone remembers exact D-Bus signal name?
dbus-monitor doesn't show any signals when I press buttons on my headset. Volume changes but no signals and the main button doesn't do anything in media player.

These are the bluetooth docs I collected for ASUI.
http://bluez.cvs.sourceforge.net/vie...d/dbus-api.txt
http://bluez.cvs.sourceforge.net/vie.../audio-api.txt
http://maemo.org/maemo_release_docum....x/node10.html
http://wiki.maemo.org/Documentation/...Bus_UI_dialogs

https://garage.maemo.org/plugins/scm...ui&view=markup -- You can find dbus headset detection around line 1241.