Add imgui 1.74

[Hopobcn]

Specify library name and version: imgui/1.74 https://github.com/ocornut/imgui

• I've read the guidelines for contributing.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the
  conan-center hook activated.

Recipy based on https://github.com/bincrafters/conan-imgui
Tested on a Ubuntu 18.04. Also tested modifying conan-examples/libs/dear-imgui (had to change the imports from misc to res)

[conan-center-bot]

All green! 😊

• imgui/1.74: Generated 130 packages. All logs here

[uilianries]

LGTM

The CMake file is better than that one in VCPKG: https://github.com/microsoft/vcpkg/blob/master/ports/imgui/CMakeLists.txt

[conan-center-bot]

All green in build 2 (1a8557debac7dfe9b4c26b640a6780ce215cdacd)! 😊

• imgui/1.74: Generated 130 packages. All logs here

[conan-center-bot]

All green in build 3 (5704f1d0bab3130399180782af13214d1bd8ac37)! 😊

• imgui/1.74: Generated 130 packages. All logs here

[danimtb]

I would like to clarify the usage of the CMakeLists.txt file, it it needed to build the bindings?

[conan-center-bot]

All green in build 5 (688d04de4b4f2a8af6bd376ee56064988b7dd30b)! 😊

• imgui/1.74: Generated 130 packages. All logs here

[Hopobcn]

I would like to clarify the usage of the CMakeLists.txt file, it it needed to build the bindings?

imgui does not provide any associated build script. It delegates the task of compiling the library to their users.
From the readme:

The core of Dear ImGui is self-contained within a few platform-agnostic files which you can easily compile in your application/engine. They are all the files in the root folder of the repository (imgui.cpp, imgui.h, imgui_demo.cpp, imgui_draw.cpp etc.).

No specific build process is required. You can add the .cpp files to your existing project.

You will need a backend to integrate Dear ImGui in your app. The backend passes mouse/keyboard/gamepad inputs and variety of settings to Dear ImGui, and is in charge of rendering the resulting vertices.

So the CMakeLists.txt is necessary to compile the cpp files (imgui.cpp, imgui_demo.cpp, imgui_draw.cpp & imgui_widgets.cpp) into a imgui library.

Then the platform backends are provided to the user inside the res/bindings folder. It's the consumer responsibility to cherry-pick which platform binding to use (via imports):

[imports]
./res/bindings, imgui_impl_glfw.cpp -> ../bindings
./res/bindings, imgui_impl_opengl3.cpp -> ../bindings
./res/bindings, imgui_impl_glfw.h -> ../bindings
./res/bindings, imgui_impl_opengl3.h -> ../bindings

I don't know if this is up to conan-center-index standards but at least this is how it is done in the bincrafters recipy.

[uilianries]

The cmakefile loooks compatible with other package managers