|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation routine, firewall configuration, button label "tree" not suitable | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Evamaria Fuchs <evamaria.fuchs> |
| Component: | Installation | Assignee: | Edith Parzefall <eparzefall> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | ke, locilka |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot of YaST2 Firewall (10.0) - [Help]
Screenshot of YaST2 Firewall (10.0) - [Tree] |
||
|
Description
Evamaria Fuchs
2006-02-01 17:14:37 UTC
I'd say Eva's observation is valid (even if we did it differently in the past). Either change it immediately for the next translation round, or postpone it after the box release. could I get a screen shot please? (In English) I am guessing it is some option to switch to a tree view, but I need to see it to think about what other options make sense. It probably calls the standard firewall module, so I will add that maintainer to the CC. Created attachment 66106 [details]
Screenshot of YaST2 Firewall (10.0) - [Help]
Created attachment 66110 [details]
Screenshot of YaST2 Firewall (10.0) - [Tree]
The layout comes from the 'DialogTree.ycp' module but I haven't found the very exact location ;) However I think it's probably somewhere in the 'base.pot'.
It's also used for DNS Server, DHCP Server and maybe others.
I definitely do not think "Catalog" is at all appropriate here. Tree is used because it opens the tree view of the module rather than the view showing the Help. I think you can navigate with Next anyway. So I'd say the issue is a bad translation and that we ought to improve the comment on the message to clarify that it opens the tree view. (see the first screenshot) [Back] & [Next] are navigation buttons between dialogs, Thet's why the [Back] button is disabled - there's no other dialog before this one. [Next] would lead to dialog showing the Firewall's summary. [Help] button is here to get the help for the current selected dialog inside the Tree-presentation. If you clicked on the [Help] button, you would get (see the second screenshot)... Here, the [Help] button is replaced with the [Tree] button which would change the view back (by disabling help and enabling the Tree-Menu). Please note, that that tree could have more tree-levels inside. See the `yast2 sysconfig` for another example. In fact it is a `Menu-Tree` but think about long translations. I'd vote to label the button "Hide Help" or "Tree View"--both versions are not that long. As long as we stay with "Tree" a German translation such as "Baum" is perfectly okay. That button is internal to the YQWizard widget. Its label is not configurable, so all discussion how to rename it is a moot point. The one thing I don't like at all of this interface is that the help panel is misused for navigating lots of subdialogs. IMHO this is not obvious at all to the user. And using a tree (which is what the YQWizard provides) when it is really a flat list adds to the confusion. IMHO navigation between the subdialogs should be moved out here into the dialog's main work area. This would also keep the help text visible by default. In particular firewall settings do deserve extensive help; all those parameters are in no way obvious. It's too late for a redesign now. mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( |