Improve zsync-curl integration about appimageupdate HOT 3 CLOSED

The rewrite features an FLTK based GUI, and is written entirely in C++, i.e., does not have a dependency on any CLI tools.

Regarding the UI framework, we might implement a GUI in Qt and/or Gtk eventually. The original issue is solved however.

About the url: feature: this should be discussed in https://github.com/AppImage/AppImages.

from appimageupdate.

I think to solve this properly, we have to directly use some kind of zsync_curl API instead of relying on the bash script.

Yes, the whole functionality of the bash script could be either rolled into zsync_curl itself, or into a small C binary that would tap into a library-ivied version of the zsync_curl codebase.

My approach would be to write an AppImageUpdate C(++) framework based on the zsync-curl source that has two or more frontends, a CLI and a GUI application.

While at the GUIs, I'd suggest to do a C/Gtk+ one and/or a C++/Qt one. I just had picked Vala because it offered a quick way to get a proof-of-concept GUI around the bash script.

from appimageupdate.

Actually, I have to admit that I like Vala, and it's sad that it isn't any more popular. I don't have much experience with Qt. Anyway, Vala uses GTK, and translates to a native application, too, which is a plus. Also, I guess including Qt in the resulting AppImage will consume more space than Gtk.

Since it is ABI compatible with any C/C++ program, it'll work with my plans to write a proper framework in C or (preferrably) C++ and integrate that in a GUI application.

from appimageupdate.