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.

Talking about SCM in Dr.Dobb's Portal

Monday, July 31, 2006 Pablo Santos 2 Comments

A couple of days ago, DDJ finally published my article about SCM in small shops. Is something I wrote long ago, talking about my experiences in my previous company, where we developed ERP software.
I was alredy very focused on SCM, in fact we were already planning starting up this company. Codice Software's first target was creating a product capable of solving configuration management problems from small to big companies at an affordable cost, just fixing some of the big issues I mention at DDJ's.
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.

2 comentarios:

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.

Image diff

Sunday, July 23, 2006 Dave 1 Comments

I was just told that subversion had a nice extension to diff images capable of blending, so I decided to get something running for plastic. Here are some shots:



1 comentarios:

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.

Some C# coding: semaphores

Sunday, July 23, 2006 Pablo Santos 3 Comments

AFAIK there is no Semaphore implementation in .NET. Today I needed a semaphore to implement some of the new functionality of a new subsystem (more on this later this week).

I played a little bit with it and here it is the tiny semaphore C# code. I wonder if is correct...


class Semaphore
{
object mLock = new object();
long mCount = 0;

void Enter()
{
lock( mLock )
{
while( mCount == 0 )
{
Monitor.Wait(mLock);
}
--mCount;
}
}

void Release()
{
lock( mLock )
{
++mCount;
Monitor.Pulse(mLock);
}
}
}

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.

3 comentarios:

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.

Differences on version tree

Tuesday, July 11, 2006 Dave 0 Comments


A long awainted one, being able to show differences by marking two revisions in the 3D tree, got finally in. Here is the shot.

0 comentarios:

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.

Visual Studio and forms resources

Tuesday, July 11, 2006 Dave 0 Comments


This is one of those "undocumented" and curious behavoirs of visual studio. To begin with, VS 2003 creates two different files to define a winform, one .cs, one .resx containing the resources. How these resources get compiled into the executable was kind of obscure to me, resulting that, in normal conditions, resources are prefixed with the namespace of the winform. Nothing new, uh?

But here comes the surprise: not in all cases. We had two forms that where getting their resources compiled with the default namespace of the project instead of the namespace of the form, causing a resource load exception, of course.

Everything becomes dark when one tries to find where this behavoir is defined, as no property defines that looks minimally related.

The problem was that these two forms had an enumeration declared before the form class in the .cs file


public namespace samplenamespace
{
public enum sdfsdf {}

public class MyForm: System.Windows.Forms.Form {}

}


Visual studio does warn you that the first element in the class
file should be the form. Indeed, if you declare a different class before the
form class, the designer stops drawing the form, and tells you about it, but
with the enum, nothing is advised. The only effect is it will prefix
resources in a different (usually wrong) way.

0 comentarios:

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 under Windows Vista

Monday, July 03, 2006 Daniel Peñalba 1 Comments

We have installed a Windows Vista Beta 2 version, and have been testing our software under this operating system. The resutl have been successfully, except running the server as a Windows service. We will have to do some changes to obtain a 100% of compatibility.

Here is a screenshot:


Dani Peñalba
Yes! I was the first employee to join Codice!
I own the record in number of check-ins to the Plastic repository. And you can find me working on every single area of Plastic.
I'm also a professional guitar player and I like scuba diving, too. You can reach me at @danipen00.

1 comentarios: