May 12, 2011 at 9:19 AM
Edited May 12, 2011 at 9:20 AM
Ok, this is the same problem as with default list display (from the ItemController). For whatever reason the decision was at some point taken that people would only ever need the list items, not the container itself!
I know the devs have it in mind to do something about this for future release.
Now ... depending on exactly what you are doing with the container, you could try using Mechanics. It's a module I've written that gives you a many-to-many relationships system that goes well beyond the capabilities of lists.
Instead of anything akin to ContainerWidget, instead Mechanics has a feature called Paperclips which allows you to push different types of connector to different zones. So this is kind of a replacement for the "page layer". Or by attaching content
to the Site object, you can cause its connections to be rendered on every page. By attaching content to the User object, connections will be displayed in zones just for that user. You can also hook into events to provide your own rules for how shapes are dispatched
to zones. So it has the flexibility of the layers system, it's slightly more work to set things up, but better UI in the long run.
If that system sounds a bit too much for you (bearing in mind it's still pretty new and there are certain things still needing some improvement!) you could try using an IShapeTableProvider to modify the "Parts_ContainerWidget" shape and add the content item
into the shape model, assuming it's even there.
On the other hand if you want to use Mechanics I'm happy to help you get the rendering how you need it. I just double checked and I wasn't actually passing in the ContentItem yet (on the Socket shape which is the equivalent here), but I've just fixed that
and will push the change up to the gallery and codeplex site soon.
Edit: BTW, gallery page is