04-01-2016, 03:20 AM
This is a very interesting idea. I don't think it would be too difficult to implement the rendering of the image (although I may have questions about all of the supported values/ranges for each proposed parameter), but I'm definitely not thrilled about needing to back up the files linked through that command. Those files wouldn't exist in the library anywhere, so it would require that in order for me to back up any chord pro file, I would first have to parse out any image commands used inside of it, figure out where the files are that are pointed to by that command (and I typically only support local files, and a uri would suggest that I should also support other targets such as a web address), and write those files into the backup file (which messes up the way backup files are currently processed). If the uri points to a valid path on one tablet, but not another, then I have to think about either just not restoring the file, or assigning a different path to it and having to dynamically modify the chord pro file to point to a valid path. All of these things can probably be handled, but I would only want to do it if it provides a very useful capability that a lot of users would benefit from. Just supporting the command itself isn't a big deal though - it's just the backup/restore that concerns me.
Mike
Mike