This issue has been bugging me for some time- the base/ and mobile/ directories within all of the module asset folders (css/, img/, js/, etc) are awkward to work with, and don't really add much in terms of usefulness. Having to navigate an extra directory level should not be required, and adding layout customizations after one of the application versions is developed should be easier. Additionally, created files should be sorted by name then layout by existing user tools.
The best solution to this problem that I can think of is to name css, js, and template files according to the conventions in the go tree for conditional file inclusions. If you name a file foobar_linux.go, it will only be compiled into the package if the target system is Linux. We could do something similar, although our filter criteria will be different. foobar.css would always be included, foobar_mobile.css would only be included for mobile clients, and foobar_desktop.css would only be included for desktop clients.
Changing this behavior will require essentially rewriting wfdr-cache-monitor and some of the surrounding scripts. Who knows- perhaps we might get a nicer codebase (the current logic for wfdr-cache-monitor is somewhat convoluted and confusing, despite several rewrites).
This issue has been bugging me for some time- the
base/andmobile/directories within all of the module asset folders (css/,img/,js/, etc) are awkward to work with, and don't really add much in terms of usefulness. Having to navigate an extra directory level should not be required, and adding layout customizations after one of the application versions is developed should be easier. Additionally, created files should be sorted by name then layout by existing user tools.The best solution to this problem that I can think of is to name css, js, and template files according to the conventions in the go tree for conditional file inclusions. If you name a file
foobar_linux.go, it will only be compiled into the package if the target system is Linux. We could do something similar, although our filter criteria will be different.foobar.csswould always be included,foobar_mobile.csswould only be included for mobile clients, andfoobar_desktop.csswould only be included for desktop clients.Changing this behavior will require essentially rewriting
wfdr-cache-monitorand some of the surrounding scripts. Who knows- perhaps we might get a nicer codebase (the current logic forwfdr-cache-monitoris somewhat convoluted and confusing, despite several rewrites).