客观评估新的 GUI 工具包
我正在检查一个新的 GUI 工具包，我的第一印象是“哇，这比我以前的工具包难用得多。”但后来我想，“难是因为不熟悉，还是因为有真正的问题？”
有哪些技术可以客观地评估新的 GUI 工具包？
I was checking out a new GUI toolkit, and my first impression was "wow, this is a lot harder to use than my previous toolkit." But then I wondered, "is it harder because it is unfamiliar, or because there are genuine issues?"
What are some techniques for objectively evaluating new GUI toolkits?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我会看看编写某个功能有多困难以及需要多长时间。然后查看所用的总行数/步数。然后最后看看最终的结果。比较这些有助于更容易做出决定，如果需要，只需编写一个小测试程序即可。此外，最终结果不仅涉及外观，还涉及平台依赖性、支持和速度。
I would look at how difficult it is and how long it takes you to write a certain feature. Then look at the total number lines/steps it took. And then finally look at the end result. Comparing those helps make it easier to decide, just write a small test program if you need to. Also the end result involves not only appearence but also platform dependency, support, and speed.