For now, the CMake actions work for a selected few branches only. It would be a pain if we make more branches to add them one by one. It's better to use wildcards so that it will work on all the important branches.

In the README.md file, the following line doesn't make sense.

I don't think anyone would want to use this engine other than to see what it's like to have support for multiple backends with multithreading and to have support for multiple backends.

Please update it to make more sense by changing it to

I don't think anyone would want to use this engine other than to see what it's like to have support for multiple backends with multithreading and to have support for multiple platforms.

We need to detach the descriptors from the pipelines and allow the user or the engine to create them using bindings. This also means descriptors have to be managed externally (which might be a pain). I think it would be best to expose the descriptor [set] manager to the frontend and create descriptors from there.

Originally posted by @DhirajWishal in #8 (comment)

As we all know, every project needs its logo. Currently, Xenon doesn't have one. If you're kind enough to create one for this project it would be of great help!

Requirements

• The logo should have something to do with Xenon (the element).
• We should be able to show it from the repository and also as an icon which we can export with the binary.
• It should be open source! I don't want to deal with any legal nonsense.
• Should be family friendly (I'm looking at you memers).
• Try not to plagiarize anything. That's a big no no.
• The image format should either be SVG or PNG.

You can add the logo image(s) in a comment and if yall feel like a submitted logo is good for the project you can go ahead and like it. The most liked logo will be chosen (if yall decide to make any 🥲).

As of now, the engine doesn't have any concept of lighting. This is not good. For this, my first plan is to add a structure or class called light which has the following properties.

• Intensity
• Color
• Position
• Direction
• Field angle

I'm sure this information can be stored in a single structure like so.

struct Light final 
{
    glm::vec4 m_Color;
    glm::vec3 m_Position;
    glm::vec3 m_Direction;
    float m_Intensity = 1.0f;    // 0 - No intensity, 1 - Full intensity.
    float m_FieldAngle = 15;
};

The lighting can be added to the scene descriptor at a specific binding. We also need to add support for having more than one light source.