« Hide

Linked resources are a feature of Eclipse, which they expose in a variety of places. When Eclipse shows one of these, they just show the bare, undecorated name. E.g. if "FOO" is a linked resource to C:\MyFoo, and the user adds FOO/bar.jar to the classpath of a JDT project, then it shows up like this in the JDT's UI:

FOO/bar.jar

In FB 2.0.1, it was decided that this is confusing, so we "wrap" these variables in ${} -- for example:

${FRAMEWORKS}/libs/playerglobal.swc

The problem with this is that it creates an inconsistency, so the end user is not sure when he should use the curly brace syntax, and when he should not.

I think we should change FB to just do it the Eclipse way: never use ${}.

(Note, by the way, that the old ${FRAMEWORKS}, which has been renamed to ${PROJECT_FRAMEWORKS}, is NOT a linked resource any more. However, we never actually show it in the UI, so it doesn't matter. With this proposal, we would never show ${ } in the UI.)


        

Show »

Linked resources are a feature of Eclipse, which they expose in a variety of places. When Eclipse shows one of these, they just show the bare, undecorated name. E.g. if "FOO" is a linked resource to C:\MyFoo, and the user adds FOO/bar.jar to the classpath of a JDT project, then it shows up like this in the JDT's UI: FOO/bar.jar In FB 2.0.1, it was decided that this is confusing, so we "wrap" these variables in ${} -- for example: ${FRAMEWORKS}/libs/playerglobal.swc The problem with this is that it creates an inconsistency, so the end user is not sure when he should use the curly brace syntax, and when he should not. I think we should change FB to just do it the Eclipse way: never use ${}. (Note, by the way, that the old ${FRAMEWORKS}, which has been renamed to ${PROJECT_FRAMEWORKS}, is NOT a linked resource any more. However, we never actually show it in the UI, so it doesn't matter. With this proposal, we would never show ${ } in the UI.)