Sybase Powerbuilder 的替代 IDE
有谁知道 Sybase Powerbuilder 的替代 IDE 吗？ 使用 VS2008 和 Eclipse 后，感觉非常笨重。
如果没有，是否有人在 IDE 之外成功地使用了这种语言？ 我并不反对使用简单的文本编辑器，但我发现编辑-导入-重新生成-测试-导出-编辑比简单地使用 Powerbuilder 编辑器更笨拙。
迄今为止，我唯一取得成功的工具是：
- PowerGen，用于构建（使用 NUnit 和 CruiseControl.NET）
- ConTEXT，它具有 Powerbuilder
- PBL Peeper 的语法突出显示功能，它具有 IDE 中不存在的一些有趣功能
编辑：我添加了赏金以引起对这个问题的更广泛的关注。 如果它存在的话，那将是一件非常好的事情。
编辑：嗯，这令人失望。 赏金显然没有让 1 个新人看到这个问题。
Does anyone know of an alternative IDE for Sybase Powerbuilder? It feels pretty clunky, after working with VS2008 and Eclipse.
If not, has anyone successfully worked with this language outside the IDE? I'm not against using a simple text editor, but I find edit-import-regenerate-test-export-edit is clunkier than simply using the Powerbuilder editor.
To date, the only tools I have had any success with are:
- PowerGen, for builds (with NUnit and CruiseControl.NET)
- ConTEXT, which has syntax highlighting for Powerbuilder
- PBL Peeper, which has some interesting features not present in the IDE
EDIT: I added a bounty to draw some wider attention to the question. It would be a very nice thing to have, if it exists.
EDIT: Well that was disappointing. The bounty apparently did not cause even 1 new person to look at the question.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
我不知道，尽管您可能可以使用源代码控制工具，在源代码控制存储库中进行编辑，并从 PB IDE 获取最新版本来缩短文本编辑器周期。 请注意，编辑超过 128 个 ASCII 的任何内容都需要进行黑客攻击。 （我的猜测是，这是为了允许所有 Unicode 在最严格的源代码控制工具中进行源代码控制。）
正如 Paul 所说，PB12 是基于 Visual Studio shell 的，并将包括可折叠代码块、Intellisense 等内容，等等....但是，对于 PB12，这将仅用于 WPF 目标和一些 .NET 类型目标（如程序集），我最后听说。 Win32 目标将继续使用“经典”IDE。
祝你好运，
特里。
PS 感谢 PBL Peeper 的称赞。
None that I'm aware of, although you could probably use a source control tool, edit in your source control repository, and Get Latest Version from the PB IDE to shorten your text editor cycle. Be warned that there are hacks required to edit anything over 128 ASCII. (My guess is that this is to allow everything Unicode to be source controlled in the most restrictive source control tools.)
As Paul said, PB12 is coming with based on the Visual Studio shell, and will include things like collapsible code blocks, Intellisense, etc.... However, for PB12, this will only be used for WPF targets and a few .NET-type targets (like assemblies), last I heard. Win32 targets will continue to use the "classic" IDE.
Good luck,
Terry.
P.S. Thanks for the PBL Peeper compliment.
PowerBuilder IDE 很笨重，但我认为完全在 PowerBuilder IDE 之外进行开发并不是一个好主意。 我认为现在有太多的依赖关系。
然而，PowerBuilder 12 的 IDE 将使用 Microsoft 的 Visual Studio Independent Shell 构建，因此发布后它应该会更好。 另外，我相信他们将废除 PBL 格式，这应该会使源代码控制更容易使用。
当然值得一看。
The PowerBuilder IDE is clunky, but I don't think developing completely outside the PowerBuilder IDE is a good idea. I think there are just too many dependencies right now.
However, the IDE for PowerBuilder 12 will be built using Microsoft's Visual Studio Isolated Shell so it ought to be much better when that is released. Also, I believe they'll be doing away with the PBL format which ought to make source control much easier to work with.
Certainly something to watch.
我所做的就是右键单击该对象并编辑源。 然后我复制文本并将其粘贴到 Notepad++ 中进行编辑。 我复制并粘贴回 PowerBuilder，然后我可以保存并查看任何错误。 如果有人感兴趣的话，我有一个相当不错的 PowerScript 用户定义语言。
添加：
请注意，我曾见过 PB Source 编辑器损坏了 DataWindows。 它们都是大型数据窗口。 为了安全起见，请始终导出 DataWindows 进行编辑。
What I do is right-click the object and edit source. Then I copy the text and paste it into Notepad++ to edit. I copy and paste back to PowerBuilder, then I can save and see any errors. I've got a fairly decent User Defined Language for PowerScript if anyone's interested.
Added:
Please be aware that I've seen the PB Source editor corrupt DataWindows. They were all large DataWindows. To be safe always export DataWindows to edit.
Visual Expert 是最有可能使您的 PB 体验变得更好的工具，它提供了一个很好的源浏览器。 恕我直言，这样的工具早就应该集成到PB IDE中了。 唯一的问题是它不是免费的，与您提到的其他工具相反。
关于使用外部源编辑器，您可能可以利用 OrcaScript，它是一种脚本语言，可让您执行从 IDE 外部导出和导入 PB 对象等操作。 这需要一些努力，但您可以使用带有 ORCA 脚本的批处理文件和一些其他外部工具来设置基本的开发环境。 但是，此设置将缺乏任何可视化编辑功能，这意味着没有（可行的）GUI 或 DW 工作。 如果您最喜欢 NVO，那么它可能会起作用。 但如果是这样的话，为什么首先要使用 PB？...
我也听说 PB12 对 VS 的使用将仅限于某些 .NET 内容，这可能只会使 PB 程序员社区的一小部分受益。 恐怕我们其他人在未来的几年里都会被这个糟糕的 IDE 困住。
One tool that will most probably make your PB experience way better is Visual Expert, which provides a good source browser. Such a tool should have been integrated into the PB IDE a long time ago, IMHO. Only problem is that it's not free, as opposed to the other tools you mention.
Regarding using external source editors, you can probably take advantage of OrcaScript, which is a scripting language that lets you perform actions such as export and import of PB objects from outside of the IDE. It will require some effort, but you can setup a basic dev env using batch files with ORCA scripts and some additional external tools. However, this setup will lack any visual editing capabilities, which means no (feasible) GUI or DW work. If you're mostly into NVOs, it could work. But then if that's the case, why use PB in the first place?...
I too have heard PB12's use of VS will be limited to some .NET stuff, which will probably benefit only a very small portion of the PB programmers community. I'm afraid the rest of us are stuck with the awful IDE for years to come.
除了导出源代码并对其进行编辑之外，我不知道还有其他用于 PB 的 IDE。 您可能遇到的一个问题是导出的源代码包含许多手册中未记录的语法。 PB IDE 生成此代码，但不支持手动创建它。 我认为你被 PB IDE 困住了
Other than exporting the source and editing it I don't know of another IDE for PB. One problem you may have is that the exported source contains a lot of syntax that is not documented in the manuals. The PB IDE generates this code but there is no support for creating it by hand. I think you are stuck with the PB IDE
在我从 Powerbuilder 5/6 开始，现在使用 PB 10 的五年经验中，我试图：
...我得出的结论是，没有机会改进Powerbuilder 成为最先进的语言
在我的哲学中 - 我在那些年中获得的 - 我区分两种类型的面向 OOP 的语言：
特别是所有对象都应该始终被编译（重新生成）的要求以及不能同时使用祖先和后代的要求使得使用真正的 OOP 变得很痛苦。
...纪念 Unix(Solaris)/C++ 的美好时光...
In my modest five Years of experiences starting with Powerbuilder 5/6, now using PB 10, I tempt to :
... i came to the conclusion that there will be no chance in improving Powerbuilder to an state-of-the-art language
In my philosophy - I obtained during those years - I distinguish between two types of OOP-oriented languages:
Especially the demand that all object should always be compiled (regenerated) and that you could't work with ancestors and descandants concurrently makes it painful to use real OOP.
...In memory of the good old Unix(Solaris)/C++ days...
我正在研究一种类似于 PowerBuilder 的替代解决方案，并且发现了两个引起我注意的解决方案。
第一个是“React Studio”https://reactstudio.com/，我是通过 Alternativeto.net 找到的。
第二个是来自一些谷歌搜索顶部的广告，但它足够相似，乍一看看起来足够好，让我想仔细看看它，它被称为“Servoy”https://servoy.com/ 。
仍在研究中，但目前我的首选是 React Studio。
I was researching a replacement solution that would be similar to PowerBuilder and I came across two that caught my eye.
The first was 'React Studio' https://reactstudio.com/ which I found via Alternativeto.net .
And the second was from an ad at the top of some Google searches but it was similar enough and looked good enough at first glance for me to want to take a closer look at it, and it's called 'Servoy' https://servoy.com/ .
Still researching but I currently have React Studio at the top of our list.
TextPad 编辑器有一个由 [email protected]< 贡献的 PowerBuilder 6.x 语法定义文件/a> 是我几年前免费下载并定制的。 它适用于更高版本（包括 8），在 PowerScript srx 文件上进行关键字颜色突出显示。 在 PB 中编辑大型源文件可能会导致崩溃，因此导出到 srx 文件、在 IDE 外部编辑然后重新导入通常会更安全、更快、更方便。
The TextPad editor has a syntax definition file for PowerBuilder 6.x contributed by [email protected] that I downloaded for free and customized several years ago. It works fine for later versions (including 8), doing keyword color highlighting on PowerScript srx files. Editing large source files in PB could get it to crash so it's usually safer, faster and more convenient to export to srx file, edit outside the IDE then re-import.