Closed Bug 982949 Opened 11 years ago Closed 11 years ago

Ringer selection should have a default value.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:2.0)

RESOLVED FIXED
2.0 S3 (6june)
feature-b2g 2.0

People

(Reporter: swilkes, Assigned: squib)

References

Details

(Whiteboard: [fxos-bug-bash-1.4] [p=2])

Attachments

(2 files)

Settings > Sound > Ringer (Helix 20140306040204): There is no default value. Expected: There is a default value selected. Also flagging Omega to specify the default value.
Flags: needinfo?(ofeng)
I think this is a dupe.
Component: Gaia::Settings → Gaia::Ringtones
Whiteboard: [fxos-bug-bash-1.4] → [fxos-bug-bash-1.4] DUPEME
Here is the spec.
Flags: needinfo?(ofeng)
See Bug 991026 for the Sound UX spec update.
Assignee: nobody → dkuo
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Whiteboard: [fxos-bug-bash-1.4] DUPEME → [fxos-bug-bash-1.4] DUPEME [p=2]
Target Milestone: --- → 2.0 S1 (9may)
Depends on: 973445
Whiteboard: [fxos-bug-bash-1.4] DUPEME [p=2] → [fxos-bug-bash-1.4] [p=2]
Arthur, This patch is to fix the default values of the tones in the sound settings, it will fix bug 982951 as well since the code blocks are the same. The main idea is to use the file paths as id to find the preloaded ringer/alert tones then display them on the ui, also the tone name can be localized if the users change the languages, which also fixed the potential bugs. As you know, sound settings are being refactoring in bug 973445, my patch is base on the refactored code so probably you will need to wait for it landed or pull the patch in bug 973445 yourself to test it, sorry about that. Would you please review this patch? thanks.
Attachment #8415033 - Flags: review?(arthur.chen)
Comment on attachment 8415033 [details] [review] patch after bug 973445 landed This patch also modified the build script so I think we should let owner/peer to also know about this, Yuren, would you please see the build script part and give us some feedback? thanks.
Attachment #8415033 - Flags: feedback?(yurenju.mozilla)
Blocks: 982951
Comment on attachment 8415033 [details] [review] patch after bug 973445 landed looks good to me for build script part.
Attachment #8415033 - Flags: feedback?(yurenju.mozilla) → feedback+
Comment on attachment 8415033 [details] [review] patch after bug 973445 landed Thanks for the patch, dominic! Please check my comments in github.
Attachment #8415033 - Flags: review?(arthur.chen)
Please, I beg of you: don't land this. It will bitrot my ringtones branch pretty badly. I promise I'll incorporate whatever changes are here into my branch.
Oh, and see bug 960329 for my branch.
Ok, looking at this a bit more, I guess I should probably explain some of my motivation for asking that this not get landed until my patch does: the main reason is that I'm changing how we store ringtones in mozSettings, and the way I'm doing things should simplify a few parts of this patch. Overall, I think it makes more sense to wait on this bug until after bug 960329 is landed, since that will reduce the total amount of changes we need to make in the settings app. The main thing I've added in my branch that helps with this is that every ringtone now has a unique ID that gets stored in mozSettings. I'm also thinking that instead of deriving the l10n ID for ringtones from the filename, we can use some of the changes I made to actually store the l10n ID in mozSettings and just share l10n files between the ringtones and settings apps.
Don't worry Jim, I am not going to land this yet and it's also blocked by bug 973445. Apologize for not notifying those changes about the ringtones to you because I am working on the 1.3T+ music blockers(you knew that) and just let this patch pending here. And thanks for letting us know the huge patch of ringtones, I think your idea is very similar to my patch and also address the localization issue in ringtones, we should land bug 960329 first, it will be nice that this bug can concentrate on the default values for the ring/alert tones, which most of the works should be in the build script and some in the sound.js in settings.
Target Milestone: 2.0 S1 (9may) → 2.0 S2 (23may)
Here's a quick idea for what we could do based on my branch: https://github.com/jimporter/gaia/commit/243d514a3d3b4cc0d7b9e5885d977269dde5726a The only downside to the above strategy is that I'm changing how dialer.ringtone.name is defined so that I can store either a string *or* an L10N ID in it. Maybe we can migrate the old values somehow.
I fixed a few issues in my branch, so here's the commit now: https://github.com/jimporter/gaia/commit/c1ed7b1eaa97fb6258d3038a29fb2f1ae4e5d445
Depends on: 960329
Updated my branch again. Here's the whole branch (just look at the latest commit, though): https://github.com/jimporter/gaia/commits/ringtones-default
Cool, and if you don't have time to write the tests, you can just pick up those I have for now or I can help to add after you landed you branch, great work Jim!
Ok, I'll merge your code into my branch. I should be able to keep most everything you wrote; it's just that it'll be easier to do the merge with your code on top of mine, rather than the other way around. Taking this bug to reflect that I'm finishing things up.
Assignee: dkuo → squibblyflabbetydoo
Status: NEW → ASSIGNED
feature-b2g: --- → 2.0
Target Milestone: 2.0 S2 (23may) → 2.0 S3 (6june)
Landed as part of bug 960329.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
No longer blocks: 982951
No longer depends on: 973445
Component: Gaia::Ringtones → Gaia::Settings
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: