[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: Let's discuss the name for the KDevelop Platform (was The name of
From:       David Nolden <david.nolden () art-master ! de>
Date:       2007-01-21 18:12:58
Message-ID: 200701211912.59087.david.nolden () art-master ! de
[Download RAW message or body]

Am Sonntag, 21. Januar 2007 18:37 schrieb Alexander Dymo:
> > Thus, I suggest to rename Koncrete back to KDevelop Platform, namespace
> > the lib/ classes with KDevPlatform:: and make one KDevelop 4 that rocks,
> > instead of two different KDevelops that are merely sufficient.
>
> Ok, there're several propositions so far:
> 1) what we have now
> namespace: Koncrete
> module in trunk/KDE: koncrete
>
> 2) Jakob's
> namespace: KDevPlatform
> module in trunk/KDE: ? (most likely kdevplatform, right?)
>
> 3) Roberto's
> namespace: none, just KDev prefix
> module in trunk: ?
>
> Other ideas were:
> kdevbase and kdevelopbase.
>
> What do people think?

I think "Koncrete" is a bit confusing, KDevPlatform is more logical, but it 
looks a bit too long.

What about a namespace called "KDev"?
KDev::PluginController is great to read and easy to write.

Module kdevplatform.

My second vote would be KDevPlatform. It's just more logical. :)

Koncrete would probably be acceptable too once you get used to it, though a 
message on the list that says "The new name of the kdevelop-platform is 
Koncrete, it will contain ... and be used by ..." would have helped getting 
used to it.

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]