Oren Shemesh <orens at p-cube.com>:
The major difference between what you want and the 'client -t' command
it that you
want changes to the template to affect existing clients, which is a way
to get all
developers using that template to follow some global change that is
taking place.
If such a template system were set up, what happens if the template
changes
to exclude files that were formerly within the client view? (Esp. if the
files are
checked out.) It seems to me either everyone takes the risk of suddenly
losing
access to files, or the have list functionality would need to grow rather
complex
to deal with it.
I think I might rather see a voluntary update system in which each user
gets a
warning that the master template they reference has changed and asks if
they
want to update their link (along with a list of what bad things might
happen if
they do). This would require versioning the template, but that's not a bad
idea
anyway. Maybe a client-side option could make such updates automatic on a
client by client basis.-Wm