meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Apr 8 at 17:15 | |
| stats | profile views | 4 |
|
Mar 7 |
comment |
Placement of delete button on form Thank you very much for the valuable insights. You raised a good point concerning the save buttons and I have changed the color to make sure it is the most visible, and de-emphasized the delete action by making it a link. The the MailChimp example is especially valuable in a related case where the user was able to cascade-delete a potentially large number of records and found this speedbump to be quite effective in preventing accidential deletions. |
|
Mar 7 |
comment |
Placement of delete button on form Thanks for the insights. You are in fact deleting the entire record you are editing. While it is rare to be editing the actual data after it has been saved, I cannot substantiate what percentage opens the edit form to actually edit or delete. |
|
Dec 15 |
comment |
Alternatives to failing a form to ask for additional input Thanks for the fast response! After having given it some more though, I have decided to proceed down this road. |
|
Apr 23 |
comment |
Getting input for a one-to-many relationship Thanks! I suppose that is a better idea than trying to cram a complex form in the tab. |
|
Jan 31 |
comment |
What pattern to apply to a sizable flight logging form Thanks for such a swift response and detailed answer. You are right, I was trying to get the form completely right the first go, what I should do is iterate, starting off simple and go from there. Great advice on the form's design as well, thanks! |
|
Jan 31 |
comment |
What pattern to apply to a sizable flight logging form I prototyped the single page form but it looked messy, which is why I was looking for alternatives. |
