resolve/refinerycms — Issue #1081: Refinery Terminology - Engines
Author: resetexistence
Created: 2011-10-13 21:46:13+00:00
State: open

As I work more and more with Rails 3.x and Refinery it is becoming more and more apparent that the term "engines" is a shared term between an idea of extending Refinery and the way it is actually accomplished - with a Rails::Engine or a Railtie.

Because of this shared name it is getting to a point where it can be confusing for developers who are participating on the project to understand the difference between a Refinery Engine and a Rails Engine. Naming variables, methods, modules, and classes can be a choir because of this conflicting namespace.

Because Refinery was birthed pre Engines this probably was never an issue before - the term Engine just made sense since they weren't exactly a huge part of Rails. I think that moving forward it would be best if the terminology was separated.

The extensibility term (Refinery Engine) should be given it's own name to separate itself from how it is accomplished (with a Rails Engine or a Railtie).

I have absolutely no suggestions to what the extensible packages should be called