User manual PROGRESS OPENEDGE GUI FOR NET TASK MAP

[. . . ] OpenEdge GUI for . NET Task Map The following tables list selected tasks that you might need to complete when working with the OpenEdge GUI for . NET and where you can find more information about them. [. . . ] In short, an ABL Inherited Control is an ABL class that inherits and extends a . NET control class; an ABL User Control is an Manuals: GUI for . NET Programming · Creating custom . NET forms and controls Generated by Clearspace on 2010-12-17-05:00 2 OpenEdge GUI for . NET Task Map · Sample ABLderived . NET user control Introducing the OpenEdge Architect Visual Designer · Adding LeftBar. cls to the project (example ABL User Control) · Adding HelpButton. cls to the Toolbox (example ABL Inherited Control) ABL class that inherits and extends the OpenEdge-extended . NET class, Progress. Windows. UserControl. , which is a container for other controls. After creating it, you can add each custom control to the Toolbox, from which you can visually add the control or user control to any ABL-derived form that you create. OpenEdge Architect Online Help: · Custom user-defined controls · Creating a user control · Creating an inherited control · Reloading the Design Canvas while using custom controls Video Tutorials: · Creating a Databound TreeView as an Inherited Control, Part 1 · Creating a Databound TreeView as an Inherited Control, Part 2 · Building a Navigation Panel as an ABL User Control Building localized forms Visual Designer automatically creates a resource (. resx) file to store resources used by a . NET form in a GUI for . NET application. To localize the form, you must translate the labels for the form stored in the resource file using third-party tools. Manuals: GUI for . NET Programming · Accessing resource files for . NET forms ABL Reference Generated by Clearspace on 2010-12-17-05:00 3 OpenEdge GUI for . NET Task Map · Progress. Util. ResourceHelper class OpenEdge Architect Online Help: · OpenEdge Architect project and resource data files Using form and control classes across two or more projects To use form and control classes across two or more projects, you must make the class files available to each project. To share control classes across projects, you can set a sharing option that allows you to use a global Toolbox for all projects accessed with the Visual Designer. You can also copy the same toolbox. xml file among different projects or users to share a common Toolbox definition among specific projects of one or more installations of OpenEdge Architect. You can set up company standard form templates by creating ABLderived forms (ABL Form objects in Visual Designer) that include ABLderived user controls (ABL User Control objects in Visual Designer). OpenEdge Architect Online Help: · Shared AVM preference page · Customizing the Visual Designer Toolbox · Sharing Toolbox settings Setting up company standard templates using form inheritance Manuals: GUI for . NET Programming · Creating custom . NET forms and controls OpenEdge Architect Online Help: · Template customization · Customization Editor Generated by Clearspace on 2010-12-17-05:00 4 OpenEdge GUI for . NET Task Map Run time/Deployment Deployment involves setting localization options and installing files associated witht the . NET objects you reference. Task Localizing an application using startup parameters and the machine culture setting Summary You can localize a GUI for . NET application using a setting of the . NET System. Globalization. CultureInfo class, and you can match other ABL data and display options to this setting using the Internal Code Page (-cpinternal), Date Format (d), European Numeric Format (-E), and Use OS Locale (-useOsLocale) startup parameters. Information Source Manuals: GUI for . NET Programming · Regional settings --localization Startup Command and Parameter Reference · Internal Code Page (-cpinternal) · Date Format (-d) · European Numeric Format (E) · Use OS Locale (useOsLocale) Deploying the assemblies. xml file, OpenEdge-installed controls, third-party controls, and your own custom controls When you deploy a GUI for . NET application, you need to locate the assemblies. xml file where OpenEdge can find it and ensure that the assemblies it references are installed appropriately. Manuals: Managing ABL Applications · Deploying OpenEdge GUI for . NET applications WebClient Applications · WebClient and OpenEdge GUI for . NET Data Binding OpenEdge provides the . NET Progress. Data. BindingSource (ProBindingSource) class to bind ABL data to . NET user-interface controls that support data binding using the System. Windows. Forms. BindingSource class. Typically, a . NET control supports data binding using a BindingSource class if it has a property of type System. Object (typically named DataSource) to assign the data source object instance, including a Generated by Clearspace on 2010-12-17-05:00 5 OpenEdge GUI for . NET Task Map ProBindingSource, or it has a property of type ControlBindingsCollection (typically named DataBindings) that you can use to bind data elements from the ProBindingSource to specified properties on the control. For an overview of data binding in the GUI for . NET, see Binding ABL Data to . NET Controls in GUI for . NET Programming. Task Binding data to lists and individual fields with a ProBindingSource Summary You can bind the individual fields of database or temp-table buffers to field and list controls. [. . . ] ABL also supports an implicit mapping between onedimensional . NET array objects and ABL arrays (variables or properties defined with an EXTENT) when you assign between one and the other. Manuals: GUI for . NET Programming · Using . NET data types in ABL · Referencing . NET class and interface types · Using unqualified . NET type names ABL Reference · Data types · Type-name syntax · USING statement Generated by Clearspace on 2010-12-17-05:00 11 [. . . ]