Quelea is relatively mature and it’s fair not to expect many new additions, but sometimes we … I need more. I argued my point for a while, however, development seems to be focused on bug-fixing (fair enough!) and the rest is snail passed or in a state of undefined no-progress.
Really, it’s just things I want to see there and while I won’t brake stuff I won’t guarantee something might not break. Though in fairness I put enough safeguard even if the feature fails it won’t crash the app.
What’s new so far:
A MIDI module , it works great!
Status: pretty much done, but might need to edit the text properties instead of from the UI. UI is good for reading them. (there is an external python app I was using initially for configuration testing as well )
Removed the annoying compulsory password. Now it can be empty! The app just connects outright. Fantastic!
Some bugfixes, typos, and Gradle update to make it compile.
mDNS, proxy test internal and as external python app. This is great for consistent and friendly URL like http://remote:1112. Every time regardless of network the same simple URL.
Status: At least that’s the idea. The internal mDNS didn’t work for me but the external python app did. Maybe I am doing something wrong.
Anyone wants to give it a shot at debugging it?
Much Improved (still working on it) control server and frontend.
The server was done in a bit bad way, meaning it was ok but lacking flexibility. Now you just drop a file like so
And just do any frontend changes very easy, just like a normal web server. It can also now serve arbitrary content such as icons, images, videos etc. if needed.
We don’t even need a mobile app anymore. But this is still work in progress
Improved and adjustable response and other configurations for the frontend which will be persistent for that specific device.
Status: still work in progress
Fantastic quick search addition panel and some icons.
The old one is alright for some multi translation options but not useful for quick action.
This one is very very quick and has key bindings allowing to find, add and show a verse while speaking in real time.
Disabling preview mode is super useful for a single person control. Maybe in rehearsal situations or when the schedule is ready and all that is needed is direct activation.
Thinking of adding an option for “contains” and “begins with” for the tokenized search. But I think I will most likely will just default to “begins with” for each token, i.e. substring separated by white space. I think this will be a better blend of efficiency, accuracy and flexibility.
This is really seriously fast with the go live selectors. Even with a “chapter add + going live” it selects the preselected verse in green and moves the focus to the live (or preview) panel.
On your github Quelea fork I can’t find any release installer assets yet. So it is not usable for an end-user. Perhaps it’s time now to take the final step and release this fork as an independant new “QueleaJP” and see what happens in time. In the past we saw similar movements with other apps. For example KeePassXC (cross-platform) besides KeepPass and more recent DOSBox-X (more flexible and provides more features) besides DOSBox.
You right! I have been thinking about it actually and at the moment there are 2-3 caveats but if people are alright with the following then have made a release:
Maybe it will be a good idea to make a backup of your .quelea (config directory) or just the quelea.properties file inside it. Some new keys or temporary keys maybe added for the new features and your configurations might be altered slightly.
The installer would be production ready, but some new features might be a little buggy.
The development is mostly things I want or need but I am open to ideas of course.
I want to test features, hance the versioning might be ignored, meaning it will stay the same for different builds. You probably don’t care about that so just look at the release date.
At the moment I can’t compile for mac specifically. It has to do with the compiler trying to setup some system paths the MAC way, supposedly. If someone can fix the manifest or reproduce the error … Packing on MAC from source . So far I don’t have or plan to have a mac but been thinking of setting up mac dev VM. Maybe if someone can share a link with a good mac image that could be useful.
For those who can maybe you can use the JAR crosspaltform installer.
Another post from a few days ago got me thinking about having multiple translations at the same time. As I was explaining the idea, I realized that I would benefit from something like this. Naturally it would be nice to have a feature … but we can do it quick and dirty like so.
What is happening here is the merger of 2 bibles at verse level with something “<–>” for visual separation.
I made a small script (with example; which works as a command line tool), which can be downloaded and used by anybody (with python3). Give your 1 or more bible files and out you have a merged version. The first input is also passes the merged attributes such as book names and other attributes.
It autodetects various tag formats, which is pretty nice.
It is available on the repository at top level with a readme.md in the bibleMerge directory.
NICE TO KNOW NOTE: this simply creates a new bible file which can be imported anywhere the inputs where used. i.e. regular Quelea or other software that works with the said format.
Preliminary version of for shortcut key mapper. I am not sure if this is actually that useful. So far after adding some window specific key bindings for the search functionality I though it would be useful to have at least a read-only where we can see a list of the mappings. In that case it might be better to place this in the “about” section.
Open to suggestions.
