17
Hello,
today i wanna get a topic to light - the templates hell - it seems like exaggeration but it is the truth, one of the best thing that was done to Xoops is bootstrap and oh boy i'm still exploring its full potential but in my current works using 2.5.6 i implemented it in the theme, and it was very nice but the look of the content area was horrible and i had to change nearly 30 template file and more in the way to fit the look and feel of bootstrap, and i think many others did the same which i think isn't a very healthy thing for a CMS, its very painful when having 5 different breadcrumbs structure and styling in same site:(
I understand that module developers aren't designers but why do we have every time a new major update release, to update all modules - ex: blue move and the later jquery/bootstrap implementation - to fit, ModuleAdmin class was a very innovative approach for a unique GUI all abroad the module's admin area, but why isn't there one front side? an example of this is the ThemeForm class, where updating the form syntax from table one to the bootstrap one was easy?
tl;dr: why not have a ModuleAdmin class like for front end, managing rendering breadcrumbs, categories, media objects, comments? it will surely make developers life easier ;)
Some people like what you do,
-- some people hate what you do,
---- but most people simply don’t give a damn.
