Continuing c9cf3b67, retain jenkinsRule but empty as a placeholder, and register its rules in the new way.
Registering them with increasing positions, since there seems to be some implicit order dependency involving TR.rowvg-start.

Retain hudsonRules/jenkinsRules for now, as many scripts in core & plugins directly modify this hash.

Don't expose stuff that need not be exposed.

One of the problems with the current way Jenkins puts JavaScripts is that most everything is in a single file. It doesn't highlight the relationship between those fragments and their corresponding tag files.

So I'm experimenting with moving out these fragments into individual JavaScript files co-located with the tag file. They then get loaded into the page via <st:adjunct>. Each script is served with unique URL such that the browser will not even have to try conditional GET when loading different pages, so this should prevent the performance problem caused by the fact that there are now lots of <script> tags in the page.

 If for some reason even this turns out to be a problem, we can always add additional build steps to concatenate them all.

This makes it consistent with other buttons like repeatable-add-button, and use of '-' prevents name collisions with form names, and make all of those UI controls addressible in the same namespace

Make Jenkins stop polling resources if the page is not visible (and if the browser supports Page Visibility API), restoring pollings when the page becomes visible again. This will make tabs in the background to not consume resources

Previously, the code was "find the nearby element of the expected @name,
then make sure it has gotten the right parent."

So if the structure is like:

  {/* outer object */
      name: "parent-name",  /* A */

      child1: {/* inner object */
        name: "child-name" /* B */
      },

      child2: {/* inner object */
        name: "child-name" /* C */
      }
  }

... and if we are looking for "../name", it finds B, and it gets
rejected, so we won't be able to find A, which is what we are supposed
to find.

With this change, we keep trying until we find the right one,
so the above case will correctly return A.

$(e).next() may return undefined.
If 2nd argument of insertBefore is undefined,
IE9 complains "SCRIPT87: Invalid argument".
To insert newChild at the end, 2nd argument should be null.
http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-952280727

Jelly/Groovy views don't do this, but erb views from Ruby often do it,
so better be robust. This is breaking J-on-J currently.

At least now the back button won't trigger the drop-down notification.

(and replaced custom event addition with simpler one from Prototype)

This is useful for adding in-page navigation in a large page.

Also animate color so that a transition from one notification to another
will appear more smoothly.

Promoted all members of defaultOptions.* up the dot to make core more
terse.

unclickable.

Added server side utilities to generate apply-aware responses.

see http://www.nczonline.net/blog/2009/09/15/iframes-onload-and-documentdomain/ for details