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.

Plastic SCM 2.0 pre

Tuesday, August 21, 2007 Dave 1 Comments

We're currently working on several open projects which will all end up creating the upcoming Plastic SCM 2.0 release.
Some of the changes and new features have been already highlighted weeks ago (what's next).
The feature I'm currently working on is the new GUI. We're about to start using it internally this week, so I expect some usability feedback coming from the team. The new appearance introduces a big change from what you've previously seen in Plastic, trying to hit several targets:

- Create a better interface to handle multiple data views
- Design it to make it attractive to users
- Simplify retrieving information from the tool, making most common operations easier than before
- Open up new integration possibilities with third party tools and even new Codice developments creating some sort of virtual canvas to place windows.

The results of a still really pre-release version can be watched here:

Hope you liked it and stay tuned for updates!

1 comment:

  1. The new interface looks quite appealing with a lot of potential :)
    I have a small concern though... While the "SCM desktop" concept has quite a lot of possibilities, it might be confusing for the users, hiding certain information that might take quite time to be found in the canvas. May I suggest to add some kind of navigator view or zoom in/out features to it? I've seen that in graphic design and modeling (UML) tools. That kind of pseudo-infinite canvas works great with graphic elements, but don't know well how it will behave with GUI elements.

    In any case, best of luck for you with the next release and the usability tests of this new GUI. According to the previous releases, I'm sure you'll find the best way to implement it :)