Hello,

I'm interested in creating a "views" browser with a similar user experience to the node relationships module. This module extends the node reference cck field to provide a browser, and just in time node creation interface.

Perhaps we could collaborate with the node relationships module maintainer and integrate a sub-module that provides a similar set of features for views reference as what is provided for node reference?

When I setup a cck field for views reference I select the auto-complete display option (similar to how node reference is configured).

Node Relationships Feature Issue posted here:
http://drupal.org/node/1103132

Comments

danielb’s picture

danielb commented

I don't want to increase the support/maintenance work load with such a feature, especially because I didn't develop it and don't see the value for blocks/views.
Plus, if it can be done via add-on modules for Node reference, why can't it be done the same way here? It really seems like a whole project unto itself.

Basically unless there is block/views specific stuff to be implemented into view reference and block reference, I intend not to maintain new features for this module unless people are used to those features from Node reference or User reference.

danielb’s picture

danielb commented
Status: Active » Closed (won't fix)

Well that's the situation pretty much. I don't know anything about this feature, or have any use of it, and it's more than I'm willing to be responsible for in terms of maintenance. I also have my own plans for the future of this module (and block reference), and that involves trying to reduce the complexity of the code and using the References module's functionality for common functionality. So this feature isn't on the roadmap for me.

However I am confident with a bit of work you would be able to make a module that does what you want, either in addition to block/view reference, or by reusing some code from block/view reference and Node relationships to create a customised module. It seems like a fairly large chunk of work that would be suitable for it's own project.

emptyvoid’s picture

emptyvoid commented

Oh I agree that such modules shouldn't be in the scope of the block or view reference modules, just like the node relationships module isn't part of the node reference module in CCK.

Rather I would expect that two separate modules would exist for each type of interface to content. I've tried to engage the maintainer of the node relationships module in the hope of extending (or creating sub-modules) for the node relationships module to take into account node, block, and view references.

I plan to try and get the module maintainer involved with review the work I do, would you be open to providing feedback as it pertains to block and view reference (baring having time to do so) when I have releases ready for review?

Thanks,