Command access restriction with areas

[adambajguz]

Is your feature request related to a problem? Please describe.
Suppose Typin is used as a hand-written API client for some API that requires to be authenticated, successful execution of login command will give a user access to more commands, while logout will remove this access.

Describe the solution you'd like
Schema areas or subschemas: we will be able to assign a command to an area/subschema and Typin will be able to restrict access to commands based on this. As programmers, we will be able to use e.g. IAreaSwitcher.

We will probably also need to provide some logic to specify whether to inherit command to child areas. Areas will be a tree structure but one command may be in many areas - co maybe no inheritance to child areas needed - just explicit assign of command to area(s)?

Additional remarks

• Strongly typed areas and strongly typed switcher? a class per area with area parent(s) specification?
• In direct mode areas/dynamic commands are pointless - how to have a simple direct mode and advanced interactive together?