*puts overpriced beer down* wouldn't it make more sense to have :-

<?php $Plugins->trigger_event( 'HtmlEndBody' ); ?>

The plugin could write the <script></script> tags, and it would give a smidge more flexability.

*wanders off to find EdB's secret stash of JB*

¥

Yeh, i've been fidling and deciding about wether to use endbody instead, but the only things that would go in endbody would be javascripts.

And it sure saves the repetitive <script .... for each plugin that needs it.

*Leaves to buy a six pack of cheap lager, you're killin me*

Perhaps I'm a bit confused, but why would you use a client-side script to trigger a server-side action? Isn't it much better to do all the server side stuff at the server? Either way, it'll fail when the visitor doesn't allow javascripts.

Skins that depend on javascript should carry a warning label.

What's bad with using the SkinBeginHtmlHead() event and outputting

<script type="text/javascript">
  addEvent( document, "load", my_function, false|true );
</script>

there? This will add it to the document's onload events..

I believe that waits for the whole page to load, not just the dom. So the javascript would be waiting for images to load as well, which could take a while...

blueyed wrote:

What's bad with using the SkinBeginHtmlHead() event and outputting

<script type="text/javascript">
  addEvent( document, "load", my_function, false|true );
</script>

there? This will add it to the document's onload events..

That does not work with firefox...

Although this does;

function addLoadEvent(func) {
	// taken from; http://simon.incutio.com/archive/2004/05/26/addLoadEvent
	var oldonload = window.onload;
	if (typeof window.onload != 'function') {
		window.onload = func;
	} else {
		window.onload = function() {
		if (oldonload) {
			oldonload();
		}
			func();
		}
	}
}

addLoadEvent(init);