Move $position and bindHtml to ui-utils

[ProLoser]

Both of these modules I think could benefit many people who do not use ui-bootstrap and they are not specific to ui-bootstrap. I myself have encountered a few places where I've needed to do position calculations and didn't want to make jquery a dependency.

I believe making ui-utils a dependency of ui-bootstrap would help improve both projects.

Personally, I use ui-utils as much as I do ui-bootstrap and tend to encourage the community as a whole to do the same, so making it a dependency does not feel unreasonable to me.

ui-utils is no longer dependent on jquery and has become much lighter in footprint.

[caitp]

I'm not sure if I necessarily like the idea of adding another dependency (I realize fully well that my opinion here doesn't matter a whole lot!)

It seems like ui-utils probably bundles things that ui-bootstrap doesn't depend on, so requiring it just for two modules seems wasteful. Not to mention that it also means many application developers would need to make unnecessary changes to their builds and/or markup to import the ui-utils deps. That's not that big of a deal I guess, but I just don't totally see it as worth doing, maybe.

I do think that the dom manipulation stuff does need to go somewhere more central (probably into jqlite, tbh), but who knows when/if that will happen.

Anyways, it's just my 2:30 am opinion, nobody gotta take it.

[ProLoser]

I concur that it would be nicer to put it in jqlite, but I don't know how likely it is for that to happen since the AngularJS core doesn't need it for anything. I also know for a fact that several other modules could greatly benefit from it.

[pkozlowski-opensource]

The fact that two wildly different parts of the system performed some logic in the same way meant less than I thought. Up until I had pulled out those libraries of shared code, these parts were not dependent on each other. Each could evolve independently. Each could change its logic to suit the needs of the system's changing business environment. Those four lines of similar code were accidental — a temporal anomaly, a coincidence. That is, until I came along.

From http://programmer.97things.oreilly.com/wiki/index.php/Beware_the_Share

As @caitp, even if I'm all for the code reuse, I think in the current state of affairs it would lead to unnecessary coupling of 2 libraries. I don't think it is going to land in jqLite so IMO the proper, long-term solution is to either to put $position and friends as a common service or ... hell... use small subset of jQuery when it becomes possible.

But this all depends on how AngularJS, jQuery and bower are going to evolve. For now sharing those 50 or something lines of code is not very practical IMO.