I agree, the Single Library provided by OSDash is the way to go. For the Linux system though it makes sense to use that single library in a plug-able process. We've written the OpenICE components to be as frontend agnostic as possible. That's why fbd, proximity, and obdgpslogger are all separate processes. Furthermore, non-OpenICE stuff like Network-manager, oFono, bluez, gpsd, etc are also their own processes. So this OSDash Client implementation will basically be just an aggregation tool for a whole bunch of separate and relevant processes.
Originally Posted by justchat_1
Like I said earlier, it may make sense for RR and CF, etc to interface with the OSDash Client Library directly instead of going through a separate process/abstraction layer.
This Linux Client really only fits the OpenICE model. For Crossplatform FE like OpenMobile, or Revfe, they may want to follow the path that keeps them crossplatform. Which will probably be implementing the Client library directly in their own plugins.
openice osdash git repo
I've created a code repo for the osdash linux client. right now it just has some stub/example code. More to come later. You can check it out of git via:
I've repented a few things I originally planned. I think I will do the client in c++/Qt as either a library or a daemon/dbus-service. I haven't quite decided yet...
git clone http://archive.openice.org/repos/osdashclient
Very cool, Kev! I was talking to OptikalFX about getting around to doing something with OSDash as we'd lost momentum.
I'll take a look at the sample code and come up with some stupid questions to ask.
Yeah, we did lose some momentum. Hopefully we can pick it back up. I'm hella-busy with life and haven't had much time for any off-work-coding.
Originally Posted by Bugbyte
Right now the example code points to the nextabyte server that matt is using to test on. Hopefully we can get the server back up and start testing in real life.