-
Notifications
You must be signed in to change notification settings - Fork 82
you should be able to save forms as different names than their explicit "form name" in Build #56
Comments
Comment by mitchellsundt Reported by
|
An interesting request, but I don't like the suggested solution. We don't yet have a filesystem-like concept where files have names but maybe contain titles as well, and I'd rather not go that way. Any other suggestions? |
Not quite true. There is a <title> element in the generated XForm, settable via form_title value on the settings sheet in XLS. The XLS filename maps into the name of the top-level node of the submitted instance (and therefore can't have spaces or special characters), and there is the form_id value on the settings sheet for the id="" attribute of that top-level node. And I see that the version value on the settings sheet is still not documented on XLSForm.org. On the device, the filename of the XML file is largely irrelevant and ignored. This is all a bit of a mess because the <title> field cannot be internationalized like all the rest of the text. But it is that field that is displayed to the user in selection lists, etc, not the filename. |
@mitchellsundt thanks for the explanation! This might be cause, then, to revive the "Form Properties" dialog I killed off for lack of usage. The title at the top of Build and the name in the Save/Open dialogs would remain as they are now, but an additional option would exist in Form Properties for "title on phone." Does that sound reasonable? If so we can slate this for next release. |
…ild. * the setting is found in the restored Form Properties dialog, under the Edit menu. * the main form title is used if no title-on-phone is given. * this commit is ugly as hell and full of hacks. but it’s the best i can do with this codebase. * resolves getodk#56.
export/new #56: allow title-on-phone to differ from title-in-Build.
Issue by mitchellsundt
Thursday Jul 09, 2015 at 17:34 GMT
Originally opened as getodk/getodk#166 (1 comment(s))
Originally reported on Google Code with ID 165
Reported by
carlhartung
on 2011-01-12 23:08:58The text was updated successfully, but these errors were encountered: