Is there any reason why compass_formalize (https://github.com/pengwynn/compass_formalize) hasn't been added to the Gemfile by default?

Comments

roblav’s picture

Issue summary: View changes
fubhy’s picture

Status: Active » Closed (won't fix)

Yeah.. I am not a huge fan of formalize. It's quite easy to use the built-in compass tools to do anything you want with your forms. I am not a fan of hacking forms any more than what the respective browser-os-combo does. There is a reason why certain form elements are controlled by the OS, not the browser and the served CSS so easily. Think about the widgets that are exposed on mobile devices. In general, if you try to do more to your forms than what you can do without any JS polyfills and other browser hacks you are probably breaking something else down the line and potentially making your forms less accessible. Form elements should always be treated with immense care and designers need to learn and understand to not try and force any overly exagerated visual effects on forms. It's not practical and not nice for UX either (in most cases).

That being said, even if you want to use formalize, it's easy to add that to your Gemfile, config.rb and Sass files. We can't include every Gem in the Sass world anyways. The starterkit Omega ships with can be extended and should be extended if you need any additional stuff. It's just a default blueprint. Feel free to modify the generated subtheme.

But yeah... I am not going to add it to the default starterkit for the reasons mentioned above. Sorry!