1344457 - Redesign main menu in the translate view

Status: RESOLVED DUPLICATE of bug 1519894

(Webtools Graveyard :: Pontoon, defect, P3)

Description

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

(Michal Stanke (Mozilla.cz) [:MikkCZ] in bug 1344120)
> Most of the time I change between the projects/file starting with the left
> most menu. So I would suggest these flows:
> 
> Changing resource only:
> 1) Click the resource menu -> a list will open.
> 2) Pick a resource from the list -> the localization view is reloaded.
> 
> Changing project:
> 1) Click the project menu.
> 2) Pick a project from the list -> the resource list will reload on the
> background and menu text changed to "---" indicating no resource is selected.
> 3) Click the resource menu -> a list for the newly selected project will
> open.
> 4) Pick a resource from the list -> the localization view is reloaded.
> 
> Changing language:
> 1) Click the language menu.
> 2) Pick a language from the list -> the projects list will reload on the
> background and menu text changed to "---" indicating no project is selected.
> 3) Click the project menu.
> 4) Pick a project from the list -> the resource list will reload on the
> background and menu text changed to "---" indicating no resource is selected.
> 5) Click the resource menu -> a list for the newly selected project will
> open.
> 6) Pick a resource from the list -> the localization view is reloaded.
> 
> Reading these flows above, I actually came to the fact, that they are
> applicable for localizers only. For l10n-drivers or any project manager (not
> localizer) might be helpful to change the language only with keeping the
> previous project and resource selected.

Comment 1

[Michal Stanke (Mozilla.cz) [:mstanke][:MikkCZ]]

(Matjaz Horvat [:mathjazz] in bug 1344120)
> Yeah, I had something similar in mind. We should try to reduce the number of
> steps, maybe by automatically openning the project menu after the locale is
> selected, and the resources menu after the project is selected. Or use only
> one big menu that works like the column-view in the Apple Finder. Could you
> file a separate bug to track this?

Comment 2

[Matjaz Horvat [:mathjazz]]

Thanks for filing.

Comment 3

[Matjaz Horvat [:mathjazz]]

(Jean-Baptiste in bug 1354814)
> I would like to ease navigation in pontoon.
> To me, it would make more sense to have first:
> * current project (or localization)
> * all localization
> * then search field
> 
> Most of the time, my work-flow are:
> * go from Resource edition page to project page,
> * go from Resource edition page to all project page,
> * go from Resource edition page to my team page.
> 
> Occasionally, I go from one resource to another, or one project to another,
> based on translation status. You may wish to sort list by completeness.
> 
> thanks for your help

Comment 4

[Matjaz Horvat [:mathjazz]]

(Théo Chevalier in bug 1354814)
> We were several French localizers realizing we’re using similar workflows,
> and that the current breadcrumb menu doesn’t really match our needs.
> 
> For instance, I basically work around this by not using the menu at all, and
> manually editing the URL to go back to https://pontoon.mozilla.org/fr .
> That’s the faster way I’ve found, but still a broken behavior…
> 
> Even reverting the order would probably not be enough to make me use the
> menu, I think I’d love to have a direct link to my team page on the
> translate view (i.e., without having to open a drop down menu and remember
> where this link is located)

Comment 6

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/pontoon/pull/984

Comment 7

[Matjaz Horvat [:mathjazz]]

Translate.Next comes with a redesigned main menu. A potential followup is bug 1578235.