Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Announcing the method history

Thursday, December 23, 2010 Pablo Santos 0 Comments

We’re very happy to announce our newest Plastic SCM release (3.0.13) including one of the features we’re most proud of: method-based history!

You can now select a method within Visual Studio, right click to show the context menu, and select “method history”. Plastic SCM will go through the file history and analyze the evolution of that specific method!!


We have the impression that 95% of the time that you go through a file’s history, the reason is to check a specific method. That’s why we came up with this new feature. In fact “method history” is one of those things we’ve always wanted to implement, but of course we had to cover the SCM basics first. But, finally, it is here!

“Method history” is our first step into a “programming language aware SCM”, a path we will be walking during the next months. We have a bunch of ideas to combine the “method history” parsing technology with XDiff and XMerge, to come up with a new line of Plastic SCM functionality in 2011.

Action, please!

First, here’s a short explanation of what “method history” is about, with graphics:

Plastic will look for the method in every revision of the item. Right now the search has some limitations (remember this is beta software):
  • We only parse C# code (Java is ready but not deployed; VB and C++ will be next)
  • We don’t consider constructors yet (but we’re on it!)
  • We locate the method by name: next step will be finding renames too!.

    A few screenshots to see it in action:


    And finally a video (available in HD!):

    How to try

    Simple: download the new release and install the Visual Studio "package" (not SCC, the newest package) and simply give it a try.

    What's next?

    As I mentioned, a ton of new stuff:
  • Being able to invoke "methodhistory" from the "annotate" views in the GUI
  • Eclipse support
  • Multiple language support + improved C#
  • Tracking refactored (moved) code between files... (wow! yes, we're on it! :P)

    Pablo Santos
    I'm the CTO and Founder at Códice.
    I've been leading Plastic SCM since 2005. My passion is helping teams work better through version control.
    I had the opportunity to see teams from many different industries at work while I helped them improving their version control practices.
    I really enjoy teaching (I've been a University professor for 6+ years) and sharing my experience in talks and articles.
    And I love simple code. You can reach me at @psluaces.
  • 0 comentarios: