Quote:
Originally Posted by Koudijs
It's not too bad, or actually, there is a lot that can be done via the Onyx libraries from the SDK. The libonyx_sys library provides the interface to the system manager, you can find the sources in code/src/sys (checkout sys_status.cpp). I have used this to implement custom screensaver support and at this moment I'm adding a wifi connection icon to the statusbar showing the signal strength.
Attachment 84848 |
I see (I'm currently hacking some tiny apps to get a grip on what is possible, and how it is done)... but if I get this correctly, an application itself decides on the menu structure...(?) which means that even if we got the gui_shell source, we could not add e.g. additional colors to naboo (or easily change its response to stylus button events)
Please correct me, if I got this wrong (I would very much like to be on this point :-| ).
At the moment, it seems to me like one'd have to change the naboo source to add new icons to the menu, or to implement new event slots for e.g., stylus button events... that would be unfortunate and most annoying...
Quote:
Originally Posted by Koudijs
There is one major issue, the only documentation available is the code itself, so it can be pretty time consuming to find out how everything should be used  |
Indeed... at the moment, I'm confused by screen refreshing... is there any documentation about it? (Need to say: I never programmed with Qt before)
Writing an application, which simply opens a MessageDialog, was easy - I didn't even need to use the screen_update_watchdog explicitely.
However, copying the PasswordDialog into another class (I needed access to its private fields), applying only trivial modifications (e.g., changing the window title), I cannot make the screen update behave even if I set a screen_update_watchdog onto it... can someone enlighten me here?
Update: Solved - I forgot to setSystemBusy(false)
Quote:
Originally Posted by Koudijs
Probably the easiest way to build the "gui_shell" is by using/checking the OpenBOOX build system, because it requires some libraries that are not part of the standard firmware. I also saw that the M92 uses a newer version of Qt of which I don't know if it's backwards compatible. |
Have to try when I find time...
Quote:
Originally Posted by Koudijs
I tried the M92 build of evopedia that can be found here, it does not run because it requires a different version of libstdc++.so.6. I think this means that the A60 and M92 are not binary compatible. I'm still hoping for a 1.7 version for the A60. |
Interesting... isn't it linked statically?