9
Michael,
The effort required to make it work on both is so large that it simply isn't realistic.
You would need to do everything in div's and such for Bootstrap, while legacy themes expect tables.
You can't do that without writing 2 completely separate templates. And even if you could, it would be really hacky code as a result.
I think that with Xoops 2.6 coming up, we should break with this legacy and make the themes bootstrap friendly - it's way easier to update them, all modules have basic styling implemented that is easy to override and it's responsive.
XOOPS legacy themes are based on tables, so they are as static as can be. Every form is implemented as tables, and if you even TRY to avoid tables, you get the hard task of trying to make it responsive.
I think it's time to break with the legacy themes and move forward with the Bootstrap based themes/modules. If someone doesn't want to upgrade, they can simply stick with XOOPS 2.5.x and the modules for that.
Just my opinion on this. It's better to support 1 thing very well rather than supporting 2 half-cooked solutions.
