On 6/22/06, James M Snell <[EMAIL PROTECTED]> wrote:
Thoughts? Complaints? Concerns before I check it in?
I'm honestly not sure it's a huge improvement in useability. You end
up typing a lot more this way (setFooAsXhtml("blah") ->
setFoo(Content.Type.XHTML, "blah")), and instead of distinct methods
that do different things you've got methods with the same name that do
potentially different things. How is this a step forward again?
-garrett
