Re^2: Net::DBus/Logitech G19 Meditator

Thanks for your reply.

After thinking long and hard about it, the API itself isn't that bad (it works and when understood is quite locigal). But the documentation of it could use some updates.

Here are some recommendations and questions:

How is the relationship between the different interfaces? A simple tree graph or similar could really clear that up.
Show some (pseudo-code?) examples on how to actually use it.
What happens if the client crashes? Thus Gnome15 clean everything up? What do i have to do for a clean shutdown?
The drawing commands feel quite slow. Any way to batch process them?
The Image() page function rocks. I was able to play high FPS movies. But what formats are supported?
Gnome15 also controls the keyboard backlight and the G-Key mapping, right? Could i use the API to control that?

After writing my "list of demands", i like to really thank you for a very nice software. It actually is more fun to use the G19 on Linux than on Windows (with the possible exception of playing DNF)!

"Believe me, Mike, I calculated the odds of this succeeding against the odds I was doing something incredibly stupid… and I went ahead anyway." (Crow in "MST3K The Movie")

Comment on Re^2: Net::DBus/Logitech G19 Meditator

Replies are listed 'Best First'.
Re^3: Net::DBus/Logitech G19 Meditator by tanktarta (Initiate) on Jan 15, 2012 at 23:27 UTC
And thank you :) I'll certainly look into implementing your suggestions regarding the documentation. To answer your other questions :- "Client Crashes" - Currently Gnome15 will clean up any resources opened by the DBUS client when it closes. It didn't used to do this, allowing bash scripts and the command line DBUS tools to be used to create pages. But this was slow, and there was no way of knowing when to clean up if it went wrong. "The drawing commands feel quite slow" - This may be just DBUS, the drawing itself should be pretty quick. I think it's possible to make DBUS calls without waiting for a reply, which might speed things up a bit - no idea how though or what any side effects might be. Another alternative is to design the screen in SVG and use the SetThemeSVG() or LoadTheme() calls which will mean only 1 call. You can then draw other shapes or text over the top of that. "The Image() page function rocks" - Interesting use of that function! It should support anything that GTK does. Can you find out by runnng :- `$ python import gtk gtk.gdk.pixbuf_get_formats()` [download] Brett	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Net::DBus/Logitech G19 Meditator
by tanktarta (Initiate) on Jan 15, 2012 at 23:27 UTC

And thank you :)

I'll certainly look into implementing your suggestions regarding the documentation. To answer your other questions :-

"Client Crashes" - Currently Gnome15 will clean up any resources opened by the DBUS client when it closes. It didn't used to do this, allowing bash scripts and the command line DBUS tools to be used to create pages. But this was slow, and there was no way of knowing when to clean up if it went wrong.

"The drawing commands feel quite slow" - This may be just DBUS, the drawing itself should be pretty quick. I think it's possible to make DBUS calls without waiting for a reply, which might speed things up a bit - no idea how though or what any side effects might be. Another alternative is to design the screen in SVG and use the SetThemeSVG() or LoadTheme() calls which will mean only 1 call. You can then draw other shapes or text over the top of that.

"The Image() page function rocks" - Interesting use of that function! It should support anything that GTK does. Can you find out by runnng :-

$ python
import gtk
gtk.gdk.pixbuf_get_formats()
[download]

Brett

[reply]
[d/l]