I take your point: it's great Tarek participates in the forums — but as soon as you need to go to a forum or look at the source code to work out what's going on that's time down the drain. STV's selling point is saving time — the lack of documentation undermines that. (And the time between November and now is long enough already — I'm not saying it should necessarily be perfect but it should be a lot further along than it is.)
Tarek thanks for the offer to prioritise. I understand you want to include changes from WWDC but when they come you'll be coding and the docs won't get the attention then — so it needs to be now :-)
Today I've spent a lot of time messing around with SCWebServiceStore and Definition — trying to understand how they relate to each other and SCDataStore and how to extend beyond the simple read-only web service example.
The API docs are great — but the need a "Programming Guide" style overview to show you how all the bits fit together. The old docs are ok but not really what I wanted — to be honest they're a bit list-like — in that they do a lot of listing of API. Rather a good discussion of the architecture and a few worked examples so that when you go to the API docs they make sense — vs now having to crack open the source to see what's going on.
So you want to read-write a remote API? Here are the constraints, here's the outline of what you need to do, here's how you step down a level if your API doesn't fit our pattern. THAT would have taken a hour or so to go through and got me going more quickly.
But that's just one area...
STV is clearly powerful, and clearly well coded and conceived. But each area needs overview docs that make clear the lay of the land so that (again) the API docs make sense when you come to them — so that they can serve as the reference as intended.
What areas in particular? How the various components sit together and interact. Actions. Customizing (all aspects). The limits of what's possible in IB — and how you drop down to code when you need to. — All of this stuff. The forums just cannot substitute for that — and the product is unfinished without it — no matter how good the coding.