grocy-desktop VS CefSharp

Double post of grocy/grocy-desktop#42.

Latest grocy-desktop (desktop application wrapper) release: https://github.com/grocy/grocy-desktop/releases/tag/v2.2.0

Guessing you're referring to grocy-desktop.

(Screenshots and specific error information can be found in my initial bug report on Github, if that's helpful. Imgur won't let me sign up for some reason, I'm sorry for the inconvenience.)

Can only say something about grocy-desktop:

About grocy-desktop: It's basically just a web server and a web browser, so works with any version of grocy (of course there could be for example missing PHP extensions or something at some point in time). So far, grocy-desktop was always updated at the same day for any new major or minor grocy release, when I look at the release history. grocy can also be updated independently (all that is also mentioned in the projects README).

Already mentioned here or there or on many other places when you search for it, CefSharp is pretty widely used in many applications...

Here is link number 1 - Previous text "#33"

That's true, sorry - I forgot that grocy-desktop auto manages the needed config.php settings and therefore overwrites the file on start (happens here).

The Fullscreen Chromium (cefsharp) based Web-Browser ignores optionally user input like Mouse clicks, and is optionally always in the foreground (Force-Top-Most), so it can be used for any situation.

Just as a background: I'm working on a façade for the CefSharp utility. This utility requires the programmer to initialize and terminate it in the same thread, once-per-process. My current implementation uses a lazy initialization algorithm requiring inter-thread communication. But the possibility of AppDomains arising or passing away complicates the algorithm by requiring threads to potentially signal one another across AppDomain boundaries. It would be easier to just let the threads communicate without worrying about which AppDomain they belonged to.

I dont want to state the obvious but of course there is CefSharp .. But of course thats pretty heavy duty as you end shipping a headless version of Chrome in your app, but it can do anything a browser can do (of course it can, its Chrome), including exectuting a JavaScript string on the fly and getting a response. Because its Chrome you evenn have access the the dev tool and everything like that. But the other suggestions might be better suited as they might be more lightweight.

Two options: Either use an embedded browser you can control programmatically like CefSharp (https://cefsharp.github.io/) or spawn a real browser and use sendkeys() to control the browser by emulating user input.

Chrome Runtime discussion in CefSharp repository.

https://github.com/cefsharp/CefSharp/ if i spiked your intrigue

CefSharp

I always use https://cefsharp.github.io/