Zen refugee here, discovering Omega since looking to create a responsive development base.

Omega is impressive and ambitious having grid / zone / region layout configuration as settings in the gui. I think this fits for audience of site builder.

Coming from the perspective of developing sites for clients, what I would prefer *not* configurable via settings is toggling the css and js files. I would never want any stylesheets or js toggled off or on by a client. Even though there are permissions for this, while developing, this abstraction adds unnecessary steps - rather than one line in the .info file, it is now at least 2 lines (description not needed), then navigate to settings just to check the checkbox. I think any "site builder" who is editing or manipulating css or js is at the level of editing a .info file, as they are already working with and understanding the site files.

I found adding css and js with the usual syntax in .info (stylesheets[all][] = css/xxx.css) does load the file, but loads before omega's stylesheets. It's the weight ordering we lose control of, even if added to the bottom. I'm still investigating the recommended best practice way to add custom js.

Is there a way to bypass the settings configuration for "Toggle styles" and "Toggle libraries" to enter custom css and js the usual way, either in the .info file, or perhaps in template.php?

If you think this is a good idea for Omega's general use case, consider this a feature request to return toggling, adding and weighting css + js to usual theming methods and taking them out of the settings ui.

Thanks, Omega is really awesome!

CommentFileSizeAuthor
#4 Deactivating "formalize.css" with the UI30.02 KBknalstaaf

Comments

Argus’s picture

Argus commented

Adding user permissions for (parts of) the Omega UI would be a better way to achieve the same.

echoz’s picture

echoz commented

Thanks for responding, Argus. That addresses part of the issue, but does not address the clunky extras of adding css - more than one line and additional step of navigating to settings to check a checkbox. Bigger picture is I'm questioning if toggling stylesheets or js is actually useful from the settings UI, that would make that extra effort worthwhile.

Argus’s picture

Argus commented

Mmm, the path Omega has chosen is to make all kinds of stuff available through the UI: disabling display of page elements, enabling libraries as Formalize and Media queries, showing a grid and last but not least the whole Zone and region configuration.

These can all be done manually and more and more theme's offer support for them, one of Omega's strong points is the UI.

Maybe Omega is less suited for situations where you have laymen (clients) making changes to the theme. But perhaps there is a way to add code that disables these options.

knalstaaf’s picture

knalstaaf commented
StatusFileSize
new Deactivating "formalize.css" with the UI30.02 KB

Deactivating "formalize.css" with the UI

  • admin/appearance/settings/(themename)
  • "Toggle libraries"
  • Uncheck "Formalize"

Done.

tsavory’s picture

tsavory commented

Is that not disabling formalize.js or is the css tied to the js?