make sure defining modules doesn't have side effects

[nilclass]

Right now defineModule calls the builder immediately, storing the module instance in an object. Once loadModule is called, the instance gets added to the remoteStorage object, and access is claimed on the corresponding paths. One reason to call the builder immediately within defineModule, is that this way module information (such as it's dataHints) is available without loading the module (which IMHO should be referred to as enabling the module, as it doesn't really load anything - the code has to be loaded already).

Now this brings trouble when the module wants to do initialization, that involves data. For example the calendar module calls privateBaseClient.sync('/'). This brings two problems:

1. in this specific case, this creates an empty directory node "calendar/", which confuses my tests
2. data is being accessed without claiming access to the directory. In reality this line probably won't do anything, because at the point where the module is defined, access cannot have been claimed, unless the user was just reloading the page, being connected already.

I can think of two ways to solve this:

1. introduce a module initializer, that is called once the module is loaded
2. only call the builder, when loading a module.

I prefer (1). Any thoughts on naming? initialize? onload? Anyway, it probably shouldn't be part of the exports but an additional key to the module's definition.

[nilclass]

The issue referenced here should have been #61: ef1df8f

[nilclass]

This issue may have become obsolete due to latest rework of loadModule. But I need to think about that a while longer...

[nilclass]

I consider this obsolete now. In case things go wrong, let's rather open another issue.