Pyxform prepends jr://image, jr:video, jr:audio to any value in these columns, which is great for simple filenames and complies with the XForms spec.
When a user enters https://example.com/myimage.jpg in the image column, this gets turned into jr://image/https://example.com/myimage.jpg.
This is unsupported usage and the result is unhelpful. What would be helpful is to either:
detect the https?:// scheme and if present, do not prepend a jr://(image|video|audio) scheme.
output an error
Strictly speaking the second option is best in terms of ODK XForms spec adherence. However, I wanted to check if anybody has objections to a PR that implements the 1st option instead. Some custom clients that use XLSForm (online-only without resource-caching) would be helped by this.
I dont see whats wrong with option 1 and can see how it would be much more beneficial. SHould we ammend the spec? Or should I just dive in and take this?
Pyxform prepends
jr://image
,jr:video
,jr:audio
to any value in these columns, which is great for simple filenames and complies with the XForms spec.When a user enters
https://example.com/myimage.jpg
in the image column, this gets turned intojr://image/https://example.com/myimage.jpg
.This is unsupported usage and the result is unhelpful. What would be helpful is to either:
https?://
scheme and if present, do not prepend ajr://(image|video|audio)
scheme.Strictly speaking the second option is best in terms of ODK XForms spec adherence. However, I wanted to check if anybody has objections to a PR that implements the 1st option instead. Some custom clients that use XLSForm (online-only without resource-caching) would be helped by this.