Alternative Design 1 for HyperApp

Instead of splitting HyperApp into several smaller components, a BigHyperApp can also be definedto perform the same functions. However, this makes it harder to reuse, such as in the following two situations:

When we need a different mechanism to access the destination nodes.
When we want the hypertext to be displayed in a different ways.

In either or both of the above conditions, a new subclass of BigHyperApp is needed. Two variants make four combinations, so four new subclasses are needed to handle all different situations. However, if LinkAccessor and Renderer are factored out, only one subclass of LinkAccessor and one sublcass of Renderer are needed.