No issue this time just issuing my final thoughts.
I certainly wrote a lot and I hope to get people’s attention and see what they think.
My aim in this series of posts is to have a discussion about the proposed issues and understand what people want. Because if just do it my way all that may be alien to everyone.
What I would hope to see is maybe more people get involved propose ideas and say what their needs are and how we can make this tool better.
And also I want to know what the future of Quelea in the next year or two will look like.
If I am going to spend the time to work on this module I want to do it for a tool that will do what I want and serve me faithfully. Naturally, for that to happen I need the other issues in Quelea to be fixed also.
Just think about the possibility of being able to play versus in Quelea, change slides or presentations/ videos, and change themes and backgrounds all in a sequential manner.
Run preprogrammed alerts etc. all from your DAW synced data.
Consistency every time and share it with all Quelea users that use the same DAW or even just a MIDI/OSC player.
Reaper is very flexible and includes a programming language, at 4 in fact including python ( for everyone), C/C++ for real-deal performance, ELL for low-level prototyping and LUA for scripting.
Use any of those to program your presentation along with your music.
Just put a marker to call an action or MIDI note to trigger something across your whole performance.
This should make you think about Quelea in a very different way.
And you can’t just get all that for free from someone who has already done the work. Maybe make a change and share it with others.
I will propose the same module in OpenLP as well (probably). The idea is very much the same and it should be able to integrate just the same. I hope the users of both can benefit from those features and I really hope to see support from the community here.
Honestly, whatever happens, I am just fine to do that on my own fork of the project.
But as I said in the beginning this is my set of features that I think will take quelea away from what I perceive as stagnation and make it a more complete toolset with the possibility of multiple new workflows that address the needs of a broader user base.
I just want to say, before the developers-maintainers say “something like this is hard to maintain”, I believe we can implement a lot more experimental features.
All it takes is a single bean entry in the configuration files and let the users decide for themselves whether they want to try them on or not.
Remember, Google has a single monolith repository with billions of files and lines of code. So surely we can include a few more experimental features disabled by default just to be safe.
Also, I am certainly going to my share and contribute.
Everything that was written was from the perspective regular (power-power) user because I am always trying to get the most out of the tool I am using and now I want to make it not better but greater!
Not to forget, lots of love and thanks to all the developers, maintainers and contributors for all the work you guys have put in.
Immensely appreciate your work.