android-libraries: androidx.wear.protolayout:protolayout missing -material.

Android framework version

net8.0-android

Affected platform version

34

Description

Wear.Tiles.Material has been deprecated and replaced with androidx.wear.protolayout:protolayout-material, but this package in not bound. Can we please get androidx.wear.protolayout:protolayout-material added.

thank you

Steps to Reproduce

no package

Did you find any workaround?

no

Relevant log output


About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Comments: 19 (19 by maintainers)

Most upvoted comments

There are examples, such as:

The folder is discovered automatically by convention.

You could file an issue here with a design proposal for bindings:

These are the best docs we have at the moment:

In general, this repo controls a lot of the binding process with this file:

https://github.com/dotnet/android-libraries/blob/2bc0d31cab1fb35507ead8ee3a6997377f975bb2/config.json#L11-L17

This .json file tells the build to look up a maven artifact, and it automatically generates a C# binding project.

This is would be different if you were making your own binding. They did it this way, so they could easily create 100s of NuGet packages.

If you want a new package for androidx.wear.protolayout:protolayout-material, one way to fast track this work is to send a pull request for the feature.

Even if it doesn’t build or isn’t complete. A pull request would help us a lot towards a new package! Simply starting the work, and saying: I got this far, here is the error.

In regards to “support”, most support policies are around security vulnerabilities, etc. These packages are certainly still maintained in that regard. Thanks!

oh, sorry to hear that! Where does this leave the bindings, are you the only one?

No. Team was reduced from 7 to 2.

What is the support model with these, is there no official MS support for these?

I know I will help our team members as community, but cannot guarantee cadence as it used to be. Regarding support - I have no idea. You will have to ask decision makers and they do not hang around.

@moljac, any progress? ta

I am sorry, but no. Some unplanned events occured.

There is PR - WIP:

https://github.com/dotnet/android-libraries/pull/1123

I am in process of returning hardware, getting new hardware, updating my CV and redume and searching for job.

I will do some updates over the summer and I might squeeze this in, but no promises.

We alredy have nugets that have/carry both net8.0 (current) and net10.0 payloads (dlls), but need few more internal tests (MAUI) before releasing them into the wild.

So, it is matter of days or weeks (max, worst case)

Thanks for the feedback.

Most likely after nugets with net10.0 are published.