openlp-core team mailing list archive
-
openlp-core team
-
Mailing list archive
-
Message #24387
Re: [Merge] lp:~mbernis/openlp/trunk_remote_app_enhancement into lp:openlp
I don't have many time to work on this project, and I develop remote features that really help our technical team of church.
I see 4 steps on how to split my work :
- First, change on existing core development
- Next, signals connect and new remote entry point in core
- Third, server side remote plugins changes
- And finaly, remote app it-self.
But, as I say, I don't have time to do this today, because I still have some feature to add on this remote app :
- I add a cloud server on the church computer to easyly put files on server. Files are PPT, ODP, AVI, JPG, ... all medias files that support OpenLP. So I don't add in the remote app a upload function (I think that a cloud service doing it more powerful that me), but I add a scan function. This one scan the cloud folder and update medias library with new files.
- Now, I must add the edit song / custom diapos function remotly : we must adjust our imported OpenSong song. To do that, I will connect the 'edit all' function to put all text in a html textarea.
Later, if I can spend more time on this, and if the worship team judge that this will nice, I try to add chords in song. Chords will not be display on live, but will use by a remote page ...
--
https://code.launchpad.net/~mbernis/openlp/trunk_remote_app_enhancement/+merge/233617
Your team OpenLP Core is subscribed to branch lp:openlp.
References