Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • PIVOT-470 Rename org.apache.pivot.wtkx.WTKXSerializer to org.apache.pivot.beans.BeanSerializerBXMLSerializer
    Despite its name and inclusion in the WTK library, WTKXSerializer never had any actual dependency on WTK. In Pivot 2.0, this class has been renamed to BXMLSerializer and moved to the Core library to reflect its more general nature. It has also recieved a number of updates and improvements, discussed below.

...

  • PIVOT-568 Add support for dynamic data binding
    Pivot 1.5 and earlier supported data binding via a load/store model that maps well to client/server applications such as REST clients. However, a more dynamic model, where a property of a target element is automatically updated whenever a source value changes, is also useful in many circumstances.

    Pivot 2.0 adds support for declaratively creating such dynamic binding relationships as well as the ability to define them in code. For example, the following markup creates a binding association between a page variable named "myText" and the "text" property of a Label instance:

...

<Label text="${myText}"/>
  • . Any time the value of "myText" changes, the value of the label's "text" property is also updated

...

  • :
Code Block
xml
xml
<Label text="${myText}"/>
  • PIVOT-546 Bindable improvements
    The Bindable interface allows a caller to easily associate Java code with markup defined in BXML. It defines a single method, initialize(), that is called on the root element of a BXML document once the document has been completely loaded.

    Though Bindable was actually introduced in Pivot 1.5, it did not provide all of the information an implementing class might need. Pivot 2.0 adds arguments containing the serializer's namespace, resources, and location, to the initialize() method. Any @BXML annotations defined on the Bindable class are also processed prior to the call to initialize(). This allows the implementing class to get access to the document's namespace (i.e. page variables), the resources that were used to load it, and the location it was loaded from, to perform any necessary post-processing (for example, registering event listeners).

...

  • PIVOT-654 Simplify editor APIs
    The editor APIs for ListView, TableView, and TreeView were significantly simplified for Pivot 2.0. They now consist of one single-method interface for each component, making it much easier to implement custom editors in a Pivot application.

...

  • PIVOT-74 Add a "closeable" property to TabPane
    The TabPane component now supports user-closeable tabs.
  • PIVOT-512 Fire tooltipTriggered() event from Component
    In prior Pivot versions, it was difficult to create tooltips containing custom content. The Component class now fires a tooltipTriggered() event that applications can hook into to show a custom tooltip. The tooltip delay is now also configurable (PIVOT-563).

...

  • PIVOT-239 Create an Eclipse launcher for org.apache.pivot.wtk.Application and ScriptApplication
    Pivot now includes an Eclipse plugin to help simplify the task of creating launch configurations for Pivot applications. When the plugin is installed, any class that implements the Application interface can be automatically launched via a right-click context menu. Additionally, any BXML file that has a root element that is a subclass of Window can also be launched via right-click using the ScriptApplication launcher class included in the platform.

Complete release notes are available here.