As a conservative "centralizer", I greatly share your thoughts here. I have
used this technique a lot and I am really happy about it when you need to
change things like a CSS. Change once, see it everywhere ;-)
The only drawback with image resources is that you cannot centralize them when
creating forms/pages for the notes client. You can only insert image resources
from the db you are working in (this limit is gone in R6, thanks Iris !).
Therefore, one enhancement I used when applying this technique (when still
using R5) and creating new db's, was to combine it with templates. Create a
template with the image resources and copy/paste them in the new db. A dialog
box will appear and ask you if you want future changes to be propagated to the
new db.
I only apply this technique for centralized image resource db's. That way, they
are actually stored in each db and can therefore be used for notes client
purposes while you are still able to manage them centrally in the template db.
As for CSS and JS libraries, I use your technique as described in your article,
since these are only used for the web and not for the notes client.
So, everyone that has read your article and doesn't apply the technique yet,
should start doing so right now. It greatly enhances efficiency when working
when working on larger projects. So, Jake, once again, great article ! I just
wanted to add my 2 pennies...
Also, these tips are to be discarded when using R6, since Lotus/Iris/IBM now
provide us with native support to share resources across db's, which is an
excellent feature in R6. Great job, Iris !
Hi Jake,
As a conservative "centralizer", I greatly share your thoughts here. I have used this technique a lot and I am really happy about it when you need to change things like a CSS. Change once, see it everywhere ;-)
The only drawback with image resources is that you cannot centralize them when creating forms/pages for the notes client. You can only insert image resources from the db you are working in (this limit is gone in R6, thanks Iris !).
Therefore, one enhancement I used when applying this technique (when still using R5) and creating new db's, was to combine it with templates. Create a template with the image resources and copy/paste them in the new db. A dialog box will appear and ask you if you want future changes to be propagated to the new db.
I only apply this technique for centralized image resource db's. That way, they are actually stored in each db and can therefore be used for notes client purposes while you are still able to manage them centrally in the template db.
As for CSS and JS libraries, I use your technique as described in your article, since these are only used for the web and not for the notes client.
So, everyone that has read your article and doesn't apply the technique yet, should start doing so right now. It greatly enhances efficiency when working when working on larger projects. So, Jake, once again, great article ! I just wanted to add my 2 pennies...
Also, these tips are to be discarded when using R6, since Lotus/Iris/IBM now provide us with native support to share resources across db's, which is an excellent feature in R6. Great job, Iris !
Best regards, Jurgen Van de Moere