Developer forum

I've heard the versioning request from many others, so I think we should see if we could improve something here.
 

About CustomerCareCenter, this module only made it to beta but was then secluded, and we made a completely new module, CustomerCenter. Only in special cases do we allow people to use beta modules, but we always reserve the right to make any changes as we see fit during the beta period. So one point could be made here: Never use beta modules API.

Another point is, that using using software without permission, which is the typical case with beta modules, since they are rarely installed,  is - well - piracy. Anothier reason not to do so.

So...

where can we see what Module corresponds to what Namespace ???

so we can track what namespaces from the API we can use and what cant we use

ONE MORE think to add as DESCRIPTION with the API, because with the lack of documentation for the API we are programming with our eyes shut regarding what can and can't use.

without that correct documentation, we can't even discuss the 'piracy' issue.

Should we ask if we can use a particularly namespace, if it's beta or available to use ...

you saw yesterday Lars how we do the programming, navigating in the intellisence and try to find out the best solution, and you also know that using only that, we can't see any differences (beta or non-beta)

.

Except from core features like TemplateV2, Database, PageView, Base, Security, and so on, everything in the API is related to a module, and most commonly is prefixed by the ModuleSystemName. In the majority of cases, the API represent what the developers found the need for during the development of the specific module, and not what custom module developers might need in order to complete modules based on the API - we have the feature request forum to serve this purpose.

I see where thread is going, and I know your point of view to this, but I think it would be interesting to hear from others how they manage without the documentation. What techniques are you using and such.

Of cause I have the opportunity to follow the development of the API at close range, but I always find it very interesting the get the new build, exploring the API and see how much I can tweak it.

But whenever you're in doubt or have questions, or if you need someone to throw the ball at when analyzing a new module or features you need to develop, you know you can always create a thread here, and we'll help you as good as we can.