ImFrame VS tracy

If you need a quick way to start a C++ ImGui app, you can use my ImFrame library. It's essentially a C++ application wrapper around glfw + ImGUI, along with a few handy additions that applications might need, like native file and folder dialogs, automatic windows settings / persistence, etc.

If you want a demo, you can use my starter framework to see if it would work for you, or check out Implot's repository directly.

If you want a Dear Imgui "starter kit", you can try ImFrame. It packages a few libraries into a very lightweight cross-platform application framework.

If you just want an empty app in which you can play with ImGui, you can use a lightweight framework like ImFrame.

To help with this, I made a framework that makes it much easier to use like a more traditional application framework, providing a few handy features you'd expect, like native file dialogs, window position save/restore, native macOS windows, platform-appropriate settings storage, image loading, a selection of fonts, etc.

Probably the fastest way to do that is to use something like my ImFrame library, which is designed to get Dear ImGui and ImPlot up and running inside an app with minimal fuss and bother. You'll need to use CMake to build the project, but it's pretty simple, as there are batch files to build in the /Bin folder for Windows, Mac, or Linux.

Dear ImGUI - Unlike the others, is designed for applications with a real-time rendering loop, such as games. Was originally designed for creating debugging UIs, although has expanded far beyond this, and is now used for full-featured applications. Requires an existing back-end to plug into. If you need an application framework for Dear ImGUI, you can use my own project ImFrame, or something similar.

I use CMake as my (meta) build system, and generate VS projects on Windows, Xcode projects on Mac, and Code::Blocks projects/makefiles on Linux. Example of one such project of mine: https://github.com/JamesBoer/ImFrame

I'm currently writing a Dear Imgui framework called ImFrame. It handles the work of creating an application loop with an appropriate renderer, using GLFW and other open source libraries, and then exposing the Dear Imgui API for your use to do what you want with it.

For example, in one of my libraries (you can see the whole thing here), I'm including the single-header library stb_image.h as a separate project, so it shows up with all the other external libraries. It's not necessary for compilation, but is just there to assist with browsing / seeing all the external libraries.

i don't really think there is _anything_ that comes even close to tracy https://github.com/wolfpld/tracy.

on top of this, given google's penchant for dumping projects aka abandonware, this would be an easy pass.

The RemedyBG debugger (https://remedybg.handmade.network/) and the Tracy profiler (https://github.com/wolfpld/tracy) both use Dear ImGui and so far I've only read high praise from people who used those tools compared to the 'established' alternatives.

For tools like this, programmers are also just "normal users", and from the developer side, I'm sure they evaluated various alternatives with all their pros and cons before settling for Dear ImGui.

Not the person you asked, but generally you might want to look at "frame-based" profilers. These are typically used in video games, but the concept is general, and can apply to other applications. The "frame" could also be something like a request or transaction being processed. I like Tracy[1], myself.

Another latency metric that you'll see, often w/respect to web apps and microservices is "P99" and similar. This is the amount of time in which 99% of requests get their response. For a higher percentile, you get a better idea of worst-case performance.

[1] https://github.com/wolfpld/tracy

I've not actually used Superluminal, but I use Tracy for similar reasons. It's free though (and, importantly, open source).

For profiling, you can check tracy.

You could try Tracy

There is no such thing as overengineering in fun projects, so I've also adopted Tracy as profiling solution. Works quite nice and gonna save me plenty of times in the future debugging performance spikes on badly optimized math heavy operations.

I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.