Lord Lotus Blog | Inherit from the design template question

Wednesday 3rd, January 2007

Inherit from the design template question01/03/2007 12:08 PM

Domino Development

I've created a template called Shared Code (sharedcode.ntf) that contains some script libraries, views and forms that I typically include in other templates. When I paste design elements from sharedcode.ntf into another template (sample.ntf), I chose to have the pasted design elements inherit from sharedcode.ntf. These pasted design elements have Shared Code specified as the design template name, and also have a special icon to the left of their design name in Domino Designer.

All of the above is working as I expected. However, when I refresh the design of a Sample database (sample.nsf) with a template that includes design elements that inherit from sharedcode.ntf, the design elements from sharedcode.ntf in sample.nsf do not have Shared Code specified as the design template name and the special icon no longer appears.

The problem I have with this behavior is that when I need to roll out a change to a design element in sharedcode.ntf, I need to put all of my application templates (sample.ntf, etc.) on my production servers, instead of just sharedcode.ntf. Let me explain this a bit more...

I know that by refreshing sample.ntf, sample.ntf will receive the design changes from sharedcode.ntf. (Although not quite the same as for other development environments, this can be referred a build.) However, if I have 100 templates (NTFs) that inherit design elements from sharedcode.ntf, and I change one of these design elements in sharedcode.ntf, I need to build all 100 templates (NTFs) again in order to deploy the change across all 100 databases. Either that, or I need to keep sharedcode.ntf and all 100 templates on my production server, and have the Designer task propogate the changes to all templates and databases.

I had thought that design elements in a database (NSF) always showed the design enheritence for individual elements, not just templates (NTFs). In fact, I remember that this was how things worked in R5. Was this behavior intentionally changed between R5 and ND6? Or, is this behavior a result of a bug in the ND6 codestream that has been fixed in later codestreams?

Comments :

1. Chad Schelfhout01/03/2007 02:31:48 PM
Homepage: http://www.chadsmiley.com

I have no way to prove that ND6 and ND7 work the same as R5 but I believe it does because I have been using design element inheritance since R5. I understand your frustration but I have to agree with Lotus' implementation with the inheritance. Why? Because if you wanted to change the design of your database you could select replace design and all the old design elements would be deleted and the new ones would be added. With your implementation some design elements could hang around. Hope that helps.

2. Martin01/08/2007 11:43:41 AM
Homepage: http://www.martinhumpolec.cz/blog

I'm a little bit in shock if it's really working as you write, because it really doesn't make sence (or make the same sence as in R5). It's almost useless in this way :(

3. Chad Schelfhout01/17/2007 10:34:25 PM
Homepage: http://www.chadsmiley.com

Here is how I have setup my environments:
http://chadsmiley.com/chadsmiley/home.nsf/d6plinks/CHAY-68VS9D
http://chadsmiley.com/chadsmiley/home.nsf/d6plinks/Domino_Environment_PartII

Typically I never migrate a library template out of my development environment but in your case it might make sense to make stripped down library template with the one or two design elements that need to be update and then temporary place it on your other servers over night so the templates and database are updated.

Credits

Su	Mo	Tu	We	Th	Fr	Sa
			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29