-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeroen Vermeulen wrote on 07/09/10 03:35: > > This may be a silly idea. It came from googling bugs by number, which > sometimes takes one to unexpected pages. > > We can link bugs to branches and vice versa. Doesn't that mean that > users would expect to see the bug's Code tab refer to the branch, and > the Bugs tab for the branch refer to the bug? > > Similar for blueprints and bugs, and probably other cases where we link > our respective applications' quintessential items. >...
The approach I took when designing the tabs was this: An object should have its own set of tabs if *most* of the tabs could apply to it. For example, a distribution source package has its own tabs, because while it doesn't have Answers, it does have an Overview, Code, Bugs, Blueprints, and Translations. But a distribution milestone does not have its own tabs, because while it could have an Overview and Bugs, it would not have anything else of its own. Bug reports fall into the latter category. If the tabs for a bug report page were specific to the bug report, "Code", "Bugs", and "Blueprints" would be the only tabs that could ever do anything -- and most of the time (when there are no linked branches or blueprints), "Code" and "Blueprints" would both take you to empty pages. Anyway, the bug report page itself *already* lists all the branches and blueprints that the report is linked to, and those lists are almost always very short, so there wouldn't be much point in putting them on separate pages. (If you were thinking that those links would go directly to the relevant branch or blueprint, remember that there can be more than one of each for a given bug report.) Having said all that, the navigation tabs are unfortunately broken in Launchpad currently, in that there is no reliable way of telling where they will take you. For example, on a build page <https://launchpad.net/ubuntu/+source/socnetv/0.81-1ubuntu2/+build/1883317>, the "Ubuntu" header implies that the tabs are for the distribution, but they are for neither the distribution *nor* the build. This was not a problem in Launchpad 2.0. - -- Matthew Paul Thomas http://mpt.net.nz/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyGJicACgkQ6PUxNfU6ecqPHQCeNniNfDEITjTVyL+fgm693y+t IXUAoLZK98YHZ7s8IXwREN+nXdvI/W72 =alhY -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
