Mar 11th, 2010, 9:03 PM
Hi Mike,
Yes, you're making perfect sense!
#2 is surprising. I thought I fixed that a while back. You are running 2.0.0 final (non-Beta), correct? Also, what theme are you using for the client account?
#1 I understand better now, thanks. It's an interesting problem. I guess the question is: how should it behave? Since the "Add" button can appear on any View, perhaps the most intuitive solution would be to have it create a new, blank submission PLUS whatever criteria was specified for that current View. For example, if the View limited results to "Pending" then when the user clicks "Add" it would create that blank View, but also set it to "Pending". Or, whatever other criteria was specified by that View.
That way, the process would be seamless from a UI perspective. They wouldn't create it then have it disappear on them because it just didn't apply to.
My only concern is that people will lose their way. e.g. they could pick a View, forget about it, then start adding records, unaware that all the records they're creating are being given default values for whatever the field or fields are that are limiting the results in that View.
Hmm... complicated stuff. What do you think?
- Ben
Yes, you're making perfect sense!
#2 is surprising. I thought I fixed that a while back. You are running 2.0.0 final (non-Beta), correct? Also, what theme are you using for the client account?
#1 I understand better now, thanks. It's an interesting problem. I guess the question is: how should it behave? Since the "Add" button can appear on any View, perhaps the most intuitive solution would be to have it create a new, blank submission PLUS whatever criteria was specified for that current View. For example, if the View limited results to "Pending" then when the user clicks "Add" it would create that blank View, but also set it to "Pending". Or, whatever other criteria was specified by that View.
That way, the process would be seamless from a UI perspective. They wouldn't create it then have it disappear on them because it just didn't apply to.
My only concern is that people will lose their way. e.g. they could pick a View, forget about it, then start adding records, unaware that all the records they're creating are being given default values for whatever the field or fields are that are limiting the results in that View.
Hmm... complicated stuff. What do you think?
- Ben