Explicit registration over window pollution.

[jeffijoe]

I think it would be better to explicitly register your views as "components", like so:

class GoogleMapView extends View {

}

// Register here - first parameter would be the element name, second is the View class.
Marionette.ViewTag.registerComponent('google-map', GoogleMapView);

Ultimately I'd like to get rid of the cp- prefix.

[grabcode]

I imagine this ticket could be sliced into 3 sub-tickets:

• Provide scope via configuration or parameter (on the fly) - the code is ready for that, it is a matter of introducing a config layer
• Creation of a View/Viewtag store (a map) to basically overwrite the default "algo" in charge of translating tags into classname. It is not hard at all, merely a matter of configuration. So it is somehow dependant on the above point.
• Update regex to look up any tags: this one is a bit of a concern as it would have performance concerns, and compatibility issues. It would indeed require some caching mechanism, and the introduction of some sort of DSL. That's fine, we just want to do it well.

I'll create a ticket for each of this point later today. Please come back to me with any comments.

[jeffijoe]

The regex would be dynamic as it would only look for tags that are registered.

[grabcode]

That's an appealing idea @jeffijoe, though I can't picture at 100% how this would work yet. I actually think that we would be better off using a memoized function to deal with the store. Easier to maintain, to test, to extend, and it might actually be more performant as a dynamic regex would costy since it would need to be "compiled" everytime (via RegExp constructor).

[jeffijoe]

@grabcode it would only be compiled when you add a new component, not for each render.