Community
Participate
Working Groups
External Tools provides variables for a resources' location and full path, which eventually resolves to the accessors of the same names in IResource. To a user, "full path" intuitively means an absolute path on a file system, while "location" is a more abstract notion - more useful a term to describe a relative position within a domain-specific semantic construct like 'workspace'. Perhaps "full path" and "location" should be swapped. Please note for version 3.0, if a renaming of this nature could be more than a remote possibility.
To me, "location" suggests the physical place where the file is stored on the disk, while a path is just a means of finding that resource in the logical structure of the workspace. Regardless of semantic interpretation, I don't think it's worth the API upheaval and confusion to existing developers to swap the meaning of these terms. "Location" and "path" are used consistently throughout the core API with those meanings. It's called "full path" to contrast with project-relative paths that are also part of the API. I think both terms are abstract when presented to the user outside the context of the workspace API. If these terms aren't clear enough when presented in the UI, then it might be appropriate to explain them more clearly within the UI.
Reopening for UI consideration.
Should come up with more intuitive variable names, that aren't so bound to Core API terminology.
Address in the new external tool rework Note: new external tool work is not yet released to the head stream and won't for a while yet.
This bug has not been fixed and should not have been closed.
Nothing more planned for 2.1. When selecting a varible as a tool argument, the variables appear with a meaninful description.
*** Bug 20588 has been marked as a duplicate of this bug. ***
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
