Announcement

Collapse
No announcement yet.

I'm a bit confused...

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • I'm a bit confused...

    Hi,

    i'm a little bit confused at the moment about the current (main) authors of RR.
    I noticed that Anrew(Skippy76) has spend a lot of time and work to RR in the past and now has released a beta version. also i recognized that there where some changes in the past (latest source not available, guino spend less time to RR (which everybody should understand of course, because he was working like crazy on RR and i want to thank him again for his work))
    i know that RR is opensource and everybody could at features by himself. but also i thought guino is/was the mainauthor of RR and he is coordinating the adding of new features to the (official) releases.
    does the current situation mean that there will be more than one version of RR in the future?
    I also spend a little time to RR and of course will do so in the futere (f.e. there where some bugs that had to be cleaned in the phoco integration). but where should i now send my changes guino, skipp76, tim...?????

    could some please enlighten me ???

    thx, hematec

  • #2
    I'd say send them to Guino still, I think Guino should still release the main app (as long as he has time of course). Any version someone else releases should remain a beta version ... I personally will only use a version of RR that has been released by Guino, sorry guys but I trust Guinos code and 90% of the time any issues I have had have been down to myself being stupid, rarely Guinos code.

    My fear is that an unofficial release of the code will become the official and no one will know which version is which.

    Comment


    • #3
      Gobby: Sorry to say, but you maybe behind a few releases.

      Basically, this is the bottom line:

      I've done mods in the past for RR. Generally speaking these mods a 10 or 20 lines of code and the changes are easy to merge in. Guino has allways done the merging.

      Guino is currently taking care of his personal life at the moment. Although he is still working on RR, he does not get to spend much time on it. It was therefore agreed by Guino that I (and a few others) would coordinate in putting our changes into a release (i.e. we take ownership of the code stream for a release).

      The changes have implemented a few new peices of functionality that would be qutie a lot of work to merge.

      The current BETA release WILL be the next official release of RR. At which point the source code / binaries will be passed back to Guino to continue on with.

      Just to complicate things further, a major part of RR (the Exec function that carries out all of the execution of the commands (see the souce code if you want to understand more)) needs redesigning. This redesign is necessary as the function has now reached it's maximum size! (max size for VB). It can be implemented in a far better way but requires substantial work for this to be done. It is likely that we will do this in two stages:

      1) Implement serpate function calls for each command that is executed.
      2) Once the above has been accomplished and released we will then implement this in a class module.

      Back to the BETA. Yes there are bugs in it, not it's not officially released. As with all bETA's it's use at your own risk. It will be an official release once:

      a) The outstanding issues are closed
      b) The functionality works the way people want it to

      I hope this answers some of the forums questions. Remember, it is open source and the best way to continue to make RR as successful as Guino has already made it is to work as a TEAM.

      TEAM WORK: Do you know how to code in VB?
      - Yes? Well maybe you could lend a hand.
      - No? Well maybe you can test things for us and let us know when issues occur.

      Issues WILL occur, but as a TEAM we can find AND solve them.

      That's my 2cc. If people dont' want me to continue adding functionality to RR then please go ahead and let me know (my wife will be more than pleased).

      Andrew (aka Skippy76)

      P.S. If anyone is concerned about my coding abilities.
      - I have two years experience in implementing navigation systems for figther aircraft
      - Two and a half years experience in development of translations and call routing functionality on telephone exchanges.
      - Three years as a validation and verification engineer for SMSCs and SMS routers
      - Currently work as a senior systems engineer for North American wireless carriers (yes, most of the big and little ones).
      06 Volvo XC90
      Use to have installed MII 10000/512Mb/40GB, Lilliput 7", OPUS 90W, Wifi-G PCMCIA, Head Unit Aux adapter, Delorme GPS, XM PCR, Audigy NX, RR
      Car PC downloads: http://carpc.harteveldt.com/

      Comment


      • #4
        Skippy76 I hope you keep working on RR. The only things I can say is great work and keep it up.
        2001 S10 ZR2

        Chucks Skin - to old

        Comment


        • #5
          thanks
          06 Volvo XC90
          Use to have installed MII 10000/512Mb/40GB, Lilliput 7", OPUS 90W, Wifi-G PCMCIA, Head Unit Aux adapter, Delorme GPS, XM PCR, Audigy NX, RR
          Car PC downloads: http://carpc.harteveldt.com/

          Comment


          • #6
            I have to agree, Guino is awsome but so are thousands of others. If you can make a program better then I am behind you

            Comment


            • #7
              Originally posted by skippy76
              Gobby: Sorry to say, but you maybe behind a few releases.

              I'll wait and see what happens, Ideally I would prefer Guino to approve the final releases if possible.

              Comment


              • #8
                A quick throw of my tuppence.

                We want to be careful RR doesn't get too bloated, it is already starting to slow down big time.

                It's great adding all the features but it needs to be in in such a way that if they are not required by individuals then they aren't able to slow the rest of the code down.

                Comment


                • #9
                  Skippy thank you very much for keeping this going!
                  2008 350z GT Installed since April 22nd 2011 - Worklog
                  2000 Protege Installed Since April 2, 2005 - Intel D201GLY|Fusion Brain|ODBPros ODBII|Engenius|GPS Rikaline|Powermate|Motorized Lilli
                  Sound Stage
                  Eclipse|MTX|Infinity

                  Comment


                  • #10
                    Originally posted by Enforcer
                    A quick throw of my tuppence.

                    We want to be careful RR doesn't get too bloated, it is already starting to slow down big time.

                    It's great adding all the features but it needs to be in in such a way that if they are not required by individuals then they aren't able to slow the rest of the code down.


                    As some mp3car members have noticed. RR seemed to be slow in the last couple releases. skippy76 if you are rebuilding the code for RR and converting some features into a class. Also think about possible DLLs that could be referenced from RR as that a user can select possible features and disable features that may slow down RR. DLLs suck in VB but I hope you get the idea. Example, I dont need phoneco or XM SAT. Maybe make it more modular.

                    Just some ideas.
                    Um, I guess this is where you put something witty.WITTY

                    My Web site, in the design stage. http://home.comcast.net/~cstrachn

                    Modified RRSkinEditor http://www.mp3car.com/vbulletin/showthread.php?t=65723

                    Comment


                    • #11
                      If you need a hand with programming i know vb6... and vb.net

                      Comment


                      • #12
                        Originally posted by Enforcer
                        A quick throw of my tuppence.

                        We want to be careful RR doesn't get too bloated, it is already starting to slow down big time.

                        It's great adding all the features but it needs to be in in such a way that if they are not required by individuals then they aren't able to slow the rest of the code down.
                        Skippy - no prob... although sticky might be in order to save answering the same question a million times.

                        Re size / speed - how about having a core app then all the extra functions as add on modules ( and I dont mean DLLs - I mean full modules designed to a standard of some kind )... this way as user only configures those modules they need to load and interact there by reducing the over head... just a thought.

                        If you make this a common standard then others can design modules to be plugged in to the core app.... as Gobby will tell u I like the idea of common standards.

                        EG - XM would never be used by some one in the UK / EU so why load it ?

                        Terran

                        EDIT - I ment to say - if we could also get Gunio to quickly look over each release before it moves from Beta status I think a lot of other will be happy that Gunio has done that ( not that I am saying you cant do it but its a confidence thing if you see what I mean... RR has been coming out from him ( even with contributions from others for some time now )) - plus he has to update his web site each time to allow the autoupdate feature to work.... unless you build in alternitive urls ?

                        T
                        My Project Site

                        Comment


                        • #13
                          I'm hoping to get skippy76's changes and merge them with the main sources today... or I can always send him my recent changes too... the only problem with multiple versions is that it confuses the users... but I don't care.. I'm always happy to get more help with this project..
                          Ride Runner RR's Myspace

                          "Being happy is not about having what you want, it's about wanting what you have."
                          "The best things in life are always free - but that doesn't mean money can't buy you good things."

                          Comment


                          • #14
                            Originally posted by jd2006
                            I have to agree, Guino is awsome but so are thousands of others. If you can make a program better then I am behind you
                            That's my thought, if you can make the program better and it's just as stable (so far so good then by all means man, I am behind you.
                            -Anthony
                            Volvo 850turbo manual | Dell Inspiron 8100 PIII-M 1ghz | 512Mb Ram | SB Extigy | Vision Mobile Media 7" touchscreen | Garmin GPS12 | iPod | Crystal Mobilesound 3way components in kicks | 2xIDQ10

                            Comment


                            • #15
                              Originally posted by ccsnet
                              Re size / speed - how about having a core app then all the extra functions as add on modules ( and I dont mean DLLs - I mean full modules designed to a standard of some kind )... this way as user only configures those modules they need to load and interact there by reducing the over head... just a thought.

                              If you make this a common standard then others can design modules to be plugged in to the core app.... as Gobby will tell u I like the idea of common standards.
                              Thats what Frodo tried with frodocomm.

                              If you use that kind of standardization, you willl have at first define these standards.
                              i allready thought about a plugin-based Front-End because RR supports so much things i never will use (f.e. mappoint).
                              i know RR supports plugins, but i didn't take a look at this before and at the possibilities of this ind of plugin structure.
                              maybe it is possible to redesign RR in that way, that there is more functionality that is allocated in plugins so everybody could choose if use it or not.
                              My thoughts were to have a main-app which handles the skin-part and routes all commands to plugins. So you first all plugins have to "login" to the main-app and tell thecore which commands, labels, indicators,... they provide.
                              So if you want a new feature you simply had to add a plugin and place a skin for this in the skinfolder/add commands in a skin. The plugin "tells" the core which features will be provided and the main app can forward these commands to the plugin...if no plugin is installed, then these skin-commands simply have no effects...
                              by that way u could have a lean RR with only the features u want to use.

                              hematec

                              Comment

                              Working...
                              X