Page Comparison

...

QSim is going to be the default MobSim. QSimConfigGroup is going to become a "normal" default config group with the usual syntax. The current "simulation", which is the QueueSimulation, will be renamed and put to the same status as the JDEQSim.

...

We are not too happy about the current way custom scenario elements are added (by class), which seems to be a slight misuse of the Java class concept: For instance, if one had added an X, and wanted to add another X later (with a special, different meaning), then one wouldn't be able to use the same class for that (or even a subclass). We would prefer a simpler, map-like interface where an Object can be added under a String key. 

...

We think that semantically conflicting Config parameters should be reported by a ConsistencyChecker, but not automatically adjust themselves to the nearest permissible point, or similar. Of course, one should try to design config options as orthogonal as possible.

...

Contribs or other extensions can access their custom config groups like this:

OTFVisConfigGroup oc = (OTFVisConfigGroup) config.getModule("otfvis");

Existing config groups which configure things which are not part of the core are removed and do not get a custom accessor method.

...