Any developer worth his salt has come across old code that has bugs in it or needs to be enhanced.
I have a series of templates which cascades their inheritances through a selection of other templates. The Master Template simply contains various totally generic routines. prototype.js sits in here, as does TinyMCE and a variety of other useful libraries, shared fields, subforms, shared pages, $$Templates etc. All of my application templates inherit bits from here, which in turn is inherited by the test applications. The Live apps never inherit for safeties sake, but have their design copied from the test apps - which the end client has tested and approved.
So if you ever find you've made a bug in a routine, fix it in one spot, and run the designer task on the server. Now everything is sorted. :)
Which is where the use of templates comes in.
Any developer worth his salt has come across old code that has bugs in it or needs to be enhanced.
I have a series of templates which cascades their inheritances through a selection of other templates. The Master Template simply contains various totally generic routines. prototype.js sits in here, as does TinyMCE and a variety of other useful libraries, shared fields, subforms, shared pages, $$Templates etc. All of my application templates inherit bits from here, which in turn is inherited by the test applications. The Live apps never inherit for safeties sake, but have their design copied from the test apps - which the end client has tested and approved.
So if you ever find you've made a bug in a routine, fix it in one spot, and run the designer task on the server. Now everything is sorted. :)