Custom CSS and JavaScript files: Isn't this what the .info file does ?

I think what this module adds over the functionality of info is two things:

First, you do not need to edit the module info file itself, you just upload .css or js files (as many as you want) to a folder in your server and they are included automatically.

Second, if you include the file in the info file, you cannot override the theme's css (correct me if I am wrong), so this module rearrange the CSS and JS and put the added files at the end of the head includes, so now your new files override the default ones.

Basically is for easiness of adding new and unlimited css and js files, and allow them to override the themes behavior.

I hope this answer your question.

Another example would be, imagine you have modified the .info file in the theme you are using. And then, this theme gets updated. You would have to edit the info file to add the css and js files again. With this module, there is no need to edit the original theme itself.

If there is something you may discuss further, please comment here. Otherwise, if the explanation I gave is correct and made sense to use this module, please close this issue. Thanks.

The reason this module looks incredible to me is that I've been trying to minimize the amount of theme-hacking that I have to do in order to implement each client website. E.g., I may see a theme that does everything I need it to except that it looks totally "wrong"; then i have to hack the theme to make it look the way I want it to.

That's not really a problem from a tech perspective, but:

* If I mod a theme, I lose update tracking for that theme (or risk over-writing my changes if I update it).
* If all I have to change is the CSS file, I can potentially offload much of the formatting work to someone else.
* Using this approach, should be able to radically simplify our version-control from client to client.
* This approach opens the door to fixing layout or JS-related issues without having to get into your IDE. I.e., it can improve the remote-maintainability of the site.

W.r.t. to JavaScript, I've always had to include a custom JS file that includes things like simple popup scripts. This would, again, mean that I didn't have to include that in the theme itself.

Obviously you can do most of these things with subthemes, but you still need to be in your IDE to properly modify them.

So, I think this is the greatest thing since sliced bread. I've been looking for something like this ever since I started working w/ Drupal 4. Pair it with a simple baseline theme and you're good to go.

[edit to fix unfinished sentence]

Thanks for your feedback and I am glad you find this module useful.

I was just looking for a method for integrating a global css file. Having looked at css injector which is far too heavy for my purposes, I decided to take a look at its sourcecode to simplify it.
Gladly I now stumbled upon this module which (at least in description) does exactly what I want!

One more reason for this module: having more than one theme activated makes it quite complex to keep all themes at the same level. Referencing a file outside the theme's folder ain't good design and copying the necessary files (and successive changes) to each themes folder is fault-prone. As well as editing the .info file every time an update is installed.

I don't see this module as a way to change a theme's own display settings, but I need a way to load small changes to very special css-rules, modifying some loaded modules and even a core css. And all of these changes are not specific to a special theme but must be loaded by every theme I might use.

Thanks for this module!
XL

You are welcome, I am glad you find this module useful!