lumbeezl wrote: Wed Apr 19, 2023 8:05 am
Qt would be the best framework for C++, no question. Of all the native applications frameworks I've used, Qt takes the pie. LGPL allows dynamic linking so licensing is no issue at all.
As far as a prototype is concerned, please check your private messages for my email. Best if we begin communication that way. I'd love to begin work on this. Just let me know.
Thanks
One of the major issues to be concerned about when programming a GUI is whether frequent updates to the library are going to frequently outmode your app on new versions of your Linux distribution.
I don't know about in C++, but in Python, I would recommend Tkinter (compare to TCL/TK) over Qt and Gtk for this reason (since Tkinter is more integrated with Python). I used to use WxPython (compare to WxWidgets) with Python, and Gtk with Vala (a programming language that compiles C#-like code to C), until I got tired of my code not working after a small number of years (and me not being invested enough in it to learn the changes required to update it, if updates were even possible without reworking the app). I think I've been using Tkinter for over a decade with few to no issues at all in a Linux desktop IDE app I use regularly (for programming, writing, reading, and such). Anyway, I might recommend looking into using TCL/TK in C++, if you're going the C++ route, and compare it to Qt as to how reliable it is long-term.
Someone who uses C++ more would probably be more familiar with how much of an issue which libraries would be in this regard. I'm not really sure how often this is an issue with Qt. If you've used it for at least five years and you update your Linux distribution regularly, you probably already have a decent idea. I haven't explored Qt much (not even on Python). However, I think you would find the
TCL/TK license nice for the purpose at hand.
Also, I strongly encourage not putting the focus primarily on how nice the interface looks (other than readability). Put the focus on content, features, and usability, because that's what matters (that's why people use the app). Even a command-line Gospel Library app would be just fine as far as I'm concerned (actually, I'd probably use that more than a GUI-based version, to be frank). Probably the major issue there would be making a good file pager that does word wrap, and supplying the data in a way that wouldn't easily allow people to repurpose it for unauthorized stuff. The main advantage of GUIs (other than it being more mouse-friendly and widget-friendly) is that the fonts render better on them than on the command-line. Plus, you can use more keyboard shortcuts and stuff in a GUI. Command-line apps are definitely more cross-platform, though, and they don't tend to get outmoded except on rare occasions. They're also faster and take fewer resources.
Plus, on the command-line, you wouldn't have to load the whole app just to use part of it. You could just do a command to open the specific thing you want to read, or whatever, and get it right away. You wouldn't want to try to immitate the GUI-based Gospel Libraries there in the way they look and function (but in the content they provides you with, yes).