many classes are "polluted" by properties and view/model
interaction, and
view styles are also APIs, even though the methods are intended to be
hidden. This is the nature of the "accepted approach" and perhaps
not too
much can be done about it.
I'm not sure exactly what you mean by "polluted" - can you clarify? I
actually think the APIs are very clear, especially now that we have
been over them 2 or 3 times.
In the long term, I expect a stable 2.0 emerge that follows the
general
comaptibility guidelines and the cruft has been removed. Once that
happen, I
think we should be much more stringent than now.
I agree. I also agree that Pivot is currently following what would
more traditionally be used as a "0.x" release model, but I think the
"1.x" scheme is OK because the platform is much more complete than a
"0.x" scheme would imply.
