SynonymsBot
Synonyms for powerbuilder or Related words with powerbuilder
applescript
ironpython
quickbasic
xcode
jdeveloper
visualage
autoit
netbeans
jbuilder
wxwidgets
jruby
dotnet
aspectj
jython
rexx
borland
haxe
inprise
msxml
javafx
cfml
watcom
foxpro
msvc
fltk
hypercard
unrealscript
zend
freebasic
mingw
glibc
jquery
msbuild
windev
realbasic
aptana
clojure
wxpython
mediawiki
coldfusion
rebol
powershell
ocaml
modula
mxml
cakephp
webmatrix
libreoffice
imagemagick
opensource
Examples of "powerbuilder"
There are a variety of grass roots community groups and resources for
PowerBuilder
developers to share and convene. These include the International Sybase User Group and what some call the very first technical journal devoted to an IDE,
PowerBuilder
Developer's Journal. There are also blogs from TeamSybase and evangelists available. PowerBuilderTV is series of webinars by and for the
PowerBuilder
community with webinars by
PowerBuilder
evangelists, developers and vendors.
PowerBuilder
Central is a community initiative to create a single source for third party add-ons and services. In mid 2013, a community based
PowerBuilder
World Tour was announced spanning 4 continents. In 2010 the DisplacedGuy
PowerBuilder
Blog launched a massive Training Portal one of the largest, regularly updated collections of free
PowerBuilder
information including reference guides, tutorials, videos, sample applications, commercial products, blogrolls, polls, migration guides with emphasis on tutorials for
PowerBuilder
12, 12.5 and PB.NET.
PowerBuilder
Central is a community initiative to create a single source for third party add-ons and services. In mid 2013, a community based
PowerBuilder
World Tour was announced spanning 4 continents.
Extensibility of the language was rather limited for older versions of
PowerBuilder
. The technologies provided to overcome this (ex.
PowerBuilder
Native Interface, or PBNI) are still rather tricky. To develop a solution that includes external C++ code may not only require a competent C++ developer, but also a
PowerBuilder
expert to guide the developer through the myriad subtleties of the language and the
PowerBuilder
Virtual Machine.
PowerBuilder
supports the following ways of interacting with a database:
The
PowerBuilder
Foundation Class Library (PFC) is a set of
PowerBuilder
objects that are customized and used to develop class libraries. These objects can be used to provide corporate, departmental, or application consistency. PFC also includes objects that are used as is for utility purposes, such as debugging. PFC is written in
PowerBuilder
and delivered as
PowerBuilder
objects with supporting PowerScript source code. It uses advanced
PowerBuilder
object oriented coding techniques, and features a service-oriented design that ensures that an application uses the minimum amount of computer resources.
Exception handling is available in
PowerBuilder
versions 8.0 and above.
PowerBuilder
supports ActiveX and OCX controls, both visible and non-visible. It also can use OLE Automation as a client. However,
PowerBuilder
supports only late binding, not early binding. Therefore, when using OLE Automation, a dropdown of possible actions is not provided.
PowerBuilder
can also act as a DDE client or server, providing a further mechanism to interoperate with other applications.
The library was initially developed by Powersoft and introduced when
PowerBuilder
5 was released. The library was later open sourced by Sybase when
PowerBuilder
10 was released. Since then a couple of forks have occurred, including one specifically to support the Appeon web enabling tool for
PowerBuilder
.
PowerBuilder
is an integrated development environment owned by SAP since the acquisition of Sybase in 2010. On July 5, 2016, SAP and Appeon entered into an agreement whereby Appeon would be responsible for developing, selling, and supporting
PowerBuilder
.
PowerBuilder
12, through compatibility with Web technologies such as ASP.NET, represents an attempt to regain market share. In order to move developers to newer versions,
PowerBuilder
12 provides utilities that attempt to simplify migration.
PowerBuilder
is used primarily for building business applications.
PowerBuilder
was used by some companies in the financial and telecoms sectors where Java and Microsoft Visual Studio are more predominant.
PowerBuilder
has been in use since 1991, peaking around 1998 with around 100,000 users.
Over the years,
PowerBuilder
has been updated with new standards. In 2010, a major upgrade of
PowerBuilder
was released to provide support for the Microsoft .NET Framework. In 2014, support was added for OData, dockable windows, and 64-bit native applications.
PowerBuilder
was originally developed by Powersoft in 1991. Powersoft went public in 1993 and was acquired by Sybase for $904 million in Sybase stock in 1995. In May 2010, SAP announced that it would be acquiring Sybase for $5.8 billion.
PowerBuilder
languished for a long time for several reasons:
PowerBuilder
applications are typically compiled to p-code, which is then interpreted by the
PowerBuilder
run time. Although it can be compiled to machine code (called c-code), a typical business application does not run a lot faster. However, applications which do an unusually large amount of computations (I/O, DBMS interaction, etc.) are likely to benefit up to 4,000x faster from compiling to machine code. The main reason why compiling to machine code was not used is an enormous amount of errors in
PowerBuilder
especially in machine code generation.
Since
PowerBuilder
12.0, the (now .NET-compliant) PowerScript language is fully compliant with the Common Language Specification (CLS), and can be compared with C#, Java or VB.NET.
There are a number of third-party tools that build upon and enhance the functionality of
PowerBuilder
, such as Appeon, Visual Expert, and Enable Multilingual.
AscentialTest provides automated testing support for the following application types including MS Windows, Internet Explorer, Firefox, Chrome, Java, dotNet (Winforms and WPF), terminals, Siebel and
PowerBuilder
.
like Borland's ObjectVision, Gupta Technologies's SQLWindows, and Powersoft's
PowerBuilder
. It was bought by KnowledgeWare in 1993. In 1994 Knowledgeware released ObjectView Desktop, a scaled-down version.
ADO is supported in any development language that supports binding to binary COM interfaces. These languages include ASP, Delphi,
PowerBuilder
, and Visual Basic for Applications (VBA). ADO support has now been added to dBase Plus 8 (With ADO)
PowerBuilder
offers native interfaces to all major databases, as well as ODBC and OLE-DB, in the Enterprise version. There are many connectivity options that allow performance monitoring and tuning, such as: