Getting more out of the P2...
Given the complexity of the P2, and the lack of inbuilt peripherals, what it really need is something like PSoC Creator.
Hopefully, P2 isn't so complex that people suppose everything must be configured ahead of time, before their main program runs.
Programs that dynamically reconfigure the hardware will get a lot more out of the chip.
Is that true? In most cases, I'd think the peripheral configuration is going to be static. Yes, there will be some neat designs that dynamically use the same I/O for different purposes, but I suspect that will be in the minority. Or are you talking about something else?
I think our core manual doesn't need to be that big. Examples can take lots of room, but descriptions shouldn't. Everything in the Prop2 is intended to be thoroughly understood and exploited. There are no black boxes inside.
Personally, I prefer having a simple code example accompany each instruction. Now, this might not be a big an issue with assembly language instructions, but I think it's indispensable for higher-level languages. Given the old adage of "a picture being worth a thousand words", a code example is the picture.