In the last days I've committed some new features to the pageroute & nodefamily modules. Now the nodefamily module comes with another new page-type for pageroute: the lonely node display This page-type will display the node of the configured content-type. This can be used to make an extra page, which acts like a kind of preview. It isn't really a preview, as the node is already stored, but it can be used to present the results to the user.
I've just committed an inital version of the pageroute module. The module can be used to provide an userfriendly way for creating and optional editing several nodes.
I've started working on providing a userfriendly way for filling out the nodes of a profile in a through steps. I started with providing a unique url for each content-type which restricts its number of creatable nodes per user to 1 - as it happens for a nodeprofile content type.
By doing the nodefamily views integration I ended in writing the module views_fusion.
Views Fusion allows one to fuse multiple views into one. So you can build fusioned views that display information that is stored in multiple nodes - useful for tabular views. It uses node relations for joining the appropriate nodes together.
In the last days I was working on the views integration for the nodefamily module. Unfortunately it turned out to be more complex than I thought originally. What I wanted to do, was that views is able to automatically join the node tables of different nodes together, so that one is able to list information of both nodes. But I noticed that this approach has some downsides. They are:
i've started development of the node relations module, i called it nodefamily module. As the module might be useful not only for profile nodes, I've written it generally, so that it may be used without nodeprofiles at all.