HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
We all remember Single Copy Template (SCT) and how this worked out, right?
Moving idea to product : Domino Designer
Couple of reasons for not using templates:
If you use template inheritance, the resources are in all databases separately instead of in one place.
When changing the design, you have to wait until all relying databases are refreshed.
Using templates recently delivers often broken code until you recompile all databases that inherit their resources from the template.
Also this produces disk overload, if most of the databases are using the same template.
Being able to load resources from another database will also reduce the cost of updating all dependend databases.
@Guest (the commenter, not OP): template inheritance can get pretty messy, and at least in the past I have been told to avoid that, because it can be buggy.
I think it would be very useful to be able to call resources from other databases.
Can you explain why you wouldn't want to use template inheritance for this? Seems to me that using templates, even multiple templates to store design elements will meet this need.