> Please continue to offer suggestions for improvement. What about adding javascripts as part of the skin (as it is done for css) ? Motivation: skins could be made responsive and/or include more dynamic components and there is no way to do that without a bit of javascript. Large javascript in the header or footer looks a bit hacky (and the javascript cannot be cached). Maybe v2 of the skin system is a good time to add something like this :
<script type="text/javascript" src="/myrepo/script.js?default"></script> Lately I have proposed a Bootstrap based skin: https://flintcode.com/repo/skin The next step would be to use the .less files (the css source files) from Bootstrap to create a custom tailored version of Bootstrap for fossil, instead of having it the other way around (aka tailoring the generated html of fossil for Bootstrap using hacky javascript). LESS provides functionalities (such as css inheritance) to do that. My question is about the licensing: would it be OK to include a byproduct of Bootstrap (MIT license) in Fossil ? Samuel _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
