useful form data
nav_first.pngFirst: thread:379
Feedback from naive user
Edited: 26 Oct 2011 12:41 by: Sheepdog
Comments: 3
nav_prev.pngPrevious: thread:290
Data form 'required' property UI design
Edited: 18 Mar 2010 09:05 by: leiger
Comments: 3
Last: thread:141
Which aspects of this design do people want first?
Edited: 11 Nov 2009 12:44 by: leiger
Comments: 14
Next: thread:328
wiki fields should support the same features as a page that doesn't use data forms
Edited: 11 Mar 2010 01:55 by: leiger
Comments: 0

scottplanscottplan wrote on 16 Mar 2010 12:25

I've posted this elsewhere, but I'm thinking the question deserves its own subthread.

I've tested forms pretty thoroughly, with the hope that I can get to my holy grail: a form that takes what users give it, but reverts to a semi-sophisticated default when they don't. I've mapped it all out, with examples, and I'm just not there yet — the green cells are successes, the red ones are obstacles.

  • For one thing, I can't do much with the data I collect via %%form_data{field}%%. I can't turn it into a link, pass it as a _template parameter, or plug it into a tricky include. Is this because form fields (symbols?) are compiled later?
  • Default values are kludgy. Assuming form fields are eventually living, useful pieces of data, I'd like the resulting page to adapt when certain data is missing. For instance, if a user doesn't provide an email, let's show their username instead. If a user doesn't point to an offsite image, let's look for one attached to the page instead. I'd prefer not to show to the user any @@ (from a tricky include), or :first (even if I did, they don't work anyway). Instead the _template should be able to respond to the data and revert to the right code. Can't do that yet.
  • I think I could get there if includes recognized the data passed to them via forms. I could pass a null value, then ignore it and assign a default value instead.

I'm open to suggestion for how to work with the existing compile sequence. But if there's no way to get there, I'd surely appreciate a way to make form data more useful.

So I'm wondering. James wanted forms to be accessible via CSIs. I want form data to be available for includes. Is it possible to have it both ways?

Start a new sub-thread

Comments: 24

Add a New Comment
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License