Announcement

Collapse
No announcement yet.

OSDash - A visual explanation for non-techies

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • OSDash - A visual explanation for non-techies

    A lot of people don't seem to 'get' what OSDash is about. So, I created this visual explanation of what the OSDash project is supposed to do for non-technical audiences.















    Originally posted by ghettocruzer
    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
    Just gotta say...Thats Awesome!

    Comment


    • #3
      Very awesome! It captures the idea well and is funny and entertaining at the same time.
      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.

      Comment


      • #4
        Bugbyte... you have too much free time, and are WAY too creative for your own good. Very good excellent explanation, very easy to understand.
        "stop with the REINSTALLS, what do you think we got some lame-o installer!!!" - mitchjs
        RevFE
        My Shop

        Comment


        • #5
          Bugbyte, thank you for this explanation, but why not just use Java? This sounds like pretty much the same reason why Java was created

          Comment


          • #6
            ummm ..... disturbing ....

            good driving skills 9 - 3 o'clock position
            HOWEVER!!!! He's not wearing his seat belt!
            I'm still trying to finger out the punk ...

            Comment


            • #8
              Originally posted by Ryven View Post
              Bugbyte, thank you for this explanation, but why not just use Java? This sounds like pretty much the same reason why Java was created
              Simple answer: None of the osdash developers like Java.

              Long answer: The reasoning has more to do with familiarity of the developers than actual technical reasons. Not to mention many of the existing frontends are .NET based (CF and OM for just a few) so they can share the same tools as the web services for generating client code, etc. It is also possible for c/c++ to embed mono and use any client assemblies in .NET. These are well known features for the developers and those same features are a big question mark if Java can do that. It probably can, but again, if you are going to use a language with equal features, you pick the devil you know rather than the one you don't

              cheers,
              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.

              Comment


              • #9
                Ah, thanks, Trip. That makes sense

                Comment


                • #10
                  Plus OS Dash is not precisely an application. It is service oriented. The service runs on a separate computer, usually at a web address. While it can perform some things that are like applications, it isn't exactly an app.

                  Need to look up a PID code? You could write an OSDash service for that. Want to know the location of your car? You could write an OSDash service for that. Want to know the current voltage of the battery? You could write an OSDash service for that.

                  You can write the services in pretty much an language you want. It's not so important that they can execute cross-platform. It's more that you want them to *communicate* with all platforms.
                  Originally posted by ghettocruzer
                  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

                  Comment


                  • #11
                    Of course if you really dig into things you realize the only change you have made is from:
                    a developer creating a plugin that interacts with a web service

                    to:
                    a developer creating a plugin that interacts with an osdash service that interacts with a web service

                    Minor savings in time, additional layer of abstraction, additional potential point of failure. When you deal with server localization you also have a loss in speed and increase in latency. For front ends which have cross-platform plugins, there really aren't any advantages to 90% of the services offered. Then we add in that quite a few providers (facebook and twitter come to mind) don't allow mitm (man in the middle) services to handle user credentials or cache any data which completely rules them out as osdash services.

                    Not saying there isn't that 10%...mainly remote access or online data storage...just that almost all of the original ideas for osdash services fall into the above.
                    openMobile - An open source C# Front End (why choose openMobile?)
                    - Always Recruiting Developers -
                    Like what you see? Donations are always welcome

                    Comment


                    • #12
                      Interesting, thanks for the explanation. I just don't like this "move back to mainframes", PC "computers getting dumber like terminals", that the whole idea looks like. But if it works, hey, you can't argue with that. Good luck.
                      Worklogs: 08 Sequoia Platinum Carputer (In Progress!)
                      Skin: MetroSex on the Beach preview

                      07 Infiniti Fx35 (done!) & 06 Infiniti M35 (gone...)

                      Comment


                      • #13
                        Originally posted by justchat_1 View Post
                        Of course if you really dig into things you realize the only change you have made is from:
                        a developer creating a plugin that interacts with a web service

                        to:
                        a developer creating a plugin that interacts with an osdash service that interacts with a web service
                        Right. The important point that isn't captured there is that the services in OSDash are stored on the web.

                        The OSDash model shouldn't be considered a monolithic replacement for plugins. It isn't. It's more of a plug-in of sorts itself. And, it's good for some things, but not other things.

                        For example, you can make a plug-in for your car pc that will read from the open source file of car PIDs for OBDII. However, as new cars are added, you'll need to update the file for your FE. OSDash could read the updated file from the web as a service, requiring only the web file to be updated a single time. Additional features of the service might suggest ways to troubleshoot the issue by finding posts in forums related to the trouble code.

                        On the other hand, it wouldn't make sense for OSDash to send real time data from your engine to a web file. That's something that is more effectively handled by a plug-in in your FE or by a stand alone logging program.
                        Originally posted by ghettocruzer
                        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

                        Comment


                        • #14
                          So:
                          OSDash could be more of a service that is relayed to users in-dash systems or to other vendors.

                          It would make sense if OSDash were a web service and all FEs or even just your browser could access. And in reverse, it could accept your data that is being logged by your in-dash.

                          Here is a link that was listed in the CF plug-in contest thread (I think that is where I found it)
                          To get some ideas rolling: web APIs

                          A standard example:
                          Using the OBD data as an example you could keep track of speed, mileage and general maintenance of your fleet vehicles. Continuing with fleet vehicles you could also tag their gps to make sure they are busy bees instead of hot dog shop junkies.

                          If I were to take this to the dealer level, I could keep an eye on your regular maintenance and send out those friendly 3,oookm oil change post cards. Or even have your parts waiting or at least in transit to dealer since they have error codes that could clue them in before your car even reaches the mechanic / dealer by tow truck.

                          Other example:
                          The movie database idea that just came up.

                          Where would I go with this?
                          * come up with a list of basic services that could provided by the server
                          * come up with a list of services that could be pushed from the in-dash to the server
                          * get people on board to create a plug-ins for the various FEs
                          * find data supplier services to come on-board so that you can provide more server based services

                          ... Still need to think about this some more ...

                          Comment


                          • #15
                            Originally posted by SapporoGuy View Post
                            * find data supplier services to come on-board so that you can provide more server based services
                            Like brought up in the movies thread...this is where you will hit problems. Supplying data costs money (for server maintenance, bandwidth, developer time, etc)...theres really no incentive for a data provider to use OSDash-it costs them money with no return. Which is why in many cases OSDash type proxies are explicitly banned by their TOS.
                            openMobile - An open source C# Front End (why choose openMobile?)
                            - Always Recruiting Developers -
                            Like what you see? Donations are always welcome

                            Comment

                            Working...
                            X