I want to create standard "Appearances" for various objects in my
application. I'm thinking I need to create a separate class for each type of
object (grids, text boxes, check boxes, panels, etc.). Is this correct?
Since these classes would only be invoked in the UI project, do I need to
make them their own project, or would I just include them in the UI project?
I'm thinking that I could reuse the code, so putting them in a separate
"Appearance" project might be a good idea.
Since I'm using Infragistics controls, I can also "skin" the app to some
degree through the use of Styles. They have preset styles for XP, XP
Explorer Bar, VS2005, Office 2000 and Office 2003. I could give the user the
option to set the app in whichever style they like. That brings up another
question. If each object has various styles to choose from, what would be
the best way to set that up? I want to be able to call the appearance
settings for that object based on the style. Would I just pass a style
property and have a switch inside the procedure for that object? I can't
think of a better way off hand since I'll always be passing only one property
to the class.
Newbie looking for opinions / best practices.
Thanks,
Dan Weese
dw****@caelumtechnology.com