Fantastic - this is a great module and I appreciate the video showing how it works without having to install it first...
Great to use a file instead of DB - not only can Drupal aggregate the CSS files (if you set the caching) BUT even if you don't, the browser will aggregate the file anyway.
File system calls are faster than bootstrapping Drupal to generate the CSS on the fly each time it's needed; in addition, using the filesystem means that Drupal can automatically aggregate the snippets into a single master CSS file for the site, saving hits and download time.
Interesting. I guess I really need to dig more into the Drupal internals. I've found that, in php, a single database call is faster than multiple file calls, but you seam to know a hell of a lot more about the Drupal framework than I do. Thanks.
Do you have a blog listing all of the modules you've working on? I really like simpleviews.
@somecomputergeek The reason why database calls seem faster than multiple file calls is because of the latency between you and the server — especially if you have a fast database server, like you seem to have. However, querying the CSS directly puts a lot of load on your DB, and it can fall over during a slashdotting.
Instead, you should use files combined with Drupal’s CSS optimisation feature, which caches all CSS files into a single file, eliminating latency issues. Highly recommended.
give link for download and try please
WMuckaMW 1 year ago
Comment removed
capaneus184 2 years ago
nice module, nice vid
kumquatsta 2 years ago
Fantastic - this is a great module and I appreciate the video showing how it works without having to install it first...
Great to use a file instead of DB - not only can Drupal aggregate the CSS files (if you set the caching) BUT even if you don't, the browser will aggregate the file anyway.
MelismaLife 2 years ago
Cool, but why use files?
Why not put it in the database? You could have multiple rules/snippets and include them inline on pageload without all of those file system calls.
somecomputergeek 3 years ago
File system calls are faster than bootstrapping Drupal to generate the CSS on the fly each time it's needed; in addition, using the filesystem means that Drupal can automatically aggregate the snippets into a single master CSS file for the site, saving hits and download time.
jeffeaton 3 years ago 2
Interesting. I guess I really need to dig more into the Drupal internals. I've found that, in php, a single database call is faster than multiple file calls, but you seam to know a hell of a lot more about the Drupal framework than I do. Thanks.
Do you have a blog listing all of the modules you've working on? I really like simpleviews.
somecomputergeek 3 years ago
@somecomputergeek The reason why database calls seem faster than multiple file calls is because of the latency between you and the server — especially if you have a fast database server, like you seem to have. However, querying the CSS directly puts a lot of load on your DB, and it can fall over during a slashdotting.
Instead, you should use files combined with Drupal’s CSS optimisation feature, which caches all CSS files into a single file, eliminating latency issues. Highly recommended.
JeremyVisser 1 year ago
Cool little module
ximono 4 years ago