Every software development project of any significant size or complexity has
a requirement for controlling the source code asset. PowerBuilder is capable
of integrating with any third-party Source Code Control (SCC) tool that
implements Microsoft's SCC API. However, the fact that PowerBuilder stores
its code inside PowerBuilder Libraries (PBLs) and not as individual ASCII
text files adds a layer of complexity to that integration. The release of
PowerBuilder 8.0 in 2001 brought with it a new set of challenges in the form
of a completely redesigned interface with SCC providers, including PBNative.
In this article, I outline the nature of the changes that were introduced in
PowerBuilder 8.0, and discuss many of the enhancements that have been
released with PB 9.0.
Why Version Control?
Version Control software adds significant administrative overhead to every
project, a... (more)
OData is quickly becoming the Lingua Franca for data exchange over the
web. The OData standard defines a protocol and a language structure for
issuing queries and updates to remote data sources, including (but not
limited to) relational databases, file systems, content management systems,
and traditional web sites. It builds upon existing Web technologies, like
HTTP and RESTful web services, the Atom Publishing Protocol (AtomPub), XML,
SAP and Sybase iAnywhere released SQL Anywhere version 16 in March 2013, and
it had many cool new featur... (more)
When Sybase first released the Unwired Platform in 2008, it was intended to
be a complete end-to-end development environment for mobile applications.
SUP developers would create the middle tier components (a.k.a. Mobile
Business Objects), and the client application executables from a single,
integrated Eclipse-based toolset. There was a "PowerBuilder-like" 4GL
screen painter, called the Device Application Designer (or DAD), that
compiled down to native Blackberry 5/6 or Windows Mobile 6.5 applications.
(Yes, it's hard to imagine, but there was a time when iOS devices were not ... (more)
Every development shop that is currently managing its PowerBuilder source
code with a third-party SCC tool and has not yet migrated to PB8 will need to
understand the upcoming changes in methodology before attempting a migration.
Even PBNative users will be affected, as that interface has been redesigned
to use the SCC interface as well.
In my previous article, "Understanding the SCC Interface in PowerBuilder 8"
(PBDJ, Vol. 8, issue 11), I outlined the sweeping rewrite of the source code
control (SCC) interface introduced in PowerBuilder 8.0. This article walks
through some simp... (more)
Sybase recently announced the first public beta of PowerBuilder 12. This is
the release that will complete Sybase’s vision of
having PowerBuilder fully support .Net development. There will be two
separate IDEs in the box:
The classic PowerBuilder IDE will still exist, and will continue to allow you
to develop and deploy traditional Win32 client/server targets, Windows
Forms, Web Forms, and J2EE components. The new PB.Net IDE will be based on
the Visual Studio Isolated Shell, and this will be the tool you’ll use for
Windows Presentation Foundation (WPF) targets, as well as the... (more)