2011-01-09, 00:45
Hi Hitcher,
I got to thinking. Considering that you have themes in the "Media" folder, labeled with the ".XBT" extension, could this folder do 'double-duty' and act as a Mod directory as well? Here's what I was thinking... If you 'extend' the focus of the theme to encompass the entire add-on directory, you could, in theory, use it to replace other items within the skin itself.
Consider this. You build a theme that includes the subdirectories called "extras/homeicons" and inside this, you have replacement home icons. Users could now build their themes using different icon sets. Expand this thought, and if you have a theme that includes the "720" subdirectory, then someone who has modded the "Includes.XML" so that they have their custom home menu items (for me, who uses "Icon View" and presently, does not have access to add submenus through your skin) on there, and you have essentially built a "mod within a theme" functionality.
The best part of this (I think) is the fact that people would be able to build their mods to be included in the themes, and when Alaska Revisited is modified, the mods are automatically built-in, and would not need the user to reapply them. We could police mods that 'break' when the skin is updated, and they could be removed from the 'official' release at your discretion.
I'm just thinking out loud here, but I think the possibility shows a lot of promise. I, for one, always enjoy having the latest version of a skin, and the ability to include icons, views, and different configurations inside the skin theme functionality itself would be a huge boon.
What do you think?
I got to thinking. Considering that you have themes in the "Media" folder, labeled with the ".XBT" extension, could this folder do 'double-duty' and act as a Mod directory as well? Here's what I was thinking... If you 'extend' the focus of the theme to encompass the entire add-on directory, you could, in theory, use it to replace other items within the skin itself.
Consider this. You build a theme that includes the subdirectories called "extras/homeicons" and inside this, you have replacement home icons. Users could now build their themes using different icon sets. Expand this thought, and if you have a theme that includes the "720" subdirectory, then someone who has modded the "Includes.XML" so that they have their custom home menu items (for me, who uses "Icon View" and presently, does not have access to add submenus through your skin) on there, and you have essentially built a "mod within a theme" functionality.
The best part of this (I think) is the fact that people would be able to build their mods to be included in the themes, and when Alaska Revisited is modified, the mods are automatically built-in, and would not need the user to reapply them. We could police mods that 'break' when the skin is updated, and they could be removed from the 'official' release at your discretion.
I'm just thinking out loud here, but I think the possibility shows a lot of promise. I, for one, always enjoy having the latest version of a skin, and the ability to include icons, views, and different configurations inside the skin theme functionality itself would be a huge boon.
What do you think?