If one enabled "Views export", exports a view, saves as a file then puts the export into a module or theme it can be loaded to override a view. It also allows a "reset point" by giving the option to reset the view after altered.

What is the difference here?

Comments

jonskulski’s picture

jonskulski commented

That's a good point and a technique I haven't tried.

Since views_discover_default_views uses module_invoke_all, it would require you module to have a correct weight. That may be a problem, but not always possible and maybe not a big enough problem to require a separate module.

This was a technique I've used on several projects (most notably with expanding Open Atrium) and has been useful enough to extend to a module for our own purposes.

The only other difference is that this could be used as a framework for ctool exportables, cck defaults, panels, etc.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Also, what's the difference to http://drupal.org/project/features ?

jonskulski’s picture

jonskulski commented

Sun,

It's not similar to features at all, the module doesn't package components into a module, export code, or anything like that. The idea is that you can tell drupal to use one view instead of another. Same with panels and any ctools exportable.

Though I think you could implement nicholas' technique using features, if that's what you meant.

jonskulski’s picture

jonskulski commented
Status: Active » Closed (won't fix)
nicholas.alipaz’s picture

nicholas.alipaz commented

Any reason you are bothering with the issue queue since this module is marked as "Abandoned" and this issue hasn't had any comments since April? Are you planning to resume work on this? Just curious really.