Confirmed users
146
edits
WebAPI/AudioChannels: Difference between revisions
→Refactor Audio Channel Service
Alastor Wu (talk | contribs) |
|||
| Line 242: | Line 242: | ||
* Gecko: The concept of refactoring the audio channel service is to deal with those issues that we couldn't solve by the existing mechanism in gecko, and we will need the changes(in below) in both gecko and gaia to have a new management. | * Gecko: The concept of refactoring the audio channel service is to deal with those issues that we couldn't solve by the existing mechanism in gecko, and we will need the changes(in below) in both gecko and gaia to have a new management. | ||
** '''New browser api''': {{Bug|1113086}} - this is the major part for the new browser api so that the gaia system app is able to control each iframe/app's audio channel, such as allowing or denying those types we have in b2g. | ** '''New browser api''': {{Bug|1113086}} - this is the major part for the new browser api so that the gaia system app is able to control each iframe/app's audio channel, such as allowing or denying those types we have in b2g. | ||
*** It's almost completed, just lacking of the volume control of the FM Radio. | |||
** '''Telephony''': {{Bug|1129882}} - The new audio channel browser api will be implemented base on the foundation of media element, but the telephony api does not use media element to produce sound, so we need the telephony api to bind on a specific window(callscreen), just like the other apps did. | ** '''Telephony''': {{Bug|1129882}} - The new audio channel browser api will be implemented base on the foundation of media element, but the telephony api does not use media element to produce sound, so we need the telephony api to bind on a specific window(callscreen), just like the other apps did. | ||
** '''VOIP''': {{Bug|1126224}} - There will be 3rd party apps that use webrtc api to implement voip services, and to fit the ux spec, these apps might behave different from the gaia callscreen app, so probably we will need a new type called "voip" to distinguish from "telephony" and "voip" audio channels. | *** Review finish, wait for landing. | ||
** '''VOIP''': {{Bug|1126224}} - There will be 3rd party apps that use webrtc api to implement voip services, and to fit the ux spec, these apps might behave different from the gaia callscreen app, so probably we will need a new type called "voip" to distinguish from "telephony" and "voip" audio channels. | |||
*** This issue is paused now, since we have no the consensus about whether we really need the "voip" type. | |||
** '''System''': {{Bug|1142933}} - The ux spec has specified a new audio channel type called "system" to represent those sounds that system use, such as the keyboard, screen lock or screenshot... | ** '''System''': {{Bug|1142933}} - The ux spec has specified a new audio channel type called "system" to represent those sounds that system use, such as the keyboard, screen lock or screenshot... | ||
*** Review finish, wait for landing. | |||
* Gaia: The system app will use the browser api({{Bug|1113086}}) to control all the audio channels in gaia, it means we will move the audio channel service from gecko to gaia, since gaia has more window related information then gecko and can do a better management. | * Gaia: The system app will use the browser api({{Bug|1113086}}) to control all the audio channels in gaia, it means we will move the audio channel service from gecko to gaia, since gaia has more window related information then gecko and can do a better management. | ||
** '''Audio Channel Manager''': {{Bug|1100822}} - we will introduce this new module in system app, to manage the audio channels. | ** '''Audio Channel Manager''': {{Bug|1100822}} - we will introduce this new module in system app, to manage the audio channels. | ||