[this could be a duplicate, I had a problem with gmane]
Hi all, Often, the client wants us to change some of the plone templates. When that is a large-scale replace/rebuild of the main_template, ok. But what I see most often in our practice is a small tweak here and there. An added textual explanation to a form. Adding a dropdown to the search box. In most of the cases, the majority of the template remains intact. Then a new plone release arrives. Has anything changed in the templates we've adapted? Do the changes conflict? Do we need to adapt some more? At least, that are the questions I'm confronted with. The reason? Quite simply copying the templates to a customizing product's skin directory and modifying them there. At least, that's the practice I'm using myself. It strikes me as sub-obtimal. How do you all handle this? I just did some braintorming and came up with the following rough idea: * Have some directory with diffs to the original plone template. * Have a small script copy the original plone templates and apply the diffs. * If there's a .metadata file, copy that right along. * Check the page template for validity (i18ndude is a great validator) * With a new plone release you can easily spot the templates that have conflicting patches. Just brainstorming :-) Reinout -- Reinout van Rees - Programmer at http://zestsoftware.nl/ http://vanrees.org/weblog/ mailto:[EMAIL PROTECTED] "White space, the opposite of black hole?" -- Joris slob _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
