Reflector service locators and app roots

[michaelelfial]

The need for these features (or a single one that can solve both problems) comes from the need to back the development of more complex apps with more granular service location facilities. A good example are parts of the app in which the components communicate predominantly between themselves - ie. inside that part and much less on global app level and with other parts. However, other considerations also exist - for instance it will be useful to have separate window trees growing from certain app parts. A good example can be seen in a document-like apps - apps that work with specific data sets that can be seen as a kind of a document. Such an app can be potentially implemented to open more than one data set using the same classes and structure for each of them. So, an app like this will have the same kind of constructs holding the different sets just like several opened documents. Obviously each structure will have to use services within itself most of the time and this also corresponds to its windows and their structure - which brings us to the idea to have service location and part/branch window management implemented as one integrated unit.

Definition

Service locator Reflector

Is an attachable to a window (and possible to other construction elements) service locator which can be easily managed to provide services relevant to the structure under it. The process of service location will be "reflected" by it instead of reaching the app's root class.

App roots

Classes that look like stripped down app and support window hierarchies for specific app parts which need higher level of separation from the rest of the app.