From the Editor-in-Chief of PowerBuilder Developer's Journal

Bruce Armstrong

Subscribe to Bruce Armstrong: eMailAlertsEmail Alerts
Get Bruce Armstrong via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn

Top Stories by Bruce Armstrong

What we needed to do was implement spell checking in the rich edit fields in our application (see Figures 1 and 2). To do that, we got a license for the Sentry Spelling Checker Engine from Wintertree Software (www.wintertree-software.com). The utility is easily implemented and works quite well on standard Rich Edit controls. However, the PowerBuilder Rich Edit control is an OEM version of an old third-party control that was popular before Microsoft introduced its Rich Edit control to the common controls. As a result, the messages and functions it supports are completely different from those that the Sentry utility is trying to use to interact with the control. Our first approach to dealing with this was to extend the PowerBuilder Rich Edit control so that it mimicked the events and functions of the Microsoft Rich Edit control. However, we soon realized that the amou... (more)

PowerBuilder News

POWERBUILDER Pocket PowerBuilder 8/04 - Sybase announced the general availability of Pocket PowerBuilder, the new integrated application development environment designed to simplify and speed the creation of mobile and wireless enterprise applications. Using Pocket PowerBuilder, developers can meet the growing demand for enterprise-class mobile solutions that deliver critical business information to workers using Windows CE-based devices. In addition, current PowerBuilder developers can leverage their expertise to build new and extend existing applications to mobile devices, help... (more)

The Next Paradigm Shift...

First there were the thin clients. Not the Internet thin clients, I'm talking about the mainframe applications with dumb terminals. Everything ran on the server; the client was basically there only to display and for input from the user. Then PCs came along and a paradigm shift occurred toward thick clients. Really thick clients in fact. Not only was the user interface running locally on the PC, but often so was the data access layer, with the application accessing local database files or perhaps a shared database file on the network. Key reasons for the shift were a better user... (more)

Deploying PowerBuilder Components to JBoss

The PowerBuilder Application Server Plugin (PASP) is a new product offering from Sybase. It's currently in beta as part of the EAServer 6.0 beta; however, when released it will be distributed as a separate product. The PASP allows PowerBuilder developers to deploy PowerBuilder components to third-party application servers (JBoss, WebSphere, WebLogic, etc.), much the same as they can with EAServer today. This is of particular importance in companies that have already standardized on a non-EAServer application server. Another important feature of the new product is the proxy serve... (more)

DataBase Tracing Features

One of the "new" features in PowerBuilder 10.5 was actually initially introduced in the PowerBuilder 10.2 maintenance release. The folks at Sybase finally addressed a number of fundamental issues with database tracing for deployed applications. Trace File Location Users are often running under accounts that don't have Administrative or Power User privileges. As a result, they may not have sufficient rights to create a file in the WINDOWS directory, the very directory where a deployed application was hard coded to store the trace file. We've been able to specify an alternative lo... (more)