It is more interesting than it seemed… looking for a solution
Rob,
I prototypes a solution in projections-categories branch.
JavaScript seems to be the most popular (at least in a small chunk of data I retrieved)
I’m not certain that this will be integrated into dev/master as it is, but your projections work there.
-yuriy
I prototyped…
Okay, well if my projections work there then I can at least update my blog entries with working code, in the knowledge that by the time they’re published this problem will all be sorted… right? 
Thanks to all your notes, the developer workflow should be a little smoother with my recent changes.
Nice,
I love a good developer experience - I’m planning on giving some more comprehensive feedback once I’ve got everything up and running and stable. 
One thing I am really waiting for is to get the query window working. That will be pretty nice.
Great so this works in that branch providing I do a complete re-build and clear my data directories (I hope I won’t have to do this on the server which is collecting data and has been for the past three weeks?)
What’s the appropriate way to sift through the results if /all-states didn’t make it into ‘dev’ ?
Read the entire result stream for ‘uniques’ and then visit /state?partition= for each one I’m interested in? Build up a state by reading through each of those streams? (Easily done)
(for example)
fromStream(‘totaleventsbylanguage’)
.when({
$init: function(s, e) {
return {}
},
“Result”: function(s, e) {
s[e.streamId] = e.body.count
}
})
Would give me the state I want, but I get the feeling this is something I should do “out of store”
PS: I have 5 days until the event store posts are due to pop, unless I swap them with a two week series I’m about to do on “OMeta” (Oh I live an exciting life)