PowerBuilder 12 的可能性
我是一名 .NET 开发人员，我听说自版本 12 以来 PowerBuilder 增强了与 .NET 的集成。与普通的WPF编程技术相比，使用Sybase PowerBuilder有哪些优势等等？
何时建议使用 Sybase PowerBuilder？
I'm a .NET developer, and I heard that since release 12 PowerBuilder enhanced integration with .NET. What are the advantages of using Sybase PowerBuilder over normal WPF programming techniques and so on?
When is it recommended to use Sybase PowerBuilder?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
使用 PowerBuilder 的第一个优势始终是并且可能永远是 DataWindow。有了它，您可以获得以下优势：
另一件被宣传为优点的大事是您可以使用可视继承。因此，您可以创建一个控件（“标准用户对象”）并将其放置在多个窗口或画布上（“自定义用户对象”）并覆盖后代级别的属性。然后，您可以稍后返回并更改祖先“标准用户对象”上的属性（例如更改您的字体标准），并且更改将传播到使用用户对象的所有位置，假设更改的属性没有在后代级别。我喜欢属性继承，但不如方法继承那么喜欢。例如，通过方法继承，在一个地方进行编码，我可以立即将一种新的控制行为普遍分发到我的应用程序（例如，在 WPF 中，也许我可以在鼠标悬停在按钮上时让按钮发出跳动的红光……或者，在良好的情况下）味道，也许不是）。或者，我可以在祖先中加载可选功能，并立即将其提供给所有后代。
在撰写本文时，PB12 仍处于早期阶段，因此随着人们使用它们，也许会出现新的优势。我保留回来重写我的历史的权利。
祝你好运，
特里。
First advantage to using PowerBuilder has always been and probably will always be the DataWindow. With it, you get advantages like:
The other big thing that has been promoted as an advantage is the fact that you can use visual inheritance. So, you can create a control ("standard user object") and place it on multiple windows or canvases ("custom user objects") and override the attribute at the descendant level. Then, you can later go back and change an attribute on the ancestor "standard user object" (e.g. change your font standard), and changes will propagate to all places that user object is used, assuming the changed attribute isn't overridden at the descendant level. I like the attribute inheritance, but not as much as I like the method inheritance. For example, with method inheritance, coding in one place I can immediately distribute a new control behaviour universally to my application (e.g. in WPF, maybe I could give my buttons a throbbing red glow whenever they are moused over... or, in good taste, maybe not). Or, I can load up optional functionality in the ancestor and make it available to all the descendants immediately.
At the time of this writing, these are still early days for PB12, so maybe new advantages will come out as people use them. I reserve the right to come back and rewrite my history.
Good luck,
Terry.
由于工作原因，我已经使用 PowerBuilder 一年了，以下是我的结论：
由于这些和更多的经验，如果不是绝对必要，我建议您不要花任何时间尝试学习 PB。只需使用 PB 12 提供的 PowerBuilder .NET IDE 即可。
Due to my work, I have been using PowerBuilder for 1 year and these are my conclusions:
Because of those and more experiences, I recommend you not to spend any time trying to learn PB if it is not strictly necessary. Just use the PowerBuilder .NET IDE that PB 12 gives you.
哈哈，“Hans Passant”和“Night Shade”听起来像是有“生产力羡慕”。
当然，您可以使用 C# 或 Python 等第三代编程语言进行编码......并适应 Microsoft 不断规定的架构更改，或者您也可以使用 PowerBuilder 等工具，该工具历来为软件开发人员提供了最高效的平台之一通过保护我们免受普遍存在的底层操作系统 API 和，呃……无尽的架构层的影响，我们可以使用这些功能……
嗯……也许这就是为什么 Microsoft 是 PowerBuilder 的第一批用户之一！
Sybase 作为一家公司能够突飞猛进的发展也是有原因的。您能透露一下移动数据库的市场份额吗？
但话又说回来，我谈论的是现实世界的经济学。您可以交付什么以及需要多长时间。 PowerBuilder 轻而易举地获胜。
从理论上讲，当然，还有其他工具可以在某些方面提供更多功能，但在实践中，特别是对于大型企业数据库系统，几乎没有一个工具可以与 PowerBuilder 做出相同的要求。
一些客户？大多数州政府、西南航空公司、加拿大国家等等。
哦，我们的工资也更高。
:)
Haha, "Hans Passant" and "Night Shade" sounds like they have "productivity envy."
Sure you can code in third-generation programming languages like C# or Python.... and roll with the architectural changes that Microsoft constantly dictate, or you can also use a tool like PowerBuilder which has historically provided software developers one of the most productive platforms available by shielding us from the pervasive underlying OS APIs and, ugghh endless layers of architecture....
Hmmmm... maybe that's why Microsoft was one of PowerBuilder's first users!
There's also a reason why Sybase as a company has been growing by leaps and bounds. Can you say mobile database market share?
But then again I am speaking of real-world economics. What can you deliver and how long will it take. PowerBuilder wins, hands down.
In theory, sure, there are other tools that offer more in some perspectives, but in a practical manner, particularly with large enterprise database systems, there is hardly a tool that can make the same claim as PowerBuilder.
Some of the clients? Most state governments, Southwest airlines, the nation of Canada, etc.
Oh, and we make more in salary as well.
:)