35
IMO a module developer duty is separating module templates from module codes.
In other words, In a well-written module everybody could change the look in MODULE/templates OR in themes/THEME/MODULE
Therefor i suggested months ago to move all css/js/images to templates folder as you can see in my version of newbb:
http://svn.code.sf.net/p/xoops/svn/XoopsModules/newbb/branches/irmtfan/newbb/templates_fulldiv_opacity/
So for example if i was not aware of this new thing:
Quote:
using :nth-child(even) in css is only one little "new" thing you should use.
or better this:
http://css-tricks.com/examples/nth-child-tester/
Sorry it is hard for me to understand.
you as a designer can add it yourself and provide a better template for me as a module developer.
As a module developer I just look at xoops.css for available css (include css3) codes and if i dont find a code to solve my issue i search in the net. So
it is the duty of core team to enhance css and js.
But anyway im totally agree to remove all hard-coded css like inline css coding. (css in html files)