Ned: ImGui Text Editor with GL Shaders
github.com
github.com
I think many developers/programmers have already picked their poison - what advantages would switching to Ned have? Would newcommers try it.. or resort to VSCode, NeoVim, etc.
Not suggesting it's wrong or a waste of time. Certainly not! I am always happy to see various alternatives out there in various sections of computing... even the likes of GNU Hurd still keeping itself going!
There has been projects where I've been very tempted to use IMGUI as it is an easy/quick approach than building a website or commonly known GUI managers. (WPF, Qt, Gtk, etc)
The problem is - these projects are not about creating text editors, but some GUI Windows (or Windows) that solves problems with check boxes, buttons, and text areas. The problem is ALWAYS when the customers says "Ooh.. it would be good if we can do this!" which, for example, is supporting a Map.. like Gmaps.. which can be supported on the web or on traditional UIs easily.
Do I have the time to support a new feature? Unfortunately.. I dont! I end up using the tools or libraries that DO have these features available. In this example, I can just put together a website using Leafletjs.
Long story short.. as much as I would love to use an Immediate Mode UI to solve a problem... it sounds like a great idea... until it isn't.
Although you could certainly use it as a desktop editor if you wanted to, I think the real value is in embedding.
Just nice to see other possibilities.
Everyone seems to want 9234567345863489634589 fps, when that's IMO completely absurd for a normal desktop app, e.g. editor! What you actually want is low latency, not constant massive bandwidth and power usage. If all your normal desktop apps constantly ran at uncapped FPS, your computer would scream and laptops wouldn't last 5 minutes on battery.
The whole point of >60FPS would be to able to reduce the delay between the user action and the results appearing on the screen.
The irony is just like with manufacturing and CPUs, the secret to getting high throughput necessary for high FPS is deep pipelining - meaning more delays compared to just drawing stuff.
The parallel of this in games has been frame generation, and fake frames - the way this is implemented that the game waits an extra frame's worth of time, then starts generating an interpolated frame between the two states, which adds extra time as well.
I propose, that instead of FPS, gaming benchmarks should move to the metric of action-to-pixel (ATP). For this metric, the FPS(or frame time) is a lower bound - if your game runs at 60FPS, your frames take 16.66ms to render - so by definition you can't react any faster than that.
Not sure if anyone's working on this, but this would be a nice way to combat the framegen BS that's going on in the games industry right now.
I will be so extremely happy when this lands, and imgui is already such a blessing.
> What you actually want is low latency
High frame rates directly contribute to lowering latency.
I guess I'm the polar opposite of you here, I heavily prefer low latency/high refresh rates over low CPU/GPU usage, as long as the machine is plugged in to a power source.
Nobody is saying they want to tolerate some horribly laggy interface for the sake of lower CPU usage. The point is simply about not wasting enormous amounts of power when it's not needed.
I don't know what to tell you when you're fucking with an immediate mode UI library...
Then how is it that many people, myself included, are able to hack fix this to only update when required? Why does the imgui dev himself promise official support for this?
(edit: This isn't snark, I can't see changes that fast, but I know what they look like slowed down and that other people may be different to me.)
As did any CRTs running below 75hz
My “super power” used to be that I could tell what refresh rate a VDU was operating at just by looking at it. Well, I couldn’t tell past 80hz. But anything below that I could.
God bless LEDs with some capacitance though...
So many "hackers" apparently did not hear about adaptive refresh. There is no need to update a static image every 240fps. You only need to increase the refresh rate for animations like scrolling, like in... everywhere??? Android, macOS, Chromium, Qt, and GTK(?) do this.
I’m going to tinker with this.
I do appreciate they have the option to disable the big sign-in button however there are other account related UI I still can't disable.
The main feature that keeps me from moving to any other editor is the vscode/vscodium feature of clicking and dragging files to insert links and embed images in markdown files. Weird that no other editor has this.
This works really well until your transparent terminal is overlapping some other text, or worse, another transparent terminal!
Beautiful as it was, I eventually stopped setting this up.