So, these days, the skin system has become really, really powerful. Powerful enough to be able to replace themes altogether, but it's up to you to decide.
- Theme settings: the equivalent is in skin.xml, in a thoroughly documented XML format; you can provide your own settings in custom.xml.
- Templates: while right now you can't simply replace an existing template, you can:
(1) write replacement functions for any template in your own Custom.template.php
(2) write replacement functions for any template in skin.xml (or custom.xml, etc),
(3) add code before or after an existing template function (through methods 1 or 2)
(4) very easily add any custom JavaScript or CSS to any template.
--> Overall, I think I could also provide the ability to override entire templates, but I'd like to avoid it, as it may easily break compatibility in the future. But really, it's just a matter of checking the skin folder, and loading the template there, instead of the 'default' template folder.
- Plugins, and skins, can already override, or add to any template functions, manipulate the layout skeleton so that one element will be shown before another instead of after it, etc.
- The only thing that isn't possible for now is completely overriding image sets, or language files, or scripts. I may write code in the future to account for these.
I don't really see anything that can't be done in skins. Granted, it might be easier to do some things in SMF and the theme system, but it's also true that some other things are much easier in Wedge, so... All in all, I think the skin system is better, more modern, and better suited to designers.
Removing themes from Wedge would allow me to...
- Simplify the folder structure. All folders in /Themes/default/ would be moved to the forum root.
- Remove a lot of legacy code from Wedge that I don't even know if it still works at this point. (I think it does.)
Drawbacks:
- It will postpone the first beta release by at least another two weeks.
- Likely to create bugs in the first phase of implementation.
- Heck, personally, I certainly hope I can still 'blame' files and view the 'commit history' for any files that have been moved, without any disruption. I think it'll be all right, but really, it's one of the things I'm worried about. I like blame, it's one of the best tools for debugging in (D)CVS software. Certainly saves me a lot of time.
So, please vote if you have any opinion on this!
- Theme settings: the equivalent is in skin.xml, in a thoroughly documented XML format; you can provide your own settings in custom.xml.
- Templates: while right now you can't simply replace an existing template, you can:
(1) write replacement functions for any template in your own Custom.template.php
(2) write replacement functions for any template in skin.xml (or custom.xml, etc),
(3) add code before or after an existing template function (through methods 1 or 2)
(4) very easily add any custom JavaScript or CSS to any template.
--> Overall, I think I could also provide the ability to override entire templates, but I'd like to avoid it, as it may easily break compatibility in the future. But really, it's just a matter of checking the skin folder, and loading the template there, instead of the 'default' template folder.
- Plugins, and skins, can already override, or add to any template functions, manipulate the layout skeleton so that one element will be shown before another instead of after it, etc.
- The only thing that isn't possible for now is completely overriding image sets, or language files, or scripts. I may write code in the future to account for these.
I don't really see anything that can't be done in skins. Granted, it might be easier to do some things in SMF and the theme system, but it's also true that some other things are much easier in Wedge, so... All in all, I think the skin system is better, more modern, and better suited to designers.
Removing themes from Wedge would allow me to...
- Simplify the folder structure. All folders in /Themes/default/ would be moved to the forum root.
- Remove a lot of legacy code from Wedge that I don't even know if it still works at this point. (I think it does.)
Drawbacks:
- It will postpone the first beta release by at least another two weeks.
- Likely to create bugs in the first phase of implementation.
- Heck, personally, I certainly hope I can still 'blame' files and view the 'commit history' for any files that have been moved, without any disruption. I think it'll be all right, but really, it's one of the things I'm worried about. I like blame, it's one of the best tools for debugging in (D)CVS software. Certainly saves me a lot of time.
So, please vote if you have any opinion on this!
Should Wedge remove theme support, if it provides an equivalent feature set through skins?


