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.

SemanticMerge goes Visual

Wednesday, July 24, 2013 Pablo Santos , 0 Comments

Edit:Thanks to Scott Hanselman and Jon Skeet for sharing the launch on Twitter.

Here we are, releasing again! Doing our best to follow the rule of “release early, release often”.

Today we’re publishing our latest feature in SemanticMerge: the “Visual Merge”. And since picture is worth a thousand words… here you are:

We’ve also added “difference rendering” to the SemanticDiff tool, so it is possible to use the new visual functionality not only during merge but also while looking for differences, which is a much more common operation:

You can download SemanticMerge, including Visual Merge and Visual Diff at www.semanticmerge.com. It is available for C#, Java, Vb.net and soon it will support C and JavaScript too. Don’t forget to follow us @semanticmerge


The full story behind visual conflict rendering

At the very beginning we explained semantic with diagrams like this:

We wanted to explain how something as complex as splitting a class into two different ones in parallel could be easily merged by SemanticMerge. Using figures (and Visio) was the better way we had.

Soon we started thinking on how cool it would be to teach Semantic to render the conflicts...

It is all about the icons

If you ever used SemanticMerge or if you visited the website then you’ve seen the way in which we render the conflicts:

As you can see each method in conflict is decorated with icons representing the type of change: “c” stands for changed, “m” for moved, “d” deleted and “a” added (we also use “r” for renamed as a special “moved” case).

Icons on the left mean differences with “source contributor” and the ones on the right mean differences with the “destination contributor” considering contributors as in the following picture:

The whole idea of putting the icons on the left and the right of the method came from this graphic (again powered by Visio):

Hence, when a method in the shape in the middle (ancestor or base) has icons at both sides it means it has a conflict. If it only has one icon it means it only has changes in one of the two contributors, so the merge will be automatic, and if it has no icons it means it was unchanged.

This is the idea behind the entire GUI and as you can see now, the originally Visio-drawn concept grew up to become a full GUI.

Some VisualMerge images

These are some of the merges you can display if you just install SemanticMerge and go to the samples directory.

Divergent move

This is the “Socket Deeper” example, in C# and rendering “hiding unchanged nodes” which greatly simplifies the entire graphic:

Group unchanged

Now an example, this time in Java, grouping unchanged parts:

The State of the Art of Merge Technology

We’ve recently posted what can be currently achieved chaining SemanticMerge into an advanced merge toolchain, which maybe is somehint you’re interested on :P

What’s next?

Stay tuned because next week we will come up with a top request in our UserVoice :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: