Magento Widgets API 的什么让您感到困惑？
这有点含糊，但我希望我能被允许。
我想了解一下 Magento 开发者社区对 Widgets API 的看法。它们是清晰的还是令人困惑的、有用的还是无用的。越详细越好。你使用该功能吗？如果没有，为什么不呢？您对该功能有什么不明白的地方？ 当我说小部件
时，我指的是特定于该功能的编程 API。
This is a little vague, but I hope I'm allowed.
I'd like to get a feel for what the Magento developer community thinks of the Widgets API. Are they clear or confusing, useful or useless. The more detail the better. Do you use the feature? If not, why not? What don't you understand about the feature? etc. etc.
When I say Widgets, I'm referring the programatic APIs specific to the feature.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是的，这绝对是我们想要更多地关注的事情，但我们还没有留出任何预算来进行实际调查。我很想创建一些我们可以为每个客户端使用的小部件，而不必创建客户端然后必须将数据传递到静态块内部的块。大约一年前我调查过它，但一直没有回头。
有趣的是，现在社区中有很多小部件，但您仍然没有听到任何有关它们的信息。我想我们只需要更多关于它们的文章，我相信在您写一篇之后，我们都会得到它:)。基本上，人们没有时间充分研究 Widget API 来利用它。由于有关它的知识库信息并不多，因此您不会看到很多人使用它们。
Yeah its definitely something we have wanted to take more of a look at but we haven't set any budget aside to actually investigate. I would love to create some little widgets that we could utilize for each client instead of having to create blocks that the client then has to pass data to inside of a static block. I looked into it about a year ago and just haven't looked back.
The funny thing is now there are a lot of widgets out there in the community, yet you still don't hear anything about them. I guess we just need more articles about them, which I am sure after you write one, we will all get it :). Basically people don't have time with how busy they are probably to investigate the Widget API fully enough to utilize it. And since there isn't a lot of knowledge base information about it, you don't see a lot of people using them.
作为一名开发人员，我了解这个 API 的有用性，并且它并不比 Magento 中的任何其他东西更难使用。我经常使用它，因为我能理解它的功能。
但我作为一个人，必须解释什么是小部件，或者为什么我制作了一些小部件，用户或设计者应该如何使用它，为什么并排存在一个块和一个小部件以及有什么区别。然后我倾向于认为这完全是一场灾难，我们应该只有小部件或只有块或一个通用名称以及一些区分小部件的静态和动态版本的类型/属性/值，所以我可以说：“嘿这个块/您可以将小部件拖动或包含在网站中任何您喜欢的位置，而这个小部件则不能”
I as a developer understand the usefulness of this API and it is not harder to use than any other thing in Magento. I have used it a lot cause I can understand the feature.
But me as the person who has to explain what is a widget or why I made something to be a widget, how should a user or designer use it, why there is a block and a widget side by side and what's the difference. Then I tend to think that this is a total disaster and we should have only widgets or only blocks or one common name and just some type/attribute/value that distinguish static and dynamic version of widgets so I could say : "Hey this block/widget you can drag or include wherever you like in your site and this one you can't"
当小部件功能推出时，我感到很兴奋。有不错的文档可供使用，我很快就能够编写自己的简单小部件。然而从那时起，我就再也没有在我的项目中真正使用过小部件。我从来没有真正理解何时使用小部件，我几乎忘记了它们。
我觉得我们需要文章和示例来展示小部件的有用性。当客户询问可以使用小部件解决的功能时，我需要在我的脑海中弹出小部件。最近，一位客户想要在主页的页脚中添加一些文本。我创建了一个静态块并在layout/local.xml 中声明它。对于小部件，这一切都可以从后端完成。
I was excited about the widget feature when it came out. There is decent documentation available, and I was quickly able to code my own simple widgets. Since then, however, I never actually used widgets in my projects. I have never really understood when to use widgets, and I almost forgot about them.
I feel like we need articles and examples to show the usefulness of widgets. I need widgets to pop up in my head when a client asks for features that can be solved using widgets. Recently, a client wanted to have some text in the footer on the home page. I created a static block and declared it in layout/local.xml. With widgets, this could all have been done from the backend.