Two Good Questions

Codejock seems like a nice toolset on top of MFC, but I am still wanting to understand two things before I proceed writing a large app that would depend on it:

1) If an app uses the ribbon with the Office2007 skin, how do you skin the dialogs, since this has been prohibited due to some sort of mysterious conflict that has been referred to. I do not want my dialogs having a generic gray look. Do I simply create skinned child windows mimicing dialogs instead?

2) Are their any layout widgets to facilitate the creation of complex forms at runtime? The more modern frameworks such as wxWidgets, Qt, and many others include nice layout and sizer controls. I have a feeling it does not, so the Codejock devs should consider implementing such -- or is their some sort of generic third-party layout toolset that I am uninformed of?

3) I do not understand what extra functionality the Codejock dialog editor offers over the VS dialog editor.

May everyone please post some comments here, however brief they may be. Are you happy with using Codejock? Any positive or negative experiences you can mention? So far the worst downside seems to be the lack of documentation. Thank you.   

ABuenger wrote: It's the best MFC toolkit on the market, period. There are only 2 competitors left in my eyes, but both have two major drawbacks: performance and quality.

Agreed. It seemed to me that the Prof-UIs framework (www.prof-uis.com) was a bit sluggish in the redraw. Also, Codejock is Pixel-Perfect. Would the other competitor be Stingray?