Tampilkan postingan dengan label powerbuilder. Tampilkan semua postingan
Tampilkan postingan dengan label powerbuilder. Tampilkan semua postingan

Rabu, 13 Januari 2010

POWER BUILDER 11.5

NEWES IN POWERBUILDER 11.5

The latest version of PowerBuilder brings .NET interoperability enhancements, DataWindow innovations and many other new capabilities to make your job even easier, your applications even more robust and your development even faster. Here's what's new in PowerBuilder 11.5:

PowerBuilder is .NET
PowerBuilder gives developers the flexibility and power to bring existing applications into or build entirely new applications for .NET WinForms, WebForms and Smart Clients. Delivering on another phase in our .NET roadmap, PowerBuilder 11.5 provides:

* Support for Strong Named Assemblies
* The ability to access .NET static, primitive and enumerative classes
* Support for IIS7

Supplanting the need to “rewrite for .NET”, PowerBuilder 11.5 delivers rich, fresh applications with speed and ease.

DataWindow® Innovations
PowerBuilder 11.5 brings more advancements to the patented DataWindow - the fastest data access, manipulation and presentation tool around. With PowerBuilder 11.5, new and enhanced data visualization features provide even richer presentation of business data through a highly graphical and interactive user experience. DataWindow innovations include the ability to render pie, column, bar, line, and area charts all in 3D, special gradient and transparency features, and support for PNG files. Plus, Rich Text Edit style for columns has been added.

Simplifying Security
Additional security tools that enable you to deliver applications that meet today's protection, compliance and integrity needs are built right into PowerBuilder 11.5. PowerBuilder 11.5 now supports the Federal Desktop Core Configuration (FDCC) regulation required of all federal agencies and contractors. In addition, there is support for CAS (Code Access Security), allowing .NET applications to run in partially trusted zones.

New Native RDBMS Support
Continuing its tradition as an open tool, PowerBuilder 11.5 comes with native drivers for SQL Server 2008 and Oracle 11g for utmost developer efficiency and productivity.

Application Server Plug-in and PocketBuilder – For Free
PowerBuilder 11.5 (Enterprise Edition only) now ships with the Application Server Plug-in, which supports the ability to deploy into third-party application servers, directly from the PowerBuilder IDE. PowerBuilder objects can be deployed to JEE application servers where they will act just like EJBs. And for those of you with mobile development mandates, PowerBuilder 11.5 also comes with PocketBuilder, enabling agile Windows Mobile™ development

PowerBuilder Web Screen Shots

Here's a sampling of some of the UI and DataWindow enhancements found in PowerBuilder 11.5. Click each screen capture to view larger.

Kamis, 04 Juni 2009

PowerBuilder Utilities

All of the utilities available for download on this page are written using PowerBuilder and require the PowerBuilder 32bit runtimes. If you have the PowerBuilder development environment you will already have these runtime files installed on your machine. The older utilities are supplied without the runtime included and these will use the VM from your development environment. However to reduce the risk on an incompatibility between the PowerBuilder versions and to allow people with older versions of PowerBuilder to use the tools with the latest VM, the VM is now being included as part of the install.
Install including PB Virtual machine
The utilities which include the VM come as two different installs, Ansi and Unicode. If you are using the Ansi version of PowerBuilder (PB4 through PB9) then download the Ansi version. If you are using PowerBuilder 10, 10.5, 11 or Pocket PowerBuilder 1, 2 then you need the Unicode version.The Unicode version of the utilities will read Unicode and Ansi files, however the performance of the Unicode version reading the Ansi files is not as quick as the pure Ansi version. The Ansi and Unicode versions can be installed side by side.

PBDelta V5.2.9
  • PBDelta for Unicode (PB10+ & Pocket PB)
  • PBDelta for Ansi (PB4 through PB9)
PBBrowse V3.3.1
  • PBBrowse for Unicode (PB10+)
  • PBBrowse for Ansi (PB4 through PB9)
PBDoc V3.3.2
  • PBDoc for Unicode (PB10+ & Pocket PB)
  • PBDoc for Ansi (PB4 through PB9)
PBPaste V2.4.0
  • PBPaste for PowerBuilder 11.5
  • PBPaste for PowerBuilder 11
  • PBPaste for PowerBuilder 10.5
  • PBPaste for PowerBuilder 10
  • PBPaste for PowerBuilder 9
  • PBPaste for PowerBuilder 8
  • PBPaste for PowerBuilder 7

Selasa, 26 Mei 2009

EAserver (sybase)

EAServer leverages a new modular architecture to support custom deployments so that applications use only the server pieces that are required. The leading solution for distributed and Web-enabled PowerBuilder applications, EAServer allows existing applications to participate in J2EE 1.4 and Service-Oriented Architectures (SOA).
Sybase EAServer Developer Edition is a free download, not an evaluation version that will time out. Use it as long as you would like for developing applications, and obtain a deployment edition license when the application is ready to be deployed

SQL Anywhere Web Edition

SQL Anywhere Web Edition is a free version of SQL Anywhere available for the development and deployment of web applications using Java, ASP.NET, PHP, and more.
The SQL Anywhere Web Edition may only be used for web browser applications. The SQL Anywhere Web Edition can take advantage of the full power of the computer and SQL Anywhere. There are no restrictions on database size, cache size, CPUs, optimization techniques, execution strategies, or SQL language support. The SQL Anywhere Web Edition has the same excellent performance out of the box that has always been a hallmark of SQL Anywhere.
Data access APIs are available in the SQL Anywhere Web Edition?
  • The SQL Anywhere .NET data provider.
  • The SQL Anywhere PHP API.
  • The iAnywhere JDBC driver.
  • The SQL Anywhere Perl API.
  • The SQL Anywhere Python API.
  • The SQL Anywhere Ruby API.
  • SQL Anywhere web services.

Get It Now

Senin, 25 Mei 2009

Powerbuilder developer tools

pblCompare is a special tool for visual PowerBuilder Library File comparison. It has a number of simple and convenient features that many users have been asking for a long time from a PowerBuilder source code comparison tool.

pblCompare is used to highlight and report on the changes made between versions of library files used for developing PowerBuilder Applications including; complete applications, groups of libraries, single objects.

Use pblcompare, it is easy and fast to show difference of Powerbuilder script, source code of Powerbuilder library files.

Use pblcompare, it also can compare two text file certainly.

Functions:

* Use as a management tool to check all the changes to an application before a new release.
* Find out what and why the changes you just made broke the application!
* export source for objects.

Features:

* pblCompare does not modify PBL's in any way. It's a viewer only.
* PowerBuilder is NOT required. pblCompare does not use PowerBuilder API to read PBL format.
* pblCompare supports PBL format of all version of PowerBuilder 6,7,8,9,10,11.
* compare pb scripts with very fast speed.

pblCompare may be used to compare the contents of two PowerBuilder library files or of more. It may be invoked using several methods depending on what you wish to do

Select and Open Powerbuilder library files in left and right, it fast show difference of Powerbuilder librariesDouble click row who show difference, Objects with difference in library will list
Double click object, it will show script of object frame, you will see what difference between two copy of Powerbuilder files
download free

NAMING CONVENTION IN POWERBUILDER

As in many programming languages , naming conventions have emerged.The management of many objects becomes imposible if they are not named according to convetion.Naming convetions are particulariy important when working in a them with other developers.

While your organization very likely will have its own naming conventions, there are several dlfauts that are used in powerbuilder. You are not forced to us these defaults but most developers do.

Naming Convention for Object

These prefixes may appear as defaults when you create an instance of these object
Type Of Object Prefix
Window w_
Menu m_
User Object u_
Datawindow dw_
Function f_
Structure s_
Query q_
Project p_

Naming Convention for Control
When you place one of these controls in a window for the control.

Type Of Control Prefix

Checkbox cbx_
Commandbutton cb_
Editmask em_
Dropdownlistbox ddlb_
Groupbox gp_
Radiobutton rd_
Singleline edit sle_
Statictext st_

Minggu, 24 Mei 2009

Windows

Windows can be built in tw ways. You can either build a new window from scratch, or you can build a windo that inherits some of its characteristics from an existing window. INHERITANCE is described later. Inheritance can be a powerful time saving tool if it used correctly. The following types windows are used in power builder:
• Main
• Respone
• Popup
• Child
• Multiple Document Interface frame (MDI)
• MDI frame with Microhelp

Main Windows are stand alone windows that are independent from all other windows. You can use main window as the anchor for your application.
Respone Windows are used to get repone from the user. A typical respone window is sometimes known as dialog boxes they enter into a dialog with user.
Popup Windows are often to display additional information on a screen inside a window that already open. They are useful from the point of view that they operate under the jurisdiction of parent window which takes care of a lot of the window management problems.
Child Window are similar to popup windows in that they exist only within a parent window. Chiled window have tighter link with the parent window.
MDI or MDI with Microhelp Window is used to open multiple windows, called sheet, within a single parent window. The user is able to move freely from sheet to sheet and take care of a lot of the tricky window management issues for the programmer, such as closing all of the MDI windows when the parent is closed. MDI frame window is a window with several part a menu bar, a frame, a client area etc.

Characteristics of PowerBuilder Objects


There are several character of powerbuilder objects that are under programmer control, they are :

• Attributes
• Events
• Scripts

Attributes are the properties of an object that control how it appears and how it behaves. They are frequently called properties in powerbuilder. Each different class has properties which are peculiar to that class. Properties can be define by he programmer when she is designing the system. They can also be change while the program is running.

Events are thing that can happen to an object. When you write come script to handle an event for an object, it is called trapping the event. Three event that are commonly trapped are the clicked event, the open event and the close event. You might be write some script associated with the clicked event of a command button. Thie code would be called when the button was clicked.

Script are the blocks of code that are stored inside each object. Unlike structure programming environments, there is no concept of a single contigoues program in powerbuilder. Instead the script reside inside an object. The are associates with evens for that object and are what governs the behavior of the application.

Senin, 16 Februari 2009

Retrive Using Datawindow Browse

when using datawindow browse as the same with datawindow input you can using this script for choosing of rows and retrieve. we can use this script in ancestor mode

SetPointer(HourGlass!)

st_message.visible = true
dw_1.AcceptText()
ibl_modify = false
If dw_1.Describe("datawindow.querymode") = 'no' and ibl_find = true then
dw_1.DataObject = dw_1.DataObject
dw_1.SetTransObject(sqlca)
ibl_find = false
End If
long llo_row
llo_row=dw_1.retrieve()
if llo_row > 0 then
if ibl_find=true then
dw_1.modify("datawindow.querymode=no")
dw_browse.object.data=dw_1.object.data
dw_browse.visible=true
wf_menu_browse(false)
else
wf_menu(3)
end if
dw_1.enabled=false
else
st_message.visible = false
messagebox("Retrieve","Data tidak ada.", Exclamation!)
return
end if
ibl_find_2 = false

Senin, 29 Desember 2008

Declare Cursor

sql_perintah="select th"+ string(ii_tahun) +"from gaji_pokok where kd_golongan= ?"

DECLARE my_cursor DYNAMIC CURSOR FOR SQLSA;

PREPARE SQLSA FROM :sql_perintah;
OPEN DINAMIC my_cursor using :kd_golongan;
FETCH my_cursor INTO :id_tahun;

If sqlca.sqlcode = 100 then
messagebox('Informasi','data tidak ada')
End if

CLOSE my_cursor;

Selasa, 09 Desember 2008

get datawindows

many type of data windows can use for reporting or form, Usualy for reporting you can use tabular type
get the data windows
dw_1.reset()
dw_1.retrieve() // get the datawindow ( dw_1)
dw_1.retrieve(unit,tgl_proses) //get the datawindow ( dw_1) with parameter

Minggu, 30 November 2008

Send Variabel to Datawindow

send variabel tertentu to data windows :

d_1.setitem( baris , 'field_datawindows ' , variabel )

contoh:
dw_1.setitem(dw_1.getrow(),'alamat',ls_alamat)

for baris = 1 to dw_1.rowcount()

dw_1.setitem(baris,'alamat',ls_alamat)

next

Kamis, 27 November 2008

Get Field dalam datawindows Report ( Tabular )

Untuk mengambil file dari datawindows pada row model report ( tabular ) digunakan perintah
//==untuk row / abris yang sedang aktif
string ls_var1
dec lc_var2, lc_hitung
date ld_var3
datetime ldt_var4
int baris

dw_1.retrieve() //==mengambil data

for baris = 1 to dw_1.rowcount()

ls_var1 = dw_1.getitemstring(baris,'field1')
lc_var2 = dw_1.getitemnumber(baris,'field2')
ld_var3 = dw_1.getitemdate(baris,'field3')
ldt_var4 = dw_1.getitemdatetime(baris,'field4')

//===hitung
lc_hitung = lc_var2 * 100

next

Get Data Windows Variable ( get field )

get the row of datawindows we can use this sintaks:


string ls_var1
dec lc_var2
date ld_var3
datetime ldt_var4

ls_var1 = dw_1.getitemstring(dw_1.getrow(),'field1')
lc_var2 = dw_1.getitemnumber(dw_1.getrow(),'field2')
ld_var3 = dw_1.getitemdate(dw_1.getrow(),'field3')
ldt_var4 = dw_1.getitemdatetime(dw_1.getrow(),'field4')

Rabu, 26 November 2008

Declaring Variable

To declare a variable, you first type in the data type followed by the name of variable. You can also assign the variable a default value by makin the name equal to appropriate value

Integer il_var_sex
Long ll_salary = 1000000
Date ld_daytogo
Date startdate = 1995-03-01

Data Types

PowerBuilder can handle many diffrent types of data. A few of the standart data type are given below:

Boolean -> True or False
Integer / Int -> 16 bit signed integer from -32768 to 32768. Whole number is not decimal points
Long -> 32 bit signed interger from -2.147.483.648 to 2.147.483.648 it is the same as an integer
String->This data type hold between 0 - 60.000 ASCII character
Blop -> A Binary Large Object can be use for extreme large data item
Datetime -> The date and time store as a single data
Dec -> These are signed decimal number with up to 18 digits
Dauble/Real -> The data types used to store very larger or very small number
Date -> Define variable as date

Gretting Aplication

Gretting for every day

ll_jam = hour(now()) * 3600 + minute(now()) * 60 + second(now())

CHOOSE CASE ll_jam
CASE IS <>
ls_slm = 'Selamat Pagi' // good morning
CASE 39601 to 54000
ls_slm = 'Selamat Siang' // good afternoon
CASE 54001 to 64800
ls_slm = 'Selamat Sore' // good evening
CASE ELSE
ls_slm = 'Selamat Malam' // good night
END CHOOSE

Senin, 24 November 2008

Open Window with parameter

when you call (open) the windows search in main windows and want to return variable you can use this script

string ls_parm

if keydown(KeyF1!) then
OpenWithParm( w_search, ls_parm, parent)
ls_parm = Message.StringParm
this.SetText(ls_parm)
end if

Using Enter Key

Default moving between field or column is “tab key” if you want to change the movement with “enter key” you can use this script. First you can make custom data window even ( even id : pbm_dwnprocessenter even name : rowenter return variable : long an then you can use this script for data windows and using “enter key” to move pointer between field.

Send(Handle(This), 256, 9, Long(0, 0))
Message.Processed = TRUE

Message.ReturnValue = 1

Senin, 27 Oktober 2008















Windows Search

If you want to make windows seacrh with user object control you can use windows object and put the user object control in centre of the windows and then you can use single line edit for search the word and so the button for execute. if you use this windows design you can use this script and put into this script in user event.
// Entry_Chosen Script for UO_1
string ls_selected_value,ls_ret

ls_selected_value = left(return_selected (),6)

if Len (ls_selected_value) = 0 then
RETURN
END IF

// ls_selected_value = "Nothing"

ls_ret = trim(ls_selected_value)

CloseWithReturn(parent,ls_ret)