Thanks for the replies. I was thinking I should have posted this in the Skinning Group forum for the group that creating the skinning mechanism, but happy to feedback here!
Specifically, I have implemented a Telerik RadSplitter in a skin. This is above and beyond the typical table based content panes, as you have layed out above. Right now, I have put an iFrame in the Rad SlidingPane, so that I can slide out a hidden documents area from the right side of the page. I thought it would be cool, and handy, to put a table in that RadSplitter (directly in the skin page), so that I could put a module there. And that would be cool. But, the skinning engine does not parse the TDs. The answer I got from Telerik was that it is because the skinning engine does not parse panes within an ASP panel.
And by parsing, in this case I am referring to the run time recognition of a TD set to runat server as a DNN module pane.
So, what I am trying to figure out, is if there is a work around, where I can force/trick/cajoul the skinning engine to recognize that this TD is still a pane.
And, in case it helps, I am just working directly in the skin .ascx file, not uploading through the skin upload parse mechanism.
Thanks!