PowerBuilder v8 和 PowerBuilder v12 之间的区别
PowerBuilder 8 和 PowerBuilder 12 有什么区别？
What is the difference between PowerBuilder 8 and PowerBuilder 12?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
哎呀。嗯，首先，有六个主要版本。 （Sybase 自 v10 以来一直在 x.5 狂潮中。）我希望您不要认为一页中可以描述六个版本，尽管 Stephanie 在一行中做得非常好。 <咧嘴笑>
因为我不知道是什么让你的船摇摇欲坠（网络服务可能会让一个人高兴，而另一个人多年来一直在寻找新的菜单样式，而另一个人可能会欣喜若狂，因为 Trim() 的新重载将提高他的性能每晚的批处理足以让他按时上床睡觉），让我向您推荐我的列表PowerBuilder 历史记录，这将使您从 v8 升级到 v11.5。 （是的，v12 丢失了：长话短说，没人关心。它会得到修复。）希望通过浏览那里，您会找到对您和您的特定应用程序有用的内容。
如果您希望将您的应用程序转移到可以与最好的 GUI 竞争的地方，v12 是一个游戏规则改变者。 PB.NET 不仅使您能够访问 WPF（它在 GUI 构建部门中具有相当强大的潜力），而且还使您能够访问 .NET 框架。进入它是一个相对轻松的迁移过程（比大多数 PB 迁移更困难，比重写更容易<grin>），这将让您进入水域并让您开始尝试如何充分利用所有这些潜力。如果您还没有准备好进行这种飞跃（迁移是单向的），那么仍然可以使用用于 Win32、WinForms 和 WebForms 开发的 PB Classic。当您获得 v12 时，您将获得这两个环境。
祝你好运，
特里
Yikes. Well, first off, six major versions. (Sybase has been on an x.5 binge since v10.) I'm hoping you don't think six versions can be described in one page, although Stephanie did a pretty good job with one line. <grin>
Since I don't know what rocks your boat (web services may make one happy, while another has been looking for new menu styles for years, while yet another might get ecstatic that the new overload of Trim() will improve the performance of his nightly batch process enough that he can go to bed on time), let me refer you to my list of PowerBuilder history, which will get you from v8 to v11.5. (Yes, v12 is missing: long story, no one cares. It'll get fixed.) Hopefully by browsing through there, you'll find what is useful for you and your specific application.
If you're looking to move your application to something that can compete with the best GUIs out there, v12 is a game changer. PB.NET gives you not only access to WPF, which has some pretty strong potential in the GUI building department, but also gives you access to the .NET framework. Getting into it is a relatively painless migration process (more difficult than most PB migrations, less difficult than a rewrite <grin>), which will get you into the waters and let you start experimenting with how to take advantage of all that potential. If you're not ready for that kind of leap yet (the migration is one-way), there's still PB Classic for Win32, WinForms and WebForms development. You get both environments when you get v12.
Good luck,
Terry
我确信有很多细微的差别，但从高层次来看，它仍然几乎相同。
我使用 PB12 classic（不是 .NET），它与 PB7 中的几乎相同。与更现代的语言和 IDE 相比，它仍然很糟糕。它仍然经常使 IDE 崩溃。 powerscript 语言也是一样，但现在远远落后于 Python、C#、Ruby 等更现代的语言。与 Java 相比，它甚至显得很古老！如果您不按照正确的顺序手动重新生成对象，您仍然会遇到奇怪的行为。调试器仍然拒绝删除断点，并且会经常崩溃。所以，根据我的经验，PB12 与以前的版本并没有太大的不同。
因此，如果您有现有的应用程序，请继续升级 - 可能有大量的错误修复和其他内容。
如果您有 PB8 并且想要启动一个新的应用程序，那么就开始使用 PB8 并看看它进展如何——您可以稍后升级。
如果您正在考虑在 PowerBuilder 中启动一个全新的应用程序，那么...考虑替代方案。
I am sure there are many little differences, but from a high-level, it's still pretty much the same.
I use PB12 classic ( not .NET ), and it's pretty much the same thing that it was back in PB7. It still sucks pretty badly compared to more modern languages and IDEs. It still crashes the IDE quite often. The powerscript language is the same, and is now way behind more modern languages like Python, C#, Ruby, etc. It even seems old compared to Java! You still get strange behaviors if you don't manually regenerate objects in the right order. The debugger still refuses to remove breakpoints, and will crash often. So, in my experience, PB12 is not hugely different from previous versions.
So, if you have an existing app, then go ahead and upgrade -- there are probably tons of bug fixes and stuff.
If you have PB8 and want to start a new app then get started in PB8 and see how it goes -- you can upgrade later.
If you are considering starting a brand new app in PowerBuilder, then...consider alternatives.
主要变化是 string 和 char 变量是 Unicode（2 字节）而不是 Ansi（1 字节）。
A major change is that string and char variables are Unicode (2 bytes) instead of Ansi (1 byte).