skinning method decision

Hi! So it would be nice to come to a decision about the skinning method. We have two suggestions: a) Use id="" parameteres in all HTML parts we would like to support to be skined, and define one function called using the page unload event to form the new look of tha page according to the used skin. Hide the page until the designed page is built up. b) Define separate functions for parts we would like to support to be skined, and put in calls to the functions inside the HTML code of every page. Form the page while it displays itself. Advantages: a) Smaller HTML files, Very small and simple skin code for inline skins, Better speed (accoring to my tests) for inline skins b) More traditional way of coding Slightly better speed for external skins Formatting, while page is displayed Disadvantages: a) The built in HTML codes, like » for the outside links are not that easy to work around in an external skin Formatting before page displayed (some more delay for external skins) b) Slower for internal skins, Bigger HTML files Handling of encapsulated elements (eg. notes inside examples) makes function definitions complex As we stated before, we prefer to have smaller HTML files, and let the inline skins be as fast as possible (ideally as fast, as they was before the skin feature introduced). We can achive these with the a) method, as my speed and size tests showed. So I would like to give my vote for the innerHTML method. What do other think about this? Note: the speed test suite is still available from http://weblabor.hu/php-doc-chm/speed.zip Goba