rksm/LivelyKernel — comment on commit baaa34762ea5b37da9175a107007506ab96c872a
File:  line 0
By rksm:

No, this is not about the ErrorStackViewer. I agree that this should go in a separate module. Thanks for doing that.

What I want to have is a "top-level" module that will pull together the dependencies of a "sub-system". The required modules

```js
lively.Helper', 'lively.ide.SystemCodeBrowser', 'lively.ide.LocalBrowser', 'lively.ide.VersionTools'
```

will load everything that is necessary to use the SystemCodeBrowser and other tools, you do not have to do this manually if you just want to ensure that those tools are loaded. And in WW we require `lively.ide` at several places. Also concerning name convention: I agree, consistency is important and naming top-level modules in lowercase is something that we do in multiple places, e.g. for `lively.morphic`. I.e. normal module names upper-case, top-level modules lower-case. And top-level modules should not do much besides pulling requirements together (maybe form a little interface like e.g. `lively.ide.browse` but not more).