-The new user, fed up with the default key bindings and eager to just
-quickly configure Ion to his liking may question the reasons for
-exposing the ''heavy'' internal OO structure in the scripting and
-configuration interface. I'm not the one to blame him for that.
-Sure it would be faster to configure Ion to everyone's liking
-if a simpler binding configuration interface was provided. Such an
-interface would, however, also be far more limited and make writing
-extensions more complicated and the advantages from using a real
-scripting language would be partly lost. One more advantage from
-a rich scripting and configuration interface is that it allows
-implementing scripts to read alternate configuration file formats,
-ones that could be, for example, modified by external configuration tools.
+Back in this document, first in chapter <A HREF="node3.html#chap:prelim">2</A> some key
+concepts and relations are explained. These include the module system,
+and Ion's object (or ``region'') and class hierarchies. While it may
+not be necessary to study the latter for basic copy-paste modifications
+of configuration files - for that you should not really need this
+manual either - it is, however, essential to for more extensive
+customisation, due to the semi-object-oriented nature of most of
+Ion's scripting interface. Knowing the different object types also
+helps dealing with the different binding ``contexts'' (see
+Section <A HREF="node4.html#sec:bindings">3.3</A>) that to some extent mirror these classes.