commit | 7cf095f23e31d90c04dcc4738e53528a2b7a1833 | [log] [tgz] |
---|---|---|
author | Thomas Stuart <tjstuart@google.com> | Wed Feb 05 00:37:32 2025 +0000 |
committer | Thomas Stuart <tjstuart@google.com> | Mon Feb 10 23:37:07 2025 +0000 |
tree | f76c9ca1984c97bca613d0f0676f32e5c429ac11 | |
parent | e1a0c9fed7a645238781202ac7d46783d9d0b7a9 [diff] |
feat: Implement Meeting Summary Remote Extension This commit implements the Meeting Summary Remote Extension, allowing a remote surface to receive meeting summary information (current speaker and participant count) from the connected VoIP application. Key changes: - **Added `addMeetingSummaryExtension` function:** Provides the entry point for the extension. This function takes callbacks for current speaker and participant count changes, and returns a `MeetingSummaryRemote` instance. - **Added `MeetingSummaryRemote` interface:** Defines the contract for interacting with the remote meeting summary service. Currently, this interface primarily exposes an `isSupported` property to indicate if the connected voip application supports the meeting summary extension. - **Implemented `MeetingSummaryRemoteImpl`:** Provides a concrete implementation of `MeetingSummaryRemote`. This class handles the capability exchange with the remote surface, establishes communication, and sends updates regarding the current speaker and participant count. - **Added End-to-End Test:** Created an end-to-end test to verify the complete flow, from capability exchange to sending updates. - **Implemented in Test App:** Manually tested by integrating the new API into the test application. This feature enables a remote surface to display real-time updates of participant data for the purpose of generating a meeting summary. RelNote: added a new remote surface Meeting Summary extension Test: e2e + manual Fixes: 392960062 Change-Id: I0989d42df4fb802c4d931451814abe177f210a43
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.