Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: OSDash - FAQs (Frequently Asked Questions)

  1. #1
    Admin. Linux loser.
    Auto Apps:loading...
    Bugbyte's Avatar
    Join Date
    Sep 2004
    Location
    Corning, NY
    Posts
    7,359
    Blog Entries
    2

    OSDash - FAQs (Frequently Asked Questions)

    Frequently asked questions about the OSDash project

    1. What is the OSDash project?

    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. For more information, see this thread or view a visual explanation of what OSDash is.

    2. I don't get it. What is the problem that this solves?

    Traditionally web services used by the various front ends had to be implemented one at a time, sometimes multiple times for each of the different providers. Should any of the service providers change their data structure the FE would require an update before it started working again.

    With OSDash, developers implement each service only a single time and yet have access to dozens of providers. Since the data source is under our control there is no risk of a data source changing its structure. Even if one of the providers does, this can be corrected server side with no adverse effects to the end-user.

    3. Is this project open source?

    Yes and the source code is available from the projects svn servers:
    http://sourceforge.net/projects/openicevis/
    4. How will it work?

    There are 4 parts to the OSDash story: Web Service, Web frontend, Client Library and Platform Specific Implementation.

    The Web Service does all the background work and provides data to the web frontend and the client.

    The Web Frontend is a web page that users can goto to change settings and view data.

    The Client Library is a development tool that runs on the users hardware (a carpc).

    The Platform Specific Implementation is done by your favorite frontend developer. He uses the Client Library to interface with the Web Service and provide pretty, easy to use user interface on your touchscreen.
    5. What front ends use OSDash?

    Currently LinuxICE, openMobile plan on implementing OSDash services but others are welcome. The client library required to access the web service is freely distributable under the LGPL license and can run on any operating system. Source code for the project is all available from the sourceforge project page and implementation guides for any front end will be available on the mp3car forums.

    6. Who is involved with this project?

    This is a crowd sourced project with community members and mp3car contributing ideas, designs, time, and resources to the project.

    7. Where can I get a technical overview of the project? Stuff like architecture, technical documentation and so forth?
    Requirements documents list is here. Check each of the sub-forums for threads on the technical details for the component you are interested in (e.g. the details for the server would be in the server forum)
    8. How can I get involved?

    We definitely need help in all areas but particularly in writing services for front ends to consume. Got an idea for a service? Want to program a service but need an idea? Check out this thread of proposed services and their status.

    9. What type of services are you talking about?

    Check the forum for Web Services under OSDash.

    10. What is the roadmap for this project?

    11. When was this project started?

    The OSDash project was started in December of 2009.

    12. Whose idea was it?

    The idea is based on Open VIS, an extension of the Linux ICE project. See the genesis of this idea by kev000 here.
    Quote Originally Posted by ghettocruzer View Post
    I was gung ho on building a PC [until] just recently. However, between my new phone having internet and GPS and all...and this kit...Im starting to have trouble justfiying it haha.
    Want to:
    -Find out about the new iBug iPad install?
    -Find out about carPC's in just 5 minutes? View the Car PC 101 video

  2. #2
    Admin. Linux loser.
    Auto Apps:loading...
    Bugbyte's Avatar
    Join Date
    Sep 2004
    Location
    Corning, NY
    Posts
    7,359
    Blog Entries
    2
    If you have questions for the FAQ, post them below. We'll fill out the answers as we have time.
    Quote Originally Posted by ghettocruzer View Post
    I was gung ho on building a PC [until] just recently. However, between my new phone having internet and GPS and all...and this kit...Im starting to have trouble justfiying it haha.
    Want to:
    -Find out about the new iBug iPad install?
    -Find out about carPC's in just 5 minutes? View the Car PC 101 video

  3. #3
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    1,783
    I don't get it. What is the problem that this solves?
    Traditionally web services used by the various front ends had to be implemented one at a time, sometimes multiple times for each of the different providers. Should any of the service providers change their data structure the FE would require an update before it started working again.

    With OSDash, developers implement each service only a single time and yet have access to dozens of providers. Since the data source is under our control there is no risk of a data source changing its structure. Even if one of the providers does, this can be corrected server side with no adverse effects to the end-user.

    Is this project open source?
    Yes and the source code is available from the projects svn servers:
    http://sourceforge.net/projects/openicevis/

  4. #4
    licensed to kill - FKA kev000
    Auto Apps:loading...
    tripzero's Avatar
    Join Date
    Aug 2006
    Location
    16.40618, 120.61106
    Posts
    2,494
    4. How will it work?

    There are 4 parts to the OSDash story: Web Service, Web frontend, Client Library and Platform Specific Implementation.

    The Web Service does all the background work and provides data to the web frontend and the client.

    The Web Frontend is a web page that users can goto to change settings and view data.

    The Client Library is a development tool that runs on the users hardware (a carpc).

    The Platform Specific Implementation is done by your favorite frontend developer. He uses the Client Library to interface with the Web Service and provide pretty, easy to use user interface on your touchscreen.
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

  5. #5
    licensed to kill - FKA kev000
    Auto Apps:loading...
    tripzero's Avatar
    Join Date
    Aug 2006
    Location
    16.40618, 120.61106
    Posts
    2,494
    Proposed question: Which frontends use OSDash?
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

  6. #6
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    1,783
    Proposed Answer:
    LinuxICE, openMobile and revFE(?) but others are welcome

  7. #7
    Organic Me
    Auto Apps:loading...
    Heather's Avatar
    Join Date
    Sep 2007
    Location
    Fells Point, Baltimore, MD
    Posts
    1,287
    Blog Entries
    48
    Quote Originally Posted by justchat_1 View Post
    Proposed Answer:
    LinuxICE, openMobile and revFE(?) but others are welcome
    All front ends should be able to use OSDash - this is one of my major expectations of this project.

  8. #8
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    1,783
    Well thats certainly the main goal....

    How about this answer instead:
    Currently LinuxICE, openMobile and revFE(?) but others are welcome. The client library required to access the web service is freely distributable under the LGPL license and can run on any operating system. Source code for the project is all available from the sourceforge project page and implementation guides for any front end will be available on the mp3car forums.

  9. #9
    Organic Me
    Auto Apps:loading...
    Heather's Avatar
    Join Date
    Sep 2007
    Location
    Fells Point, Baltimore, MD
    Posts
    1,287
    Blog Entries
    48
    Quote Originally Posted by justchat_1 View Post
    Well thats certainly the main goal....

    How about this answer instead:
    Currently LinuxICE, openMobile and revFE(?) but others are welcome. The client library required to access the web service is freely distributable under the LGPL license and can run on any operating system. Source code for the project is all available from the sourceforge project page and implementation guides for any front end will be available on the mp3car forums.
    I a thinking, what if we post publicly which front ends are participating, somewhere aside from just this FAQ? This way, perhaps other front ends will look at the list and not see there name there and jump on board?

  10. #10
    licensed to kill - FKA kev000
    Auto Apps:loading...
    tripzero's Avatar
    Join Date
    Aug 2006
    Location
    16.40618, 120.61106
    Posts
    2,494
    Quote Originally Posted by justchat_1 View Post
    Proposed Answer:
    LinuxICE, openMobile and revFE(?) but others are welcome
    Right on. We should probably wait until we have a solid implementation of a web service end-to-end before we claim we use it though .

    I a thinking, what if we post publicly which front ends are participating, somewhere aside from just this FAQ? This way, perhaps other front ends will look at the list and not see there name there and jump on board?
    Make another sticky? "Who Uses OSDash"
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

Page 1 of 2 12 LastLast

Similar Threads

  1. Ok, I read the FAQs but have a few questions.
    By alwaysinsession in forum Newbie
    Replies: 3
    Last Post: 08-16-2007, 06:38 PM
  2. Replies: 6
    Last Post: 05-25-2005, 11:53 AM
  3. Frequently Asked Questions
    By bgoodman in forum The FAQ Emporium
    Replies: 33
    Last Post: 05-03-2005, 06:25 PM
  4. Replies: 5
    Last Post: 04-18-2004, 03:21 PM
  5. Replies: 9
    Last Post: 08-12-2002, 11:50 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •