Re: [platform-core-dev] PathVariableManager and friends...

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Can you expand a bit on why you don't
want to use the existing path variables as they are?  If we can avoid
another duplicate "variable" concept I think it would make for
an easier user experience (there are already path variables and java classpath
variables).  What problems would you see with sharing path variables
with the linked resource mechanism? I realize the UI for path variables
is currently closely tied to the notion of linked resources, but if it
was made more general would it serve your needs?

platform-core-dev-admin@xxxxxxxxxxx wrote on 12/16/2003
02:12:37 PM:

> 
> In our product, we need a mechanism that supports Path Variables 
> very similar to the Linked Resources. However, we do not want to 
> have our variables mixed in with the Linked Resources since this 
> could potentially create problems for us. Ideally, we would want to
> use the  PathVariableManager, PathVariablesGroup, 
> PathVariableDialog, PathVariableChangeEvent, etc. However, the only
> difference would be is that we would be able to store the Path 
> Variables in  our plugin's preference store, with our own prefix.
> These classes are currently defined as internal, as well as the 
> interfaces that these classes implement are tagged "This interface
is not 
> intended to be implemented by clients." Any possiblity of making
> this service available to other plugins? 
>