就地编辑与单独编辑页面/模式？
我有一些数据被分成几个部分，很像 StackOverflow Careers 的简历功能（尽管它不是简历数据），可以通过 jQuery Web 应用程序进行编辑/创建。它有点层次化（工作可以有子工作等），所以根据我采用的 CRUD 方法，这意味着不同的工作量。我不介意花时间把事情做好，但我不想花很多时间做一些花哨的东西，但这并不是最佳的用户体验。
是否对“编辑”这种分段的分层文本数据的不同风格进行过研究：
就地编辑（例如，单击表单元素（例如职位名称），它变为可编辑，然后单击“确定”并保存）
编辑按钮，将您带到新屏幕（如当前的 StackOverflow）
弹出模态表单的编辑按钮
所有字段都是开放且可编辑的，单个保存按钮（如 StackOverflow Careers）
对于何时应使用这些不同的表单来提供最好的用户体验？
I have some data that is broken up into sections, much like the Resume feature of StackOverflow Careers (it's not resume data, though), that is editable/create-able via a jQuery web app. It's a bit more hierarchical (jobs can have sub-jobs, etc.) so depending on what method of CRUD I take, it means differing amounts of work. I don't mind spending the time to do it right, but I don't want to spend a lot of time making something fancy that isn't an optimal user experience.
Has there been any research done into the different styles of "editing" this kind of segmented, hierarchical text data:
Edit in place (e.g. you click on a form element such as job title, it turns editable, then you click "ok" and it saves)
Edit button that takes you to a new screen (like StackOverflow currently)
Edit button that pops up a modal form
All fields are open and editable, single save button (like StackOverflow Careers)
Is there general consensus on when those different forms should be used to provide the best user experience?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这取决于。如果您的用户群精通网络，我会建议使用就地编辑方法，因为它提供了自然的编辑流程。
就地编辑
当您编辑层次结构的一部分时，您将与其余信息进行内联编辑。这使您可以在编辑时检查您的编辑如何应用于其他信息（而不必在屏幕之间来回移动）。
就可用性而言，一次性编辑分组项目的场景很好，因为它可以节省多次点击。例如，如果作业具有以下数据项：
最好提供一种一次性编辑所有数据项的机制以及就地编辑每个项目的行为。
内联编辑还可以防止层次结构的其他部分被意外更新。
模态编辑
这种编辑方法在整个层次结构和您正在编辑的部分之间引入了障碍（即您正在输入的信息与其在层次结构中的位置之间的关系不会立即显现出来）从用户界面来看）。
新屏幕
与模态编辑一样，编辑信息与整个层次结构的关系会丢失。然而，这是一个非常基本的设置，大多数用户群都会立即理解。它还可以保护整个文档免遭意外更新。
所有字段打开
这提供了将编辑的信息保留在上下文中的好处（与就地编辑一样），并且非常简单。不存在需要用户学习必须单击元素才能编辑它的学习曲线。
然而，作为一个有不止一种形式被我好奇的孩子毁掉的人，我不喜欢它如何将整个层次结构暴露给意外的更新。
It depends. If your user base is web savvy, I would recommend an edit in place approach because of the natural editing flow it provides.
Edit in place
When you edit a section of a heirarchy, you edit inline with the rest of the information. This allows you to check how your edits apply to the other information as you're making them (rather than having to move back and forth between screens).
In terms of usability, a scenario where grouped items are editable all at once is nice as it saves multiple clicks. For example, if a job has the following data items:
It's good to provide a mechanism to edit all at once along with the edit each item in place behavior.
Inline editing also protects the other sections of the hierarchy from being accidentally updated.
Modal Edit
This editing method introduces a barrier between the hierarchy as a whole and the section you're editing (i.e. the relationship between the information you're entering and it's place in the hierarchy isn't immediately apparent from looking at the UI).
New Screen
As with the modal edit, the relationship of the edited information to the entire hierarchy is lost. However it is a very basic setup that most of your user base will understand immediately. It also protects the entire document from accidental updates.
All Fields Open
This provides the benefit of keeping the edited information in context (as with edit-in-place) and is very simple. There's no learning curve that requires a user to learn they have to click an element to edit it.
However, as someone that has more than one form ruined by my curious kids, I don't like how it exposes the entire hierarchy to unintended updates.