[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-core-dev] e4 Resources Kickoff Meeting
|
Yes, I think that's the point.
We need to start looking at file-system-based aliases
as distinct elements
in the resource tree. Apparently it works for Mac
aliases already; for
symbolic links not yet.
When the Alias
is a distinct element it can have a property "transparent"
(adopt markers,
context etc from the aliased resource) or "context-sensitive"
(maintains its own markers, context etc but still keeps
Editor Buffer in
sync with the underlying resource.
In case of transparent aliasing, markers generated from the
various contexts
that hold the resource need to be cumulated (merged)
together and all
attached to the underlying resource.
In case of context-sensitive aliasing, these stay
separate.
Cheers,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Random thought: A Mac "alias" file is itself a resource, which could have
markers written against it (even now). Could we have a distinction between the
actual resource and a collection aliases for it, and then add markers to the
aliases.
