Does not support tabs definitions AFAICT Chords not being specified inline leads to positioning issues without mono-spaced fonts, and leads to positioning only being correct in one language. Good separation of concerns of definition of songs/sets vs visual/presentation of said sets. Has a sensible song progression describing what portions of the song are planned in what sequence. Set format can support other needs of a worship service, such as video, pictures, bible verses, slides, and so on. Customizeable, immediately-searchable XML song format If either format will ultimately become the native format remains to be seen, but we will start with OpenSong, to get the other features out there. There is a plan being fleshed out to support chordii/chordpro format as well or even switch to it altogether. FormattingĬurrently this application supports only the OpenSong format. Other languages and locales should be intentionally supported, so that we can help the persecuted church for example. Some features of the original web app, particularly the RTF format export, do not support Unicode.
#Opensong reinstall full#
Full service presentation (sermon/multimedia/bg/etc) Unicode and regional support Conversion/Cooperation with ChordPro format?ġ4. Will vet needs with worship leaders and adjust the below plan. Shared, mobile scenarios - self-guided or presenter-guided Build a worship set - order, capo, transpose, and annotate a set list.
Track song use, popularity, tagging, etc.
On boot the app will process the inbound folder and drop the results in the other two folders based on success or failure. To see this thing work with actual data, or to add songs to the database in bulk, you can extract DataImport.zip (in the root of the project) to the folder specified in the app config file. This will become a pre-packaged container at some point.
0 kommentar(er)
