Today's in-car computing experience is centered around the device -the car pc. Software application front ends such as Linux ICE, Ride Runner, Centrafuse and so forth are loaded on the pc and configured for the hardware. Plug-ins written for one front end are often platform or even front-end specific. This limits both usefulness of the plug-in and growth of the car pc hobby.
In addition, the full potential of connecting the car to the web is not realized. While in-car connectivity is not prevalent today, the cost of that capability will continue to fall in the near future allowing for near continuous internet access from the car pc.
The OSDash project is a project to build plug-ins as services that can be accessed by any front end through an open source and standardized interface and methods. It consists of a client that runs on the pc and a server that provides access to web services that run out on the web. In addition, a web-based configuration tool is used to control which services are available and how they will work.
This architecture allows any car pc that runs the client to access the services and use them in the front end. Developers can write them once and make them accessible to all front ends while front-end enthusiasts can integrate them into the program of their choice. Freely, transparently, and openly.
Didn't follow that explanation? Check the "OSDash visual explanation for non-technical types"
For FAQs about the OSDash project, see this thread
Edit: link added.
Want to:Originally Posted by ghettocruzer
-Find out about the new iBug iPad install?
-Find out about carPC's in just 5 minutes? View the Car PC 101 video
Where's the link??
In all seriousness, I'm excited about this. I think that this is a step in the right direction to getting an information provider interface standardized, so we don't have so many people duplicating the same work over and over again for each individual frontend.
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks