Quote:
Originally Posted by kodomo
hm - ic - so it's not as much as I thought it'd be... unfortunately, some of the stuff I need is actually in the system_manager... do you have a clear view on how gui_shell and system_manager interface, and whether there are forseeable API issues between the A60 and M92 version?
|
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.
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
Quote:
Originally Posted by kodomo
What would you deem the first step?
If your gui_shell can be compiled as a single binary which I may copy onto the regular firmware and try starting it, I could check whether it compiles in my M92 devel setup...
|
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.
Quote:
Originally Posted by kodomo
Would you like some M92 binaries (e.g., naboo) to check on whether they run on the A60? (It seems to me that it makes sense trying to salvage as much of the closed source from the newer firmware as we can... when I think about their promised multitasking functionality, I'm a bit worried about serious API modifications)
|
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.