litho | declarative framework for building efficient UIs | User Interface library

A pcolormesh is a mesh of rectangles, where individual heights can be assigned to rows (and columns). The first parameter of pcolormesh are the mesh borders on the x-axis, the second for the y-axis. Such a mesh needs one row and one column more than there are values, so 2 in the x-direction and 7 in the y-direction for a 1x6 mesh.

The values need to be stored in a matrix (the third parameter). To create the matrix, the following steps are taken:

• df['litho'] is the list of strings
• [:-1] takes all elements except the last
• .map(d2) maps the strings to numbers
• .to_numpy() converts to pandas series to a numpy array
• .reshape(-1, 1) converts the 1D array to a 2D array, where the number of rows is equal to the length of the 1D array (-1 means: the number needed to make the 1D and 2D array have the same number of elements) and the number of columns is 1

Note that vmin and vmax need to be set explicitly because not all possible values are present in the matrix.

For the figure size, it's easier to use the object-oriented interface, using fig and ax instead of plt.. fig, ax = plt.subplots(...) allows to set the size, and can also create multiple subplots.

Apart from the figure size, also the aspect ratio of 'ax' (the inner plot) can be set. In the example below, an aspect ratio of 0.01 is used, which means the 442 units in the y-axis will occupy the same number of pixels as 100 times the 1 unit on the x-axis.

You have to create a Radio group and manage state from there, that is the parent:

Here is one way of doing it:

Not smth we are aware of. But due to its declarative nature it's not hard to build one by yourself. Conceptually, you'll just need to propagate all props from json fields to Component props and a special field for a Component type.

Adding the following dependecy solves the problem. Just incase anyone ever needs it.

implementation 'com.facebook.fbjni:fbjni:0.0.2'

Because Litho uses declarative approach to building UI, binding comes naturally – you just can't change a property on a View in-place, you need to recreate a new Component. So, when a new data comes from whatever source you have, you'll just recreate a Component and set it to LithoView or ComponentTree.

Another way is to pass your Controller as a Prop, subscribe to data changes and on every update of data, call a State Update for the Component, let's say. For subscribing/unsubscribing you can use OnAttached/OnDetached methods: https://fblitho.com/docs/onattached-ondetached

Let me know, if you need more info

The problem is when your program first runs it sets currentCalories variable to "Total"

You have the option of using @TreeProps which expose a prop to the entire subtree for a component. We generally don't recommend this approach because it can make the dependencies of your Component hard to reason about -- for example if you want to re-use that Component in another tree, it's not clear from the creator of that component that there's a contract that the Component must be hosted in a subtree that defines that specific @TreeProp.

The warning you screenshot is not really correct, I will work on editing it or removing it.

If you really want to use Litho, you can download the image, and convert it to a Drawable object.

There is not much difference from adding any other custom view to Litho. You'll need to create a MountSpec for PlayerView and then include that MountSpec as a Component.

More info about MountSpecs.

And here is a good example of MountSpec implementation for a ProgressBar: ProgressSpec