Question: I want to customize the UITabBar in order to have a tab in the middle that has curved border on top and slightly greater height than the other tabs, the idea might look like this <http://grazsecrets.at/> , the only difference is that it uses a logo.

Answer: 
**Argument for the script inclusion solution**

The `on` solution is ugly and involved. It requires more code than the simple script inclusion, and mixes up concerns between the load handling code (which is presumably somewhere else) and the lightbox contents. Why should that code know about the ids of elements inside the lightbox?

**Argument for the `on` solution**

It involves one less HTTP request and so will probably be faster.
The way `.on()` was designed, you would set up the event handler first like this:

```
$("#blah").on('click', "#something", function() { alert('Hi'); });

```

Then, when you load the content in `#blah`, your event handler will automatically work for the `#something` element and you don't need a `.load()` handler.

The way this works is jQuery sets up an event handler on `#blah`. That event handler examines any click events that bubble up to it and when it sees one that has a target that was on an object that matches the selector `#something`, it fires the event. The `#something` can come and go as much as it wants because the actual event handler is on the parent object that exists the whole time.

Using this method, you would not need the extra blah.js file.