context dependent scope paths
| Reported by: |
Ichthyostega |
Owned by: |
Ichthyostega |
|
Priority:
|
lesser
|
Milestone:
|
1alpha
|
|
Component:
|
lumieraSteam
|
Keywords:
|
|
|
Sub Tickets:
|
#322, #323, #324, #424, #432, #661, #663, #672, #676
|
Parent Tickets:
|
#108, #331, #356
|
When the high-level-model no longer is a tree, but a DAG (which happens when we add virtual clips), then we need a means to reduce it temporarily to tree shape, to enable use of all the existing query capabilities. The envisioned solution is to remember the access path taken to a current focus location. Navigation and placement attribute queries will then use a scoping similar to the one visible from this focus location.
As an asside, this problem is quite similar to file system navigation including symlinks. Under which circumstances shall a discovery follow symlinks? Where do you get by cd .., especially when you went down following a symlink?
This ticket covers integrating this feature based on functionality already built into the basic placement scopes and scope path handling.
Change history
(17)
| blockedby: |
322 → 322, 323
|
| blockedby: |
322, 323 → 322, 323, 324
|
| Milestone: |
0integration → 1alpha
|
| Priority: |
normal → lesser
|
| Type: |
todo → planned
|
| blockedby: |
322, 323, 324 → 322, 323, 324, 324
|
| blockedby: |
322, 323, 324, 324 → 322, 323, 324
|
| blocking: |
108, 331 → 108,331
|
| blocking: |
108,331 → 108, 331, 356
|
| blockedby: |
322, 323, 324 → 322, 323, 324, 424
|
| Description: |
modified (diff)
|
| blockedby: |
322, 323, 324, 424 → 322, 323, 324, 424, 432
|
| blockedby: |
322, 323, 324, 424, 432 → 322, 323, 324, 424, 432, 661
|
| Description: |
modified (diff)
|
| blockedby: |
322, 323, 324, 424, 432, 661 → 322, 323, 324, 424, 432, 661, 663
|
| blockedby: |
322, 323, 324, 424, 432, 661, 663 → 322, 323, 324, 424, 432, 661, 663, 672
|
| blockedby: |
322, 323, 324, 424, 432, 661, 663, 672 → 322, 323, 324, 424, 432, 661, 663, 672, 676
|
| blockedby: |
322, 323, 324, 424, 432, 661, 663, 672, 676
|
| blocking: |
108, 331, 356
|
| Parent Tickets: |
→ 108, 331, 356
|
| Sub Tickets: |
→ 322, 323, 324, 424, 432, 661, 663, 672, 676
|
(In #661) see also the tracking ticket for context dependent paths.
More specifically, #424 drafted a solution for this problem, but meanwhile I think it would be better to keep this functionality as a responsibility of the ScopePath, as opposed to hiding it somewhere in the query functions for placement index.