<BLOCKQUOTE>quote:</font><HR> So maybe the answer (to implement alternative 1) would be to associate meta data with the mod group that would allow the same configuration to be applied to all mods within the group when the user decides to install the group. <HR></BLOCKQUOTE>
My line of thinking is going the same direction. The best way to do this is to have meta data at the "Group Level" and if a Mod in the group has the option, great, otherwise use the default skin. There are 2 problems to overcome: 1> dynamic application so that when a new Mod comes into a Group it is allowed to add to the meta data of the group. 2> Mods must be self contained, A user should just have to copy it to the Mods folder to get it to work. That means even if he doesn't know what group it belongs to it will still show up in the right place.
I'm booked solid now with 2 other playests (oh yeah, my real job too) but I can give this some thought now, and some time later.
Gordon, can you read data models? Creating a data model will ensure I understand the problem completely. I may model this out and have you look at it, if you want.
[ 04-17-2001: Message edited by: TwoSheds ]