Closed Bug 995358 Opened 10 years ago Closed 10 years ago

[Settings] Reorganize developer menu entries.

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: janx, Assigned: janx)

References

Details

(Keywords: dev-doc-needed)

Attachments

(3 files, 2 obsolete files)

Currently, the Developer menu is confusing and hard to use, and would greatly benefit from having its entries reorganized. Important entries like Remote Debugging should be made easier to reach, and similar entries (e.g. graphics-related) should be grouped together.
Attached file github pull request
Attached image developermenu.png (obsolete) —
This is a screenshot of developer menu entries in their new order. (Sorry for the bad edit on "Developer HUD", I edited the screenshot to make it look more like bug #995124 sub-menus.)
Comment on attachment 8405666 [details]
developermenu.png

Omega, as mentioned in bug 995124, I'm trying to reorganize the developer menu entries in a way that makes more sense. Here is a screenshot of what I'm trying to achieve. Do you agree with these changes? If so, could you please include them in your Developer menu UX spec? Thanks!

P.S. That screenshot was badly edited to make the "Developer HUD" sub-menu look more like the sub-menu in your spec. In the future, I'll update the Settings App's CSS to make sub-menus look like your spec.
Attachment #8405666 - Flags: feedback?(ofeng)
Basically I think it's a good idea to regorgainze them, but I'm not sure whether it's well reorganized in your proposal since I'm not a dev. So I need feedback from another dev. here. Arthur, could you have some comments here?

Since we are refining the Developer menu now, I have one suggestion here:
There are some long strings here and cannot display completely, I need your help to make them shorter. I think all "Enable XXX [v]" can be just "XXX [v]", like:
"Enable hardware compo... [v]"  ->  "Hardware Composer [v]"
Flags: needinfo?(arthur.chen)
Attachment #8405666 - Flags: feedback?(ofeng) → feedback?(arthur.chen)
Flags: needinfo?(arthur.chen) → needinfo?
Flags: needinfo?
Comment on attachment 8405666 [details]
developermenu.png

(In reply to Omega Feng [:Omega] from comment #4)
> Basically I think it's a good idea to regorgainze them, but I'm not sure
> whether it's well reorganized in your proposal since I'm not a dev. So I
> need feedback from another dev. here. Arthur, could you have some comments
> here?

Also needinfoing Anthony who had some good suggestions earlier.

> Since we are refining the Developer menu now, I have one suggestion here:
> There are some long strings here and cannot display completely, I need your
> help to make them shorter. I think all "Enable XXX [v]" can be just "XXX
> [v]", like:
> "Enable hardware compo... [v]"  ->  "Hardware Composer [v]"

I already shortened a few strings, so I can do it further. Removing the "Enable"s makes sense, I'll do that.
Attachment #8405666 - Flags: feedback?(anthony)
Comment on attachment 8405666 [details]
developermenu.png

Looks good to me, thanks!
Attachment #8405666 - Flags: feedback?(arthur.chen) → feedback+
Attachment #8405666 - Flags: feedback?(anthony) → feedback+
Hi Jan, how do you think where we should organize Update Channel and Update URL? (see spec in bug 995124)
Flags: needinfo?(janx)
Hi Omega, I think the way you did it in the spec makes sense, i.e. an "Update" category at the bottom of the Developer menu with two text inputs (the channel needs to be a text input and not an option selector because you might need to change it from e.g. "nightly" to more values like "mako/1.4.0/nightly").

However, I'll leave the update parameters out of the scope of this bug, which focuses on reorganizing just the current options in the menu, and will add the "Update" category in bug 984962.
Flags: needinfo?(janx)
Attached image developermenu.png (obsolete) —
New screenshot with shorter strings, Rik's and arthurcc's f+.
Attachment #8405666 - Attachment is obsolete: true
Attachment #8408188 - Flags: feedback+
Comment on attachment 8405525 [details] [review]
github pull request

Vivien, this change simply reorganizes Developer menu items into categories that make more sense, and shortens the strings so that they fit on a small screen (at least in English).

For convenience, a screenshot shows the new look of the Developer menu. Please have a look :)
Attachment #8405525 - Flags: review?(21)
Comment on attachment 8405525 [details] [review]
github pull request

Actually Arthur, since you already gave feedback on the suggestion, maybe it makes more sense for you to review the code. Please have a look :)
Attachment #8405525 - Flags: review?(21) → review?(arthur.chen)
Comment on attachment 8405525 [details] [review]
github pull request

Thanks for the patch janx! As https://github.com/mozilla-b2g/gaia/commit/70e495701aeb8e99fa1f8191a4508ad9f86d804a has been landed, there are two conflicts due to it removed the labels containing the buttons. Please help resolve the conflicts and request the review when ready.
Attachment #8405525 - Flags: review?(arthur.chen)
See bug 995124 for the updated UX spec.
Comment on attachment 8405525 [details] [review]
github pull request

Hi Arthur, I rebased my commit to resolve the conflicts. Please have another look :)
Attachment #8405525 - Flags: review?(arthur.chen)
Comment on attachment 8405525 [details] [review]
github pull request

r=me, thank you!
Attachment #8405525 - Flags: review?(arthur.chen) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Adding dev-doc-needed because this might invalidate a few screenshots of the developer menu.
Keywords: dev-doc-needed
Attached image developermenu.png
(string "Remote debugging" changed to "Debugging via USB")
Attachment #8408188 - Attachment is obsolete: true
Attached image developerhud.png
Reorganized Developer HUD
Blocks: 986547
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: