{"id":2139,"date":"2021-03-16T21:54:00","date_gmt":"2021-03-17T01:54:00","guid":{"rendered":"https:\/\/anvil-of-time.com\/?p=2139"},"modified":"2021-03-16T13:56:30","modified_gmt":"2021-03-16T17:56:30","slug":"100-days-of-powerbuilder-tutorial-day-4-a-look-at-the-ide","status":"publish","type":"post","link":"https:\/\/anvil-of-time.com\/powerbuilder\/100-days-of-powerbuilder-tutorial-day-4-a-look-at-the-ide\/","title":{"rendered":"100 Days of PowerBuilder – Tutorial – Day 4: A Look at the IDE"},"content":{"rendered":"\n

This is part of my project ‘100 Days of PowerBuilder’ which is a series of discussions focused on basic PowerBuilder development.<\/p>\n\n\n\n

Note: This article is written with examples created in PowerBuilder 2019 R3. The same steps would be pretty close with any version going back to 9.<\/em><\/p>\n\n\n\n

Mastering the PowerBuilder Integrated Development Environment (IDE<\/a>) is the key to becoming a successful PB developer. As is normally the case with an IDE, there are many ways to accomplish the same task and each developer will create their own processes to do so. In this discussion we will go over some common configuration changes which should enhance productivity within the PB IDE.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Here again is the standard screen normally presented after PowerBuilder is installed and run for the first few items. Now it’s time to banish this since we no longer need it. Select the ‘Reload last workspace\u2026’ option and unselect the ‘Show this dialog\u2026’ and then close the window.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Now from here we have selected our ‘100day’ target and opened the ‘w_main’ object in the IDE. The system treeview on the left is a nice navigational tool but it is always on top. Sure we can resize it or move it to another place but we still have the issue that it reduces the working area within the IDE. Close this frame altogether.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

While we are at it, lets set up some system options to make things a bit more friendly. Open the System Options dialogue. <\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

Unselect the ‘Automatically Clear Output…’ option. This is especially important when searching through the code within the IDE. If you leave this option checked, previous search results are cleared; if you have a photographic memory then leave it checked. Select the ‘Disable database connection when compiling…’ option. This prevents the IDE from attempting to connect to the default database when performing a build (normally this is not important).<\/p>\n\n\n\n

On the Workspaces tab you should have the ‘Reopen workspace…’ option checked.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Remember to click OK to save these changes.<\/p>\n\n\n\n

Getting back to the IDE we see that the working area is fairly large now and encompasses almost all of the space within the IDE. To view our workspace and the associated object we need to bring up the Library Painter. Choose the Library Icon from the toolbar.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Notice the default location is My Computer which is of limited use. The library painter is very similar to the Explorer window in Windows. The left treeview is for navigation and the right is the detail. Right click on the treeview on the right.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

Choose the Set Root option and then ‘Current Workspace’<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Now when you open the Library Painter you see the Workspace treeview to the left and the current object pane on the left.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

While in the Library Painter we can set some options, first on the General Tab<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

and then in the Include Tab.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

I normally don’t make any changes here to the defaults.<\/p>\n\n\n\n

Now when we click on an object to open it we see that the script painter opens much larger and is on top of the library painter.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

So if we take a closer look at the Script Painter for our window we have created we have the basic layout as shown.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Along the bottom of the ‘working area’ are a series of tabs.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

These show the visual layout of the object, the current script (in our case the closequery event script), the list of Events, the list of Functions, and the Declare Instance Variables script.<\/p>\n\n\n\n

On the right side of the working area is the Properties pane.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Along the top are a series of tabs showing various properties. These tabs (and properties) change based on the object selected in the Layout tab of the window or from the Control list (shown below).<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Along the bottom of the Properties pane are tabs for the Properties, the Control List, and the Non-Visual Object List<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

If you right click within the General properties area on the Properties tab you can change the layout of the tabs. The default is Labels on Top.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Here is the appearance when Labels On Left is chosen.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

In this mode the information is shown in less space.<\/p>\n\n\n\n

The Control List tab for our sample application looks like this.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

You can select another control by clicking on it from the list. In this case we have two controls, the main window and the exit button.<\/p>\n\n\n\n

You can control the various panes shown in the script painter from the View menu option. Here we are choosing to have the Event List in its own pane.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Since our system option is to have Horizontal Windows dominate the event list shows on the bottom. Not too helpful in my book.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Move the pointer over the separation bar of the Event List and the title bar appears. From this point you can ‘pin’ the titlebar by clicking on the pushpin icon.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Drag on the titlebar with the pointer to change the location of this pane. Move it to the tab area below the Properties pane (or some other location). You will see a shadow box appear indicating the location will receive the dropped pane.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Now the Properties pane is ‘split’ into two with the newly dragged Event List on the bottom.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Do the same with the Function List so now you have both lists (as tabs) underneath the Properties pane. You can now experiment with changing the Properties pane width to give your script pane the most area possible.<\/p>\n\n\n\n

If you really screw things up or just want to start over, go to the View menu, choose Layouts and then (Default). You can also save layouts here once you come up with one or more you really like.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"

This is part of my project ‘100 Days of PowerBuilder’ which is a series of discussions focused on basic PowerBuilder development. Note: This article is written with examples created in PowerBuilder 2019 R3. The same steps would be pretty close with any version going back to 9. Mastering the PowerBuilder Integrated Development Environment (IDE) is…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[86,3],"tags":[62],"_links":{"self":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/2139"}],"collection":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/comments?post=2139"}],"version-history":[{"count":10,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/2139\/revisions"}],"predecessor-version":[{"id":2181,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/posts\/2139\/revisions\/2181"}],"wp:attachment":[{"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/media?parent=2139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/categories?post=2139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/anvil-of-time.com\/wp-json\/wp\/v2\/tags?post=2139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}