Skip to main content

Custom Control Design Definition Tricks

I think by now many people are aware of the Design Definition you can set when creating a custom control. Here is a quick refresher if you are not. A design definition simply replaces what you see when you drop the control on an xpage. By default, it shows whatever is in your control, but this property can be used to replace that with:
  • documentation about how to use the control, for example what custom properties mean or other requirements such as using a data source named "document1"
  • A visual short-hand, for example a control could just show <Header Control> instead of everything inside. This is great for minimizing clutter in the designer and it can also speed up the loading/rendering of the xpage in designer.
  • An interactive tool that allows you to drop additional controls inside
 There are a couple of advanced features that can be tricky to figure out unless someone shows you. Here is one:


Setting label text dynamically

If you drop a label and an edit box into a custom control, you can set what they look like through the design definition. For example you could display it this way:

<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
    <xp:table>
      <xp:tr>
        <xp:td>fieldLabel</xp:td>
    <xp:td>
          <xp:inputText
            value="dataSource"
          >
          </xp:inputText>
        </xp:td>
      </xp:tr>
    </xp:table>
</xp:view>
The problem with doing it this way is once you drop a few of these controls on your document, you can't tell one from another without looking at the custom properties of each. There is another way of doing this using JSP expressions. By changing the definition a little bit, we can dynamically set the display text of the custom control so that we can identify one instance of a control from another:

<?xml version="1.0" encoding="UTF-8"?>
<xp:view xmlns:xp="http://www.ibm.com/xsp/core">
    <xp:table>
      <xp:tr>
        <xp:td>
          <%=this.labelText || 'Label'%>
        </xp:td>
    <xp:td>
          <xp:inputText
            value="<%=this.bindTo || 'DataSource'%>"
          >
          </xp:inputText>
        </xp:td>
      </xp:tr>
    </xp:table>
</xp:view>
I'd like to find a way to edit these properties directly on the custom control at some point, just to make this a little easier and more fool-proof, but for now I'm satisfied with just being able to do this at all.

One caveat I have found is that this doesn't seem to work when you are using property groups. When I tried to do something like value="<%=this.input1.bindTo || 'DataSource'%>" designer kept complaining that input1 is null.

Comments

Popular posts from this blog

XPages Application Framework (Part 1?)

Note: I changed projects and priorities after my last POI article, resulting in a long hiatus. I anticipate using that framework on my current project and will likely refine and complete my related article series. For the past several months, I've been fortunate enough to lead a project overhaul from traditional Domino Webapp to XPages. I had a few goals in mind, but the top three were integrating Bootstrap, embracing MVC principles, and eliminating all SSJS . I imagine the motivation for Bootstrap integration is self-explanatory. There is an OpenNTF project out there called Bootstrap4XPages. I didn't use that for a number of reasons - the main being a policy in the current environment. But you may ask yourself (if you didn't follow that link), why so much hatred for SSJS? I have a litany of reasons. It impacts readability of the XPage source; it hurts maintainability when logic is scattered across dozens of XPages, custom controls, and script libraries; it mixes log...

Killing SSJS - Passing a parameter using Expression Language - Part 2

In part 1, I showed how you can expand the DataObject implementation to allow you to pass a parameter to a method and return the result. It's not a perfectly elegant solution, and it has some limitations, but it's a very solid technique and not at all difficult to implement or maintain. But I kept running into roadblocks. What if I have to compute part of the expression? What if I have to get a value based on another parameterized getter? You can't compute part of an EL expression in your EL. So after some research and experimentation, I created the GetMap. This isn't a new concept - it was developed for JSF 1.1 (which is what XPages is built on) but the rest of the world has moved on to JSF 2.0 and so some of these older techniques can be a little tricky to unearth since this hasn't been an issue in the JSF world for years.

Rows per page selection: Part 2

I was asked to create a control that would allow users to select the number of rows per page in a view/repeat control (the application uses both). It seemed simple at first, but I ran into a few issues that I thought I'd share the solutions to. Problem 2: When the page refreshed, the combobox value always reverted back to the default It turns out that the Integer value stored in the viewScope doesn't get run through the converter back to a string before being compared to options. I needed a way to calculate the option values so that they would be Integers. This is also not the first time I've run into issues where I need a value to be of a different type, and I see questions like this on StackOverflow from time to time. I attempted a few minor things before I realized I needed to break out my old stand-by, the GetMap . The GetMap is just a fake Map implementation that takes the key and transforms it or uses it to look up some other value. In this case, we are doing the f...