Adobe 65007312 Programming Guide - Page 54

CHAPTER 3: Creating Export and Publish Services Customizing the Export and Publishing Manager dialogs 54 The function that you define here returns a table of tables, where each table defines one dialog section: sectionsForTopOfDialog = function( viewFactory, propertyTable ) return { { ...section entry section entry end A section entry table defines the contents of an implicit container, which Lightroom creates to hold your view hierarchy. X Each section entry sets a title and synopsis for the section; the section is identified by the title text on the left, and is collapsible. When in the collapsed state, the synopsis text is shown on the right: X The rest of the table entry creates the UI elements that are shown when the section is expanded. To create the UI elements, use the LrView factory passed to your top-level sectionsFor... function. This process is explained in more detail in Chapter 5, "Creating a User Interface for Your Plug-in." When adding sections to the Export dialog, the propertyTable parameter for both functions is the property table containing the plug-in and Lightroom-defined export settings. When your plug-in is being used as a publish service provider, the property table contains additional values that tell you about the publishing status; see "Publish Service properties" on page 67. You can add your own program data values to this table (see "Remembering user choices" on page 57), and create bindings between the UI elements and the data values, so that the UI text is dynamically tied to your plug-in data. This is shown in the example below, and explained more fully in "Binding UI values to data values" on page 94. A custom section example This sample code creates a section in the destination dialog with two UI controls, an editable text field and a button. These are in a container, a row element which controls the placement of its child nodes, but is not drawn on the screen. The value of the edit field is tied to a data key in the property table. The enabled state of the button is also tied to a data key, so that the button is only enabled when the user types into the edit field, thus setting the data value. In this example, the synopsis text is also dynamic, bound to the same data key as the edit field value. (Currently, you cannot bind the title value.) Notice that for synopsis, you must specify the bound table explicitly. This is because it is not part of the view hierarchy, where the propertyTable is automatically assigned as the default bound table. All of these concepts and techniques are explained more fully and described in more detail in Chapter 5, "Creating a User Interface for Your Plug-in." sectionsForTopOfDialog = function( viewFactory, propertyTable ) local LrDialogs = import "LrDialogs" -- get the namespaces we need local LrView = import "LrView" local bind = LrView.bind -- a local shortcut for the binding function propertyTable.user_text = "" -- add program data, no initial value propertyTable.buttonEnabled = false -- button starts out disabled