What is/are the generally accepted design patterns for Javascript bookmarklets?

All the bookmarklets I have ever done are directly inserted into the DOM of the main page. All the code has lived inside a namespace for that bookmarklet so the DOM pollution is kept at a minimum, and of course there are checks to make sure there are no collisions with existing variable names.

All the bookmarklets I have ever done are directly inserted into the DOM of the main page. All the code has lived inside a namespace for that bookmarklet so the DOM pollution is kept at a minimum, and of course there are checks to make sure there are no collisions with existing variable names. The reason for insertion into the DOM of the main document is because it makes everything easier - there is rarely any good reason to make it harder on yourself than it has to be :) But of course this depends on your goals.

Pattern 1: javascript:void(document. Title += 'HAI! ') any bookmarklet return value gets converted toString and act as it was passed to document.

Write void operator prevents it Pattern 2: javascript:(function(){ for ( var I = 0; I Alt; })() bookmarklets are running in the global scope, so without anonymous function code above will "leak" loop counter as window.i.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.