proposed add: outerHeight/Width + innerHeight/Width

[bluesaunders]

Now that Cash is modularized, should we add the following methods?

• outerHeight()
• outerWidth()
• innerHeight()
• innerWidth()

They'd be useful for having more refined control of determining the size of elements without having to hardcode in magic numbers, or try to acquire the numbers with calls to getComputedStyle(elem);

[mnelson]

Now that we're modularized I'm generally fine with the addition of stuff like this. For the sake of argument, let's consider the following:

1. Where do we stop? Let's not rebuild jquery / zepto for the sake of it.
2. Are there cases where we need these methods right now?
3. Should "more complicated" methods like these be included into the existing, similar modules (i.e. heightWidth.js) or to a new module (i.e. advancedHeightWidth.js).

[bluesaunders]

Definitely good points.

1. Agreed. For starters, I think we should continue questioning an addition before implementing for implementation sake.
2. We ran into one yesterday, but better design of the page and leaning more heavily on CSS might help.
3. Good question, idk.

[robrobbins]

The Outer* are more useful IMO as the issue Brendan found was that the padding was, of course, not being reported by height(). I think the answer may be @bluesaunders 2nd point, better design. The need for it may just be a design 'smell'... I will put together a module for it, at some point, but it won't be in the default build