//A view within the UI, featuring some component of relevance to »the model«.//
While any UI is comprised of numerous widgets acting as //view of something,// only some of those views play the prominent role to act as //building block component// of the user interface.
Such UI component views exhibit some substantial traits
@@ -2764,7 +2764,7 @@ Here, //Allocation// means
* to determine the hosting location
* possibly to instantiate and register a new instance
* and finally to configure that instance for the desired role
-The classical example to verify this definition is the //allocation of viewers:// when starting playback of a new media item, we "need a viewer" to show it. But we can not just create yet another viewer window -- rather we need to allocate one of the possible "viewer slots". In fact this is a configurable property of the UI layout employed; sometimes some people need the limitation to one single viewer entity (which might even be external, routed to a beamer or monitor), while other ones request the classical editor layout with two viewer windows side by side, while yet different working styles might exploit a limited set of viewers allocated in stack- or round-robin style.
+The classical example to verify this definition is the //allocation of viewers:// when starting playback of a new media item, we "need a viewer" to show it. But we can not just create yet another viewer window -- rather we're bound to allocate one of the possible "viewer slots". In fact this is a configurable property of the UI layout employed; sometimes some people need the limitation to one single viewer entity (which might even be external, routed to a beamer or monitor), while other ones request the classical editor layout with two viewer windows side by side, while yet different working styles might exploit a limited set of viewers allocated in stack- or round-robin style.
!View access
The global access point to component views is the {{{ViewLocator}}} within InteractionDirector, which exposes a generic access- and management API to
@@ -3469,7 +3469,7 @@ The InstanceHandle is created by the service implementation and will automatical
→ see [[detailed description here|LayerSeparationInterfaces]]
This overarching topic is where the arrangement of our interface components meets considerations about interaction design. The interface programming allows us to react on events and trigger behaviour, and it allows us to arrange building blocks within a layout framework. Beyond that, there needs to be some kind of coherency in the way matters are arranged -- this is the realm of conventions and guidelines. Yet in any more than trivial UI application, there is an intermediate and implicit level of understanding, where things just happen, which can not fully be derived from first principles. It is fine to have a convention to put the "OK" button right -- but how to we get at trimming a clip? How do we how we are to get at trimming a clip? if we work with the mouse? or the keyboard? or with a pen? or with a hardware controller we don't even know yet? We could deal with such on a case-by-case base (as the so called reasonable people do) or we could aim at an abstract intermediary space, with the ability to assimilate the practical situation yet to come. @@ -3517,6 +3517,17 @@ The concept of a //focus goal// has several ramifications: for one it implies th !Building the framework To create such a system is an ambitious goal. We can not reach it in a single step, since it entails the formation of a whole intermediary layer, on top of the //usual UI mechanics,// yet below the concrete UI interactions. Especially, we'd need to clarify the meaning of //perspective,// we need to decide on the relation of top level frame, individual view, layout, focus and //current location within the UI.// On a second thought, building such a system implies we'll have to live with an intermediary state of evolution, where parts of the new framework are already in place without interfering with common conventional usage of the interface as-is. + +!!!UI coordinates +Especially the focus navigation entails the use of some kind of ubiquitous coordinate system within the user interface. In fact this is more of a topological navigation, since these coordinates describe the decisions and forks taken on navigation down the //focus path.// +* [optional] top-level Window (UI frame) +* [optional] Perspective +* Panel +* local path +** [optional] Group +** ~View-ID +** component.component.component... +
+ ...was für verschiedene Arten von Zugriff +
++ sind denkbar und müssen in der Strategy konfigurierbar sein? +
+ + ++ mögliche +
++ Komponenten +
+ + ++ Grundlagen für InteractionControl +
+ + ++ Abstraktion zur Steuerung schaffen +
+ + +- der an geeigneter Stelle hängt + Verwaltung autmatisch via ViewLocator -> PanelLocator
-