Re: [ccmtools-devel] library renaming

[Teiniker E. <ego...@tu...>]

Hi Leif!

Quoting Leif Johnson <le...@am...>:

> I've made the following name(space) changes in my local copy of the CCM
> Tools, in both the environment files and the component templates :
>
>   localComponents --> LocalComponents
>   localTransaction --> LocalTransaction
>   remoteComponents --> RemoteComponents
>
> I know, it's nitpicky, but I thought it was more consistent with our
> capitalization so far (SmartPtr, CCM_Utils, etc.).
>
> This would break all kinds of compatibility, however, between old
> environments and new components, so I wanted to find out if I should
> abandon these changes or go ahead and check them in. Let me know.
> Cheers !

So, if the tests are running after this refactoring, please check it in.
I will change the remote generator in that way too.

There is a naming convention that (in my opinion) can also be changed:
   CCM_Test -> test
All the generated directories start with CCM_*, while the manually written or
modified directories should have different names like src and test.
If we package a component, we can remove all the CCM_* directories because ther
is no bussiness or test code contained in. Thus, all CCM_* directories can be
completely generated from IDL3 files.
What do you think about that?

:-) Egon