We have a "Navigation" toolbar that only has the Back (.uno:NavigateBack) and Forward (.uno:NavigateForward) arrows to navigate a history of document positions. Since LO 7.2 and the fix for bug 115817, the functionality is included in the "Navigate By" tool in the Navigator, when the "Recency" category is selected. (The "Navigate By" companions arrows are usually .uno:ScrollToPrevious and .uno:ScrollToNext, but change to .uno:NavigateBack and .uno:NavigateForward when "Recency" is selected.) The "Navigation" toolbar is therefore less useful, but users might still rely on it for UI customisation so I would be against removing it or replacing its commands. However, I think it needs renaming, in order to: - avoid confusion (with Navigate By and the Navigator); - clarify what it is used for; - make it consistent with the "Recency" name used in the Navigate By tool. My suggestions: - "Recency Navigation" - "Recent Locations" - "Navigate by Recency" - "Navigate Recent Locations" ...other suggestions? Is "Position" better than "Location"?
The 'Navigation' TB was implemented exclusively for the recency navigation as found in web browsers. It tracks edit cursor positions within a current documment. Its major annoyance was its pop-up mode, since tamed by a default fixed docking appended to the Standard TB. Recency had been missing from the SB Navigator, which had focused on movement between document objects. Inclusion of a Recency mode in the Navigator brought it edit cursor stack movement, with enhanced expansion of the types of cursor events being tracked and available to move between. With suppression of the pop-up, its appearance in the View -> Toolbars menu list with labeling as the "Navigation" is benign. The TB is obviously not the SB Navigator, even for the Benjamin user. I don't see advantage to renaming, and of course no reason for removal. Recency subtly describes behavior of the stack, a distinction needed in the SB Navigator deck, but in function it remains Navigation and the name of the TB works. -1
The close naming is a source of confusion. How about "History" or "Navigation History"?
(In reply to Heiko Tietze from comment #2) > The close naming is a source of confusion. How about "History" or > "Navigation History"? Eww, no. "Recency" would be most correct TB name, but a horrible burden for l10n/i18n to localize. So instead "Recent Positions" for TB name, keeping current button names "Back" / "Forward"? That would remove any Navigation vs. Navigator ambiguity.
(In reply to V Stuart Foote from comment #3) > So instead "Recent Positions" for TB name Or "Position History" (which combine recent proposals; also "History" is known from webbrowsers, with the idea of keeping a chronological order)
(In reply to sdc.blanco from comment #4) > (In reply to V Stuart Foote from comment #3) > > So instead "Recent Positions" for TB name > Or "Position History" (which combine recent proposals; also "History" is > known from webbrowsers, with the idea of keeping a chronological order) OK "Position History", +1 Should be translatable
+1 for "Position History"
Sounds like "Position History" is the top contender - which makes me think: do we also want to make the Navigate By dropdown's text consistent with it, by replacing "Recency" with "Position History"? "Navigate by - position history" works well. I think it would make sense and clarify the role. "Recency" makes it sound like "how recently the object was created". In that list, it's the only element out of 21 that is about about "things that don't exist anymore". All other elements are about "what currently exists in the document" (or session, for Reminders). We better make that extra clear with an appropriate, consistent label. "Position History" (16 chars) wouldn't be too long for that Navigate By list - "Wrong table formula" is already longer (20 chars).
(In reply to Stéphane Guillou (stragu) from comment #7) +1 Tracks exactly with what I was thinking all the way down to the "Position History" length compared to the "Wrong table formula" length.
(In reply to Stéphane Guillou (stragu) from comment #7) > Sounds like "Position History" is the top contender - which makes me think: > do we also want to make the Navigate By dropdown's text consistent with it, > by replacing "Recency" with "Position History"? "Navigate by - position > history" works well. > I think it would make sense and clarify the role. "Recency" makes it sound > like "how recently the object was created". In that list, it's the only > element out of 21 that is about about "things that don't exist anymore". All > other elements are about "what currently exists in the document" (or > session, for Reminders). We better make that extra clear with an > appropriate, consistent label. > "Position History" (16 chars) wouldn't be too long for that Navigate By list > - "Wrong table formula" is already longer (20 chars). No objection, +1 "In for a Penny..."
How about "Navigate History" or "Navigate Positions"? I'm also ok with "Position History", although I like that less.
(In reply to Eyal Rozenberg from comment #10) > How about "Navigate History" or "Navigate Positions"? > > I'm also ok with "Position History", although I like that less. I think the idea is to remove navigate/navigation/navigator from the mix and avoid any potential to misidentify. "Position History" seems to work best in that context.
(In reply to V Stuart Foote from comment #11) > (In reply to Eyal Rozenberg from comment #10) > > How about "Navigate History" or "Navigate Positions"? > I think the idea is to remove navigate/navigation/navigator from the mix and > avoid any potential to misidentify. Indeed, and it has the added benefit of being able to use the same string in Navigate By (without repeating "Navigate"). I think we need both "history" for the familiarity with browsers, and "position" to clarify it's about cursor position (and not age of objects).
We discussed the topic in the design meeting and welcome both suggestions. Code pointer: * UIName for the navigationobjectbar in officecfg/registry/data/org/openoffice/Office/UI/WriterWindowState.xcu * ST_RECENCY in sw/inc/strings.hrc