material-dialogs VS Gson

What part of the chat exactly are you asking about? There are multiple things at play here. E.g For the bottom sheet, you can check out this library: https://github.com/afollestad/material-dialogs/blob/main/documentation/BOTTOMSHEETS.md. For the elevation/shadow effect, check this out: https://proandroiddev.com/statelistanimator-a-powerful-little-tool-for-elevation-animation-4b31781e98a0

Seeing how the go-to library for Material Dialogs (2 and below) has not been updated in the last 2+ years, does anyone have a replacement or fork they’re happy with?

I use Material Dialog https://github.com/afollestad/material-dialogs which allows you to pass in HTML for the message which uses the color as I defined here.

See https://github.com/afollestad/material-dialogs/issues/2051

Project: Material Dialogs (A beautiful, fluid, and customizable dialogs API) Copyright (c) 2014-2016 Aidan Michael Follestad. License (The MIT License (MIT)) https://github.com/afollestad/material-dialogs/blob/master/LICENSE.txt

Most of the time is spent in JSON parsing, specifically in AccessLogAggregator.parseLineJson. Within parsing, the majority of time is spent in org/json/JSONObject.. Since there are faster JSON libraries available, we'll switch to Gson and repeat the tests. To do this, we'll add the following method to our code:

In this concrete example we'll create 3 products. We can then convert this JSON to the list of products using Gson.

Gson has been in maintenance mode for at least 6 years. It's kind of a shame, because the API and implementation were a lot cleaner than Jackson.

For more information on native-image build arguments, please consult the GraalVM Native Image Options documentation. The next listing contains the contents of reflect.json, which contains a bunch of data classes that we need to serialize and deserialize with Gson, as well as our Lambda handler class which the runtime needs to instantiate based on the qualified class name passed to the Lambda function.

The loadModel() method is special. It needs to dynamically update the model path specified in the JSON-formatted template file according to the extraction path of the Jar package. Gson can be used to load and update the JSON object.

If you check out the Gson user's guide, there's a section titled "JSON Field Naming Support" which explains how to do this. There are also lots of examples if you google "gson rename field".

gson

I am not sure if this is what you are looking for, but allot of projects that I worked on used gson to convert between Java objects and JSON strings (https://github.com/google/gson). Maybe you should check it out.

Since this JSON contains the JSON representation of Java objects that are unknown in PoSh/.NET, all you could do is extract the provided object data (values), but not the objects themselves. In order to extract the "real" objects as they're defined, you'd have to start from the Java side, and use a tool like Gson.