Andy,
Not that you necessarily should have them, but do you have any strong
thoughts about resource identifiers? Views start life as a string, then
a resource identifier, and then finally as a realized view. The string
name is reasonable, and the realized view is unavoidable. Is the
identifier stage particularly useful? Could there be an argument for
replacing it with views that simply have not been realized? I suppose
they simplify changing the view class used in a saved view resource, but
are they essential to allowing that? Are there any other questions I
should be asking?
I am curious because I have an analogous design problem involving
"identifiers" and fully realized gizmos. Part of me thinks the
identifiers are useful entities, and part of me thinks they don't buy
very much. "If it ain't broke, don't fix it" will probably win in the end.
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
Locked
