First off, thanks for responding. Sorry for the confusing title. I was trying to avoid craming my entire issue in there so I made briefer than it should have been.
Most tutorials/examples I have seen have one piece of data--a record, with one Part, and is displayed with one widget. What I need are three widgets that display different aspects of the same data: a Ball.
2. Ya it does seem wasteful to me too. However, I used Orchard.Comments as the base for my module since it seemed to do roughly the same thing I wanted to do. Figured if they did it like that...
3. Not really sure why I did it like that. Seemed like a good idea at the time, I'm sure. Like I said, I was trying to use Orchard.Comments as the template for my module and I may have tried to make some square pegs fit in that round hole.
So, I have a Part and a Record. I can create content types to my heart's content. I'm trying to figure out a way to feed different sets of that content to different widgets. What would be the best way to go about that? Based on what I found in Orchard.Comments,
I believe I can use just one model for the different widgets. It's the interaction of the Parts, Handler, and Driver that I'm struggling with. Based on your comments, here's my revised thinking:
I have a BallsPart that I need to include in with each of the widgets in the ContentDefinitionManager. My Model and Handler are rough but ok. And I'm going to need a Driver for each widget.
Is that a better approach?