Rethinking Templates vs. Resource Types (aka Content Types)

If we could add a custom right-click menu, I think we could come up with some work-arounds: https://forums.modx.com/?action=thread&thread=63810&i=1

A plausible work-around could exist inside of a CMP, but the UX would probably be too disruptive.

Hey Y'all

Since this thread started i have developed a Simplx Extra that does exactly what we have discussed here. And more. It is called Simplx Mirage and can be found at:

https://gist.github.com/1350981

Its pretty much uber nice if i may say so myself

Please help me to debug!

Thanks,
Lars

Blog posts on Mirage:

http://larscwallin.blogspot.com/2011/11/introducing-simplx-mirage.html
http://larscwallin.blogspot.com/2011/12/introducing-simplx-mirage-part-ii.html
http://larscwallin.blogspot.com/2012/01/introducing-simplx-mirage-part-iii.html

What's the status on this? This is EXACTLY where MODX should be heading

Did you try Mirage? It is pretty darn great I think

No actually, haven't had time to properly try it--but in truth I was wondering when modx will integrate natively...

I wouldn't hold my breath for that one

While looking at the Mirage site, I noticed one major misconception, which appears to be the underlying rational for the entire project.

Template variables do not extend the template. They extend the resources that use that template. When TVs were first developed, templates were simply a convenient way to categorize resources that would use the TV. I've always felt that this was a mistake, that a new table for resource categories should have been used. If it were actually two tables, one for categories and one for the resource/category relationship, then resources could be assigned to multiple categories, which would open up a lot of very useful possibilities.

If someone wants to make templates into something they are not and never were intended to be, that's fine. But I seriously doubt that such an inversion of the function of templates will ever be incorporated into MODx itself.

Indeed as you say Resources in MODX are extended, and categorized, using a Template.
Templates in turn are defined using a name and a set of fields, which in turn are typed as String, Number, Date, List etc.

When a Resource applies a Template such as a Car, it inherits all the fields of this "category", extending it's set of default fields.
In essence the Resource changes it's public appearance saying
-"From now until I say when I can be expected to have a Registration Number, a Color, a Brand and a Price! ".

Mirage is just a manifestation of this idea