From: Reini U. <ru...@x-...> - 2004-04-24 08:02:42
|
Alessandro Vernet schrieb: > When you go from page A to B, to C, to D the PageTrail plugin displays: > > A => B => C => D > > Now when I go back to B somehow (for instance by clicking on "B" in the > PageTrail), PageTrail displays: > > A => B => C => D => B > > That is certainly not a bug, but for me it makes more sense to just > display (as I go back to B): > > A => B > > I modified the PageTrail plugin to do this (source attached), and also > not to use <tt> (let the user of PageTrail decide what font family > should be used). Maybe it would make sense to have an option in > PageTrail to let the user choose what happens when we go back to a page > which is already in the trail. Would that make sense? I don't think so generally. It would make sense, if the user did hit the "Back" button to go back to B. But the path he followed should be printed asis, even if there are cycles. But if he went back to B by clicking on the B link on the PageTrail, it would qualify as similar to the "Back" button. So we cannot accept this patch, because you removed cycles generally, but we will accept patches to support the above described features. And we will try to add it by our own eventually if time permits. One problem: How to undo cookies when the user hit the browsers "Back" button? Referer? The easy patch would be to change the WikiLink in PageTrail. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |