Wonderland modules

[Bernard]

Continuing from thread http://groups.google.com/group/openwonderland/browse_thread/thread/794168bf2ce2b8a8

I really like the idea of having configurations.

My concern over the increase of modules is as follows:

1) The more modules we include the more likely it is that we have to
download the whole binary even if there's a small non-functional fix
(such as a typo) in one of the modules, which kinda violates the
principle of having modules in the first place.

2) The more modules in the binary, the more the client has to
download. This increases the initial download time, the amount of heap
required by the client, and the amount of cache required by the
client.

Personally, I'd like to see a minimal configuration that could be
extended as required. For example, when we use MiRTLE we only need the
following core modules:

affordances
animationbase
appbase
artimport
asset-meter
audiomanager
avatarbase
avatarbaseart
celleditor
cellselection
content-repository
context-menu
core-help
darkstar
darkstar-api
hud
jmecolladaloader
kmzloader
mtgloader
palette
pdfviewer
presencemanager
quick-reference
security
security-groups
security-session-noauth
servermanager
sharedstate
snapshot-manager
textchat
viewproperties
voicebridge
webdav

regards

Bernard