New project name

Topics: Developer Forum
Aug 17, 2006 at 5:56 PM

In case you haven't noticed there is a slight error in the name of this project. It should be 'CustomBorderForm' but by mistake the CodePlex team entered 'CustomerBorderForm'. I've contacted them, but there is no way to change project name in Team System once it was created. But we were given unique opportunity to recreate the project with a new name. We don't have much content so this won't be a big problem.

However I've decided to postpone this and ask for your opinion on the name for this project.

Current name (CustomBorderForm) is simply the name of the main class from my article. Personally, I like the name 'Skinned Forms' used by Codeable.
(, as it targets the area I started exploring in the 0.5 release.

So tell me what do you think?

Aug 18, 2006 at 9:31 AM
Hi kobush,

Well, when I created my own dll assembly based on your code, I named it Lizard just because they change their skin.

I still think it would be a great name for this project...
Aug 22, 2006 at 6:05 AM
I personally don't have any good ideas as far as a title is concerned. I just think it is always best to title projects/solutions/assemblies with the most meaningful names possible. I prefer branding by company not by product.

I mean: What did you google to find kobush in the first place?

Just my thoughts.
Aug 22, 2006 at 9:55 PM
Good point here from Codeable. I've just checked the statistics on my articles.

There is indeed a lot of queries like:
drawing image border
custom form border
form without border
own title bar button

But some refer to technical details found in the article like:
window non client area
wmncpaint, wmnccalcsize

I was also contacted today by someone regarding few issues with the code. When asked I was told he found it by searching for 'custom forms' in google.

But still I think Lizard is pretty cool name. I haven't found any other .NET project with this name. I think we can still get good search hits by providing clear description for the project. I already notice increased interest here on CodePlex than when it existed only on my blog.

So at this point I think it should be either 'SkinnedForms' or project 'Lizard'.

Aug 23, 2006 at 6:36 AM
We can always use the brand name, and let the motto be the description.


Aug 23, 2006 at 6:38 AM
Damn thing! they need a confirm, preview, or something.

Something like:

The perfect motto

Aug 23, 2006 at 9:44 AM
How about:

<i>Skinable Applications</i>
Sep 7, 2006 at 5:53 PM
I've been lurking for a while, following this cool project, and thought I would jump in and add a few bits to this discussion.

I'm actually not too fond of "Lizard." It sounds....strange to me, and generally has a negative connotation in my opnion. If we're conveying something that changes skin, I would prefer "Chameleon," but that is harder to spell, so perhaps it would be harder for people to find?

I’m often a fan of projects whose names mean what they say: “DotNetSkin” for example is a name which immediately makes it clear to me what it does. Granted, it’s already taken, but you see what I mean. Other competitors on the space are “DirectSkin” and "Skin Crafter" - again, more skin references. Maybe the good “skin” names are already taken, in which case you are probably right to think outside the box and use an animal reference. Or maybe: “Skin Shifter” perhaps? isn’t taken. :)

Sep 11, 2006 at 5:41 PM
Should we move into this new project in CodePlex kobush?

Sep 11, 2006 at 10:12 PM
I would still like to settle some things before moving to new space. Like the project license for example. Let's continue to work in this space at least until our next release.

BTW. How do you like the changes that Cdamez has made so far? Is this the direction you were thinking?
Sep 12, 2006 at 10:06 AM
I think it is a good step forward and it is clearer on how the overall library is structured.

I did my own implementation of it a while ago and I would need to share it with you. Let me know how I should do so we could compare both ways and peek whatever is the best in both of them.

Now, another point I think we should definitively make a decision would be what are the objectives we would share on this project. From my point of view, we should start by giving a simple windows skinning library free and easy to use for a developer.

But what would be next?
We need to agree on which would be our next steps so we make sure we design correctly the assemblies to support future improvements and extended scope and avoid refarctoring or reengineering our code.