Which Features are important for PowerBuilder Projects
PB.NET Features
While the usage rate of PB.NET remains low, we wanted to know why certain projects used this version. The graphs below represent the importance given to different PB.NET features.
The main goal of PB.NET consists of developing desktop applications based on the corresponding .NET technology (WPF). It’s however the feature used the least by participants of the survey, because only 17% believe that it’s a major feature. This result is in part due to the fact that the migration from PB Classic to PB.NET/WPF requires an important effort, which a lot of PowerBuilder projects are not ready to do. WPF could also have been chosen for development of new applications, but we know that a small part of PB users (see above) work on new development projects. They generally evolve existing PB Classic applications.
PB.NET is therefore mainly used to offer existing applications interoperability with .NET. That’s why the creation of components and .NET web services to be consumed by PowerBuilder applications are among the most wanted features in PB.NET.
Finally, we can see the years weighing on PB Classic’s IDE: the features offered by the IDE of PB.NET (based on Visual Studio) are the most appreciated in the ranking.
PB Classic Features
The following is a ranking of PB Classic improvements for your projects. (1 being not important and 5 being crucial)
Other PB Classic Improvements (please explain)
PB IDE - PB Applications UI - DW Enhancements - Interoperability Compatilibity - Web - Mobile - Ntiers - Language - Miscellaneous
PB IDE
PB Applications UI
DW Enhancements
Interoperability compatilibity
Web - Mobile - Ntiers
Language
Miscellaneous
As tablets and wireless networks become more ubiquitous, it's important to have a transaction object that can properly manage connects and disconnects gracefully. The more support for this that can be built into the IDE (instead of having to custom build transaction management), the better. |
Be able to properly patch executable by sending only specific pbd libraries and not complete executable |
A better version controller. |
I want my compiled Help back again!! It’s bloody ridiculous that they released version 12 with such crappy help! |
- when you rename existing event/function it may change its place in functions list in .sr? file, |
- when you edit window with OCX control on it OLE specific data is changed every time, even if you don't change OCX object properties |
- when you group select controls in DataWindow object (with Ctrl key pressed) the order of controls in .srd file changing leading to a mess in comparison between old .srd and new .srd even if the change was minor. |
- the way .pbg files are changing isn't clear, at least it must be documented |
ORCAscript is really weak, it should be more powerful, look at PBOrca. |
Better implementation for Multi threading application allowing PB apps to be more responsive and thus increase the user experience. Faster full rebuilds. |
inline filter, sorting, multi column, keystroke search and find, better stability as I get many null references and unresolvable external linking during runtime and it is not consistent. |
manipulate ZIP libraries including SFX |
Need better Help files, as an example, there should be chapter wise explanation / tutorial of how to go about writing first WEB application. We need guide explaining Client-Server to Web code migration with legacy code salavging. Need explanation with example code for Web Application indicating how to take care of Session, Transaction & Security. |
Poder enviar correos desde codigo de power builder sin necesidad de usar la configuracion de Outlook |
Internal reliable support for hirarchical data (not limited pbxml, not oleobject msxml etc) - 5 |
Send and recieve e-mails, call external functions of DLLs too complicated. |