I've created a new Google Code project for TChromeTabs. You can find it here: http://code.google.com/p/delphi-chrome-tabs/source/checkout. This is my first open source project, so I would appreciate any advise that you think might be useful.

-
I've created a new Google Code project for TChromeTabs. You can find it here: http://code.google.com/p/delphi-chrome-tabs/source/checkout. This is my first open source project, so I would appreciate any advise that you think might be useful.
http://code.google.com/p/delphi-chrome-tabs/source/checkout

Comments

  1. Warren PostmaDecember 10, 2012 at 11:24 AM

    My big advice: Use Mercurial, not subversion! :-)

    ReplyDelete
  2. Colin JohnsunDecember 10, 2012 at 6:12 PM

    What about Git? and hosting on Github or Bitbucket?

    ReplyDelete
  3. Krom SternDecember 10, 2012 at 9:08 PM

    Seriously, is there a good comparison chart between SVN/Hg/Git pros and cons? Cos I keep hearing Git here and Hg there, but the only minor trouble with SVN is branches merge..

    ReplyDelete
  4. Colin JohnsunDecember 10, 2012 at 10:22 PM

    We use SVN branches at work and it provides my team-mates endless hours of frustration. Everything from tree conflicts to missing meta-data that keep on stopping branches from merging. Since I'm the only one using git, I avoid this problem by letting git do the merging locally and all I do is check in the merged code back into the SVN repo. No issues.

    ReplyDelete
  5. Warren PostmaDecember 11, 2012 at 7:35 AM

    Here's the problem with Subversion; On a team of equals where everyone is happy comitting and working on a rolling basis (I get all your commits and you get all mine), Subversion works okay.  The Hg and Git advantage boils down to this single pearl of wisdom: "I should be able to commit code and let you look at it, and when you decide you want it, you should add my code to yours, and when you decide you want it back out, you should be able to do that too, and all your decisions should be yours to make, and not be forced on you by your choice of version control tool".     In Mercurial and Git for instance we have something called a "pull request", which simply means "Hey Paul I fixed that bug in your code, here's my fix".  Instead of Paul granting me commit access he reviews and pulls fixes, decides the fix is good, and then updates the master central copy. He becomes the project leader again, instead of just one more comitter.  It's for Paul's sake that I suggest he lead his own project and have no other direct committers.   Subversion is just CVS done better, it's still a 1970s version control system at heart.  Git is Linus Torvald's swiss-army-knife tool, and Mercurial is comparable but far easier to learn and use.  A good comparison would be Git is like the C++/MFC/VisualStudio tool combination, whereas Mercurial is like Delphi, simple, powerful, and fast.

    ReplyDelete
  6. Sébastien ParadisDecember 12, 2012 at 8:44 AM

    Tested: nice work but still a few bugs :)

    ReplyDelete
  7. Paul ThorntonDecember 12, 2012 at 8:46 AM

    Sébastien Paradis Thanks ... would be nice if you could tell me what the bugs are :o) I'm working on the code now.

    ReplyDelete
  8. Baoquan ZuoDecember 13, 2012 at 8:20 AM

    Paul Thornton  Hi, Paul, It looks very impressive. If you wanna document the library some day, it is our pleasure to invite you to join our Open Source Project Donation Program. http://www.devjetsoftware.com/news/ann-documentation-insight-donation-program-for-open-source-projects/

    ReplyDelete
  9. Paul ThorntonDecember 13, 2012 at 10:41 AM

    Baoquan Zuo Thanks, that's very cool of you. I'll apply now :)

    ReplyDelete
  10. Roberio PracianoDecember 17, 2012 at 12:49 AM

    Great job

    ReplyDelete

Post a Comment