Bug 371001

Description Susan McCourt 2012-02-08 14:59:55 EST

For 0.4, the orion.page.links.related extension works only with commands.  This is fine for internal hrefs or places where we want to make a command.

But there should be other ways to establish a link:

- if someone has defined a link scanner, they could define an orion.page.links.related extension that points to that link scanner and describes what property in the page target is scanned.  For example, one could add a link scanner for git hub repository names, and then define a related link extension that says "use this scanner on the property GitURL"

- A plugin shouldn't have to first define a navigate.command (which is what happens now) in order to then have a related link.  They should be able to specify validation properties and and href callback as part of the extension.  The command could just be a shortcut when you need the command anyway.

- It might also be nice to let the user specify a related link for a particular page.  We would need UI to determine whether the link should apply to all instances of the page, or just that page+resource, etc.  It's sort of like the user being able to generate the plug-in.