我应该什么时候使用编辑器网格或 extjs 表单
我可以通过 extjs 编辑器网格以及 extjs 表单对表进行插入，我应该使用什么以及何时使用什么？ 哪个更好？我使用了 extjs 表单面板，但没有使用编辑器网格？
我应该使用编辑器网格吗？
I can make the inseration to the table by extjs editor grid and also through the extjs form , what should i used and when i used what ?
which is better ? i had used the extjs form panel but i haven't used the editor grid ?
should i use the editor grid or not ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这与您为用户提供什么样的用户体验有关！以这些场景为例：
1。频繁修改
假设用户需要频繁修改、向网格添加记录。在这种情况下，使用表单面板对于用户来说可能是一个“漫长的过程”。他可能必须选择记录，单击编辑按钮，然后弹出表单，进行编辑并最后保存。
为了减少用户的点击并减少流程..可以使用编辑器网格。
2.查看/过滤/报告
常见的场景是使用网格来简单地查看、过滤掉所需的记录，并将网格用作包含分组数据、汇总数据等的报告。在这种情况下，您甚至可能没有添加功能。您进行编辑的机会可能会减少。在这种情况下，您将选择普通网格。
现在，在某些情况下，网格显示只是一个摘要。在我的一个应用程序中，网格上只列出了几个字段（仅重要字段）。选择一行将在带有表单面板的窗口中为您提供更多详细信息。在这种情况下，您无法使用编辑器网格，因为在给定时间只有部分数据可见。
另一种查看方案是在网格旁边有一个包含所有字段的表单，并且它们绑定在一起。在这种情况下，表单面板位于网格旁边。当用户选择一行时，数据将加载到表单中。您可以在此处提供数据修改功能。 示例！
3.涉及的数据类型
您还需要考虑您显示和操作的数据。编辑器网格非常适合快速、频繁的更改。但对于编辑长且复杂的数据来说，这可能不是一个好主意。例如，编辑器网格中是否有 HtmlEditor（富文本编辑器）？
当您按步骤（某些向导、逐步输入等）输入数据时，您无法使用编辑器网格。在这种情况下，您将不得不使用 FormPanel。
我想这几点会对你有所帮助。
Its about what kind of UX you are providing to your users! Take these scenarios:
1. Frequent modifications
Lets assume a user need to frequently modify, add records to the grid. In this case, using a form panel can be a "long process" for the user. He might have to select the record, click on edit button and the form pops up, edit and finally save.
To reduce the user's click and reduce the process.. you can use the editor grid.
2. Viewing / Filtering / Reports
Common scenario is to use the grid for simply viewing, filtering out required records and use as grid as reports with grouped data, summary data etc. I this case, you may not even have a add functionality. You may have a less chance of edits. In this case you will go for normal grids.
Now, there are situations where the grid display is only a summary. In one of my applications, I have only few fields listed on the grid (only important fields). selecting a row will provide you more details in a window with form panel. In such cases you cannot have editor grid because only part of the data is visible at a given time.
Another viewing scenario is to have a form beside the grid with all the fields and they are bound together. In such a scenario, you have the form panel beside the grid. And when user select a row, the data is loaded into the form. You can provide data modification functionality here. Example!
3. Type of data involved
You also need to consider the data you display and manipulate. Editor grids can be good for quick and frequent changes. But It might not be a good idea for editing long and complex data. For example, would you have a HtmlEditor (Rich text editor) in the editor grid?
You cannot use editor grid when you have data entry in steps (some wizards, step-by-step entry etc). In such cases you will have to go with the FormPanel.
I think these points will help you.