>> I’ll take a look at skins. Most people are probably not going to write skins >> would be my guess though. > > Exactly - a typical app developer will use the include model, because it is > intuitive and easy to work with.
That probably came across a bit more pompously than I intended it to. I don't mean to imply that this is the best approach and that others are not worth considering. However, from personal experience writing a non-trivial application, I can say that the include model maps very well to the use case of modularizing an application's sub-components. As you can imagine, it is considerably easier to understand and work with than writing a custom skin, and so will probably appeal much more so to a typical app developer. However, based on what you have said, you are not a typical app developer - you are attempting to create reusable components that can be shared using a model similar to the framework components themselves. To me, that represents a strong use case for writing a custom skin. Please note that writing a skin is not something to be afraid of. It is nowhere near as complex as you might think, especially if you are extending an existing concrete class. Also, there are plenty of examples to draw from. G
