slidex | web remote controller from any of your device on a network | Wifi library

In the vertex shader are declared the varying (output) variables N, L, E. But they are never set, because there are identically named local variables which are set. This causes that the values of the varying (input) variables N, L, E in the fragment shader are always (0, 0, 0).

The issue can be fixed by removing the declaration of the local variables and setting the varying outputs:

I did not understand exactly the difference between them. Could anyone help me ?

The technique used in the code snippet of the question is Gouraud Shading.

In common Phong shading means the technique, which does the light calculations per fragment, in compare at Gouraud Shading, the light calculations ar done per vertex.

This means that at Phong shading the light calcualtions ar done in the fragment shader (Not to be confused with Phong reflection model).

Phong shading:

At Gouraud Shading the light calculations are done in the vertex shader, for the corners of the primitives (corners of the triangles). The calculated light is (either in a perspective correct manner or linearly) interpolated for all the fragments covered by the primitive, according to the Barycentric coordinate. This increases the performance, but gives a big loss of quality, especially on large primitives and strong specular highlights.

Gouraud Shading:

Note, the light is not linear distributed on a surface. If the light is only calculated for some samples and interpolated in between them, this causes flat stains.

See the example, which compares the 2 techniques:

I think you misunderstand the purpose of Redux.

Components already have individually scoped state. Redux is not meant to re-invent that wheel. The use case you are describing is perfectly handled by the component state.

Redux is meant to hold information that is relevant across the entirety of your application, or at the very least 2+ disparate sections.

You shouldn't try to overutilize redux. It has it's very valuable purposes, but don't use a hammer when you need a screwdriver.

See? unrecognized selector sent to instance xxx which means you have a method that does not implement at a certain controller.

And reason: '-[App.ViewController aButton:]: unrecognized selector sent to instance 0x7fe464c131c0' which means the method of aButton: in App.ViewController does not implement or you call App.ViewController does not contain this method

It is possible to add DataColumns to a DataTable even when it already contains DataRows.

I don't do JSON much, but my general approach with dodgy XML is to decompose into a stream of key-value pairs where the key is the XPATH "address" and the value is the content of the node (excluding child nodes), then loop through the stream to build the DataTable. Maybe a similar approach can be taken here with JSONPath.