Links Package: add views support

Annnnnd the patch to links.module that includes it if views.module is installed.

This version of links_views.inc corrects the issue with display of local and global link titles. Since the population of each field depends on a given site, there are now three handlers for the link_url: display as URL, display as local title, and display as global title. Should take care of your problem with the blank titles.

Syscrusher, thanks for the response. I definitely see your point about local vs. global link titles. Your method (display the local title if it's available and the global title if it's not) should be very easy to implement. I can make that change this evening.

Regarding the multiple-line-items-per-node, that behavior was intentional. Each link is a separate record, at Views.module demonstrates the same kind of behaviour with taxonomy or amazon-node driven views, all of which can have multiple records associated with a node. For normal use of the weblinks.module, though, most users will never encounter the issue, and it will allow them to create 'slice and dice' browsable weblink archives via views.module.

Additional benefits of having each link treated separately (rather than concantenated together into a single field):

1. A links page can list every URL that's been mentioned on the site, regardless of what node it was posted on. The 'recognize links in the body of each node' setting links.module offers makes this even more powerful.
2. With creative use of Views, it's possible to list a node's linked URLs on a separate tab, like www.example.com/node/1/links, or to easily display them in a sidebar block.

Listing ALL the links associated with a node in one field (as one might want to do in a node listing) is possible with the views module, but if it's done, I think it would probably be best to put that in a separate field as far as views is concerned. 'All associated links', or something like that.

Obviously, I could be wrong ;) But that's what I had in mind when I put the .inc together.

Here's a patch that changes the field behavior: now, there's a single 'Link title' field that displays the local title if it's available, and the global title if there's no local one. The handlers have been changed a bit, so that link titles can be shown as clickable links or plain text.

It's not ready for prime time, but below is an example of the sort of stuff that's possible with it: this view definition shows all the attached links for a node in a separate tab, rather than below the body of the node.

<code>  $view = new stdClass();
  $view->name = 'node_links';
  $view->description = 'a tab listing all links associated with a node';
  $view->access = array (
);
  $view->view_args_php = '';
  $view->page = TRUE;
  $view->page_title = '';
  $view->page_header = '';
  $view->page_header_format = '1';
  $view->page_footer = '';
  $view->page_footer_format = '1';
  $view->page_empty = '';
  $view->page_empty_format = '1';
  $view->page_type = 'table';
  $view->url = 'node/$arg/links';
  $view->use_pager = TRUE;
  $view->nodes_per_page = '20';
  $view->menu = TRUE;
  $view->menu_title = 'links';
  $view->menu_tab = TRUE;
  $view->menu_tab_default = FALSE;
  $view->menu_weight = '';
  $view->sort = array (
  );
  $view->argument = array (
    array (
      'type' => 'nid',
      'argdefault' => '1',
      'title' => '',
      'options' => '',
    ),
  );
  $view->field = array (
    array (
      'tablename' => 'links_node',
      'field' => 'link_title',
      'label' => 'title',
      'handler' => 'links_handler_field_title_clickable',
    ),
    array (
      'tablename' => 'links_node',
      'field' => 'clicks',
      'label' => 'clicks',
    ),
  );
  $view->filter = array (
  );
  $view->requires = array(links_node);
  $views[$view->name] = $view;

Ehhhh, here's a patch with a few typos and some terminology cleaned up (always use 'link' instead of 'weblink,' etc.)