frontend (global local)
ActiveScaffold is skinnable by creating and using different frontends. These frontends can package up completely different javascript, stylesheets, images, language files, and partials. They are a powerful way of potentially changing the entire UI for ActiveScaffold to blend with your design. Any partial called for by the ActiveScaffold code that is not provided by a frontend will fallback to using the partial from the default frontend.
When more frontends are shipped with ActiveScaffold, or when you have written your own, you can decide which frontend to use either globally or on a per-controller basis.
Examples:
config.frontend = :shiny_new_frontend
config.frontend = :custom_fronted
Frontends were a 2.x feature, when active scaffold was a plugin, and frontends
should be in active_scaffold directory. Since active scaffold is a gem that
feature it's broken, nobody have asked for it I think it's a feature which
nobody was using.
No, theme feature is easier and it should work. When you set a theme, a class
named theme_name-theme is added to main div (the div with active-scaffold
class), so you can add some css rules in your pipeline like:
.theme_name-theme .record ...
Also, you can override colors using scss, you can use any name for the scss
file. Require the scss file in your manifest file and import active_scaffold in
your scss file:
# application.css file
/*
*= require ...
*= require active_scaffold_override
*= require ...
*/
# active_scaffold_override.css.scss
$header_color: #fff;
@import 'active_scaffold';
You can look at active_scaffold_colors.css.scss for available scss variables