GTK+ VS electron-builder

Clone https://gitlab.gnome.org/GNOME/gtk

This is the GTK file chooser, not to be confused with the gnome file browser (nautilus). The repo is there. The issue for this particular bug is there. My merge request is there.

GTK and Gnome are almost 25 years old, and they're nowhere as messy as the Windows

https://gitlab.gnome.org/GNOME/gtk

I'm trying to port a small GTK3 project over to GTK4 and I'm stuck for a week or so at wrapping my head around menu bars. In GTK3 I used `GtkMenuBar` which is replaced by `GtkPopoverMenuBar` as far as I understand, but I don't understand how. All examples I've found for GMenuModel implemented that hamburger symbol which I don't like (example given).

git clone gtk repo, git checkout the gtk-3-24 branch.

GNOME does maintain GTK. It is the core of their development platform. Its code is even hosted on GNOME's Gitlab

in '~/.config/gtk-3.0/gtk.css' file. Please note this may break some apps somehow. Also, this is not solution, it's only a workaround. It's better to communicate with GTK developers here: https://gitlab.gnome.org/GNOME/gtk

Yeah, that's the Gtk file dialog. Please file a bug report at https://gitlab.gnome.org/GNOME/gtk.

I'm trying to make a text editor in gtk (yes I know there are already plenty of those, but it is a project to learn, not for actual use), and I got pretty far already I would think. I'm basically following the GTK docs for GTK4 and cross checking them with the examples from the GTK git. However I am stuck on something. The current most state of my program is broken, as I get this error when trying to start the program:

The last step for each platform's build process is to upload the app to our GitHub releases repository. We automated this step from the beginning, but when we started creating builds for the new M1 chip Macs, we had to add a manual step. This involved merging files needed for the auto-updater to work with the M1 builds.

https://github.com/electron-userland/electron-builder/issues... that issue kinks to the PR that adds the automation.

It's a non-trivial thing to test, since it involves so many secrets and the notarization step can take over an hour, so I don't expect anyone here to actually want to look into it.

My original comment really was just venting my frustration, not a cry for help (but I might be crying soon if I can get to the bottom of this!).

> The ‘autoupdater’ does three things,

>

> - check the app for updates (using Sparkle)

> - report any crashes (using Sentry)

> - start a local HTTP proxy on port 40701 (this can be changed using the configuration json file in the app bundle).

>

> The latter is of course, not to be expected of any app on the machine, especially not one that just claims to be an auto updater.

Well, yes. And no.

For example, electron-builder [^0], a popular framework used for Electron app packaging and auto-updates, uses a local update server on Mac [^1] to add a more sane system backed by a more insane system, Squirrel.

[^0]: https://github.com/electron-userland/electron-builder

[^1]: https://github.com/electron-userland/electron-builder/blob/m...

The Project uses Electorn-Builder to package the app and Electorn-Updater to update.

You can read about this issue here: https://github.com/electron-userland/electron-builder/issues/7114

Ostara is based off of electron-react-boilerplate and uses electron-builder to package the application.

Install electron and electron-builder

I believe Visual Studio Code uses Electron and posts releases on a regular basis. Maybe check their A quick Google search for "electron build github release" turns up "Electron Builder" https://www.electron.build/ I don't really know though; I've never used Electron.

I also would like to have an NSIS installer so if it happens to package the Chromium executable along with my app, how can I accomplish that? I am using electron-builder.

We use electron-builder at work.