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

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

I suggest entering a feature request
against platform core so this discussion does not get lost.  Once
M6 is out the door most of us will be on holidays until next year.

John.

platform-core-dev-admin@xxxxxxxxxxx wrote on 12/17/2003
10:43:46 AM:

> 
> Here is the reason we want plugin specific Path Variables. 
> 
> Our data is used in a team development environment. When serializing
> our data, the absolute paths are checked for possible Path Variable
> matches. Any match will be replaced. Now if a developer has a Path
> Variable defined that is not associated with this specific 
> application, it is possible that an unexpected match may be found.
> When the data is used by other developers, they will not have the
> corresponding Path Variable. Teams usually define a standard set of
> Path Variables for a given application. 
> 
> Here is a simple example that may help explain the problem: 
> 
> Team defines the following PathVariables: 
>         Here= C:\where\here 
>         There=C:\where\there 
>         Somewhere=C:\where\somewhere 
> 
> Developer X has also defined 
>         Home=C:\ 
> 
> Now if the data contained a path, C:\Temp, when Developer X 
> serializes the data, the result would be $(HOME)\Temp. 
> None of the other developers will have that defined. 
> 
> If you made the UI more general that would be great. I think we just
> need to be able to group the variables as "global" or 
> plugin/application specific. 
>         T. 
>