Package swingtree

Class UIForList<E,L extends JList<E>>

java.lang.Object
swingtree.UIForAnySwing<UIForList<E,L>,L>
swingtree.UIForList<E,L>
Type Parameters:
L - The type of the JList instance which will be managed by this builder.
public final class UIForList<E,L extends JList<E>> extends UIForAnySwing<UIForList<E,L>,L>
A SwingTree builder node designed for configuring JList instances.

Please take a look at the living swing-tree documentation where you can browse a large collection of examples demonstrating how to use the API of this class.

  • Method Details

    • _state

      protected swingtree.BuilderState<L> _state()
      Returns the state of the builder, which is a container for the wrapped component as well as it's type and current EventProcessor.
      Returns:
      The state of the builder.

    • _newBuilderWithState

      protected UIForList<E,L> _newBuilderWithState(swingtree.BuilderState<L> newState)
      An internal wither method which creates a new builder instance with the provided BuilderState stored inside it.
      Parameters:
      newState - The new state which should be stored inside the new builder instance.
      Returns:
      A new builder instance with the provided state stored inside it.

    • withEntries

      public final UIForList<E,L> withEntries(List<E> entries)
      Takes the provided list of entry objects and sets them as JList data.
      Parameters:
      entries - The list of entries to set as data.
      Returns:
      This instance of the builder node.

    • withEntries

      @SafeVarargs public final UIForList<E,L> withEntries(E... entries)
      Takes the provided array of entry objects and sets them as JList data.
      Parameters:
      entries - The array of entries to set as data.
      Returns:
      This instance of the builder node.

    • withEntries

      public final UIForList<E,L> withEntries(sprouts.Vals<E> entries)
      Takes the provided observable property list of entries in the form of a Vals object and uses them as a basis for modelling the JList data. If the Vals object changes, the JList data will be updated accordingly, and vice versa.
      Parameters:
      entries - The Vals of entries to set as data model.
      Returns:
      This instance of the builder node to allow for builder-style fluent method chaining.

    • withSelection

      public final UIForList<E,L> withSelection(sprouts.Var<E> selection)
      Takes an observable property in the form of a Var object and uses it as a basis for modelling the JList selection. If the Var object changes, the JList selection will be updated accordingly, and vice versa. If you do not want this relationship to be bidirectional, use withSelection(Val) instead.
      Parameters:
      selection - The Var of entries to set as selection model.
      Returns:
      This instance of the builder node to allow for fluent method chaining.

    • withSelection

      public final UIForList<E,L> withSelection(sprouts.Val<E> selection)
      Takes an observable read-only property in the form of a Val object and uses it as a basis for modelling the JList selection. If the Val object changes, the JList selection will be updated accordingly. However, if the JList selection changes due to user interaction, the Val object will not be updated.
      Parameters:
      selection - The Val of entries to set as selection model.
      Returns:
      This instance of the builder node to allow for fluent method chaining.

    • withRenderComponent

      public final UIForList<E,L> withRenderComponent(ListEntryRenderer<E,L> renderer)
      The ListEntryRenderer passed to this method is a functional interface receiving a ListEntryDelegate instance and returns a JComponent, which is used to render each entry of the JList instance.
      A typical usage of this method would look like this: 
      
   listOf(vm.colors())
   .withRenderComponent( it -> new Component() {
     {@literal @}Override
     public void paint(Graphics g) {
       g.setColor(it.entry().orElse(Color.PINK));
       g.fillRect(0,0,getWidth(),getHeight());
     }
   })

      In this example, a new JList is created for the observable property list of colors, which is provided by the vm.colors() method. The entries of said list are individually exposed specified renderer lambda expression, which return a JComponent instance that is used by the JList to render each entry. In this case a colored rectangle is rendered for each entry.

      Parameters:
      renderer - The ListEntryRenderer that will be used to supply JComponents responsible for rendering each entry of the JList instance.
      Returns:
      This instance of the builder node to allow for fluent method chaining.

    • onSelection

      public final UIForList<E,L> onSelection(sprouts.Action<ComponentDelegate<JList<E>,ListSelectionEvent>> action)
      Adds an Action event handler to the underlying JList through a ListSelectionListener, which will be called when a list selection has been made. {see JList#addListSelectionListener(ListSelectionListener)}.
      Parameters:
      action - The Action that will be notified.
      Returns:
      This very instance, which enables builder-style method chaining.

    • withCellRenderer

      public final UIForList<E,L> withCellRenderer(ListCellRenderer<E> renderer)
      Sets the ListCellRenderer for the JList, which renders the list items by supplying a custom component for each item through the ListCellRenderer.getListCellRendererComponent(JList, Object, int, boolean, boolean) method.

      Parameters:
      renderer - The ListCellRenderer that will be used to paint each cell in the list.
      Returns:
      This very instance, which enables builder-style method chaining.

    • withRenderer

      public final <V extends E> UIForList<E,L> withRenderer(Configurator<RenderBuilder<L,V>> renderBuilder)
      Use this to build a list cell renderer for various item types by defining a renderer for each type or using Object as a common type using the fluent builder API exposed to the Configurator lambda function passed to this method.
      A typical usage may look something like this: 
      
  UI.list(new Object[]{":-)", 42L, 'ยง'})
  .withRenderer( it -> it
      .when(String.class).asText( cell -> "String: "+cell.getValue() )
      .when(Character.class).asText( cell -> "Char: "+cell.getValue() )
      .when(Number.class).asText( cell -> "Number: "+cell.getValue() )
  );
      Note that a similar API is also available for the JComboBox and JTable components, see UIForCombo.withRenderer(Configurator), UIForTable.withRenderer(Configurator) and UIForTable.withRendererForColumn(int, Configurator) for more information.
      Type Parameters:
      V - The type of the value that is being rendered in this combo box.
      Parameters:
      renderBuilder - A lambda function that configures the renderer for this combo box.
      Returns:
      This combo box instance for further configuration.

    • getType

      public final Class<L> getType()
      The type class of the component managed by this builder. See documentation for method "build" for more information.
      Returns:
      The type class of the component managed by this builder.

    • getComponent

      @Deprecated public final L getComponent()
      Deprecated.
      Use get(Class) instead.
      The component managed by this builder.
      Returns:
      The component managed by this builder.
      Throws:
      IllegalStateException - if this method is called from a thread other than the EDT and this UI is configured to be decoupled from the application thread. See UIFactoryMethods.use(EventProcessor, Supplier).

    • component

      @Deprecated public final OptionalUI<L> component()
      Deprecated.
      Use get(Class) instead.
      The optional component managed by this builder.
      Returns:
      An OptionalUI wrapping a component or null. This optional will throw an exception if the application has an application thread (see UIFactoryMethods.use(EventProcessor, Supplier)) and this method is called from a thread other than the EDT.

    • peek

      public final UIForList<E,L> peek(Peeker<L> action)
      Use this if you wish to access the component wrapped by this builder directly. This is useful for more fine-grained control, like for example calling methods like "setName", "setTitle", and so on...
      This method accepts a lambda to which the component wrapped by this builder will be supplied. The lambda can then call said methods or perform other tasks which might be relevant to the component while also not breaking the benefits of nesting and method chaining provided by this class...
      The below example shows how this method allows for more fine-grained control over the wrapped component: 
      
      UI.panel()
      peek( panel -> panel.setDebugGraphicsOptions(true) );


      Parameters:
      action - A Consumer lambda which simply returned the wrapped JComponent type for interacting it.
      Returns:
      This very instance, which enables builder-style method chaining.

    • applyIf

      public final UIForList<E,L> applyIf(boolean condition, Consumer<UIForList<E,L>> building)
      Use this to only build a certain part of the UI if the provided boolean condition is true. Which is to say, if the condition is false, then the second lambda is ignored, if on the other hand the condition is true, then the second lambda is executed with the current builder instance passed to it as a parameter. Inside the lambda, one can then continue building the UI while also not breaking the benefits of nesting and method chaining provided by this builder...

      This is in essence a more advanced version of apply(Consumer).
      Here a simple usage example: 

      
    UI.panel()
    .applyIf( userIsLoggedIn, ui -> ui
      .add( UI.label("Welcome back!") )
      .add( UI.button("Logout")).onClick( () -> logout() )
      .add( UI.button("Settings")).onClick( () -> showSettings() )
    )
    .applyIf( !userIsLoggedIn, ui -> ui
      .add( UI.label("Please login to continue.") )
      .add( UI.button("Login")).onClick( () -> login() );
    );
      Here we use theis method to build a panel with different content depending on whether the user is logged in or not.

      Parameters:
      condition - The truth value which determines if the second consumer lambda is executed or not.
      building - A Consumer lambda which simply consumes this builder instance.
      Returns:
      This very instance, which enables builder-style method chaining.

    • applyIfPresent

      public final UIForList<E,L> applyIfPresent(Optional<Consumer<UIForList<E,L>>> building)
      Allows you to build declarative UI conditionally, meaning that the UI is only built if the provided Optional value is present. If the value is not present, meaning it is null, then the second lambda (containing UI declarations relevant to the value) is simply ignored.

      Consider the following example: 

      
 // In your view model:
 public Optional<MySubModel> getM() {
   return Optional.ofNullable(this.model);
 }

 // In your view:
 UI.panel()
 .add(UI.label("Maybe Sub Model:"))
 .applyIfPresent(vm.getM().map(m->ui->ui
   .add(UI.label("Hello Sub Model!"))
   .add(UI.label("A:")
   .add(UI.textField(m.getA()))
   .add(UI.label("B:"))
   .add(UI.textField(m.getB()))
   // ...
 ))
 .add(UI.label("Some other stuff..."));
      The applyIfPresent method takes an Optional<Consumer<I>> as parameter, where I is the type of the UI builder. This allows you to map the optional value to a consumer which is only executed if the value is present. If the optional value is present, the consumer is executed with the current UI builder as a parameter, which allows you to continue building the UI as usual.
      The m->ui->ui may look a bit confusing at first, but it is simply a lambda expression which takes the optional value and returns a consumer (ui->ui... ) which takes the UI builder as a parameter.
      This is in essence a more advanced Optional centric version of applyIf(boolean, Consumer) and apply(Consumer).
      Parameters:
      building - An optional consumer lambda which simply consumes this builder node.
      Returns:
      This very instance, which enables builder-style method chaining.

    • apply

      public final UIForList<E,L> apply(Consumer<UIForList<E,L>> building)
      Use this to continue building UI inside a provided lambda if you need to introduce some imperative code in between the building process.
      This is especially useful for when you need to build UI based on loops. The current builder instance will simply be supplied to the provided Consumer lambda. Inside the supplied lambda, you can then continue building the UI while also not breaking the benefits of nesting and method chaining, effectively preserving the declarative nature of the builder.

      Here is a simple example of how this method can be used to build a panel with a variable amount of images displayed in a grid: 
      
      UI.panel("wrap 3")
      .apply( ui -> {
          for ( String path : imagePaths )
              ui.add( UI.label(UI.icon(path)) );
      });


      Here is another example of how this method can be used to build a panel with a variable amount of buttons displayed in a grid: 
      
    UI.panel("wrap 4")
    .apply( ui -> {
      for ( int i = 0; i < numOfButtons; i++ )
          ui.add( UI.button("Button " + i)
          .onClick( () -> {...} );
    });


      Parameters:
      building - A Consumer lambda which simply consumes this builder instance.
      Returns:
      This very instance, which enables builder-style method chaining.

    • get

      public final L get(Class<L> type)
      This method completes the building process for the wrapped JComponent type by returning it. However, it also expects the user to pass the class of the JComponent wrapped by this builder! This is not out of necessity but for better readability when using the builder in more extensive ways where the beginning and end of the method chaining and nesting of the builder does not fit on one screen.
      In such cases the expression ".get(MyJComponent.class)" helps to identify which type of JComponent is currently being built on a given nesting layer...

      Here is a simple example that demonstrates this technique using a JPanel and a JMenuBar: 
      
      UI.panel()
      .add(
          UI.menuBar()
          .add( UI.menu("File") )
          .add( UI.menuItem("Open") )
          .add( UI.menuItem("Save") )
          // ...
          .add( UI.menuItem("Exit") )
          .get(JMenuBar.class)
      )
      .add( UI.button("Click me!") )
      .get(JPanel.class);
      As you can see, the expression ".get(JMenuBar.class)" as well as the expression ".get(JPanel.class)" at the end of the builder chain help to identify which type of JComponent is currently being built and returned.
      Parameters:
      type - The type class of the component which this builder wraps.
      Returns:
      The result of the building process, namely: a type of JComponent.

    • add

      @SafeVarargs public final UIForList<E,L> add(JComponent... components)
      This builder class expects its implementations to be builder types for anything which can be built in a nested tree-like structure. Implementations of this abstract method ought to enable support for nested building.

      Parameters:
      components - An array of component instances which ought to be added to the wrapped component type.
      Returns:
      This very instance, which enables builder-style method chaining.

    • add

      public final <T extends JComponent> UIForList<E,L> add(UIForAnySwing<?,T> builder)
      Uses the supplied builder to build its component and then add it to the component that is being built by this builder instance. This directly allows you to nest your builder based UI declarations in an HTML-like fashion.
      Type Parameters:
      T - The type of the JComponent which is wrapped by the provided builder.
      Parameters:
      builder - A builder for another JComponent instance which ought to be added to the wrapped component type.
      Returns:
      This very instance, which enables builder-style method chaining.

    • add

      @SafeVarargs public final <B extends swingtree.UIForAnything<?, ?, JComponent>> UIForList<E,L> add(B... builders)
      This method provides the same functionality as the other "add" methods. However, it bypasses the necessity to call the "get" method by calling it internally for you.
      This helps to improve readability, especially when the degree of nesting is very low.
      Type Parameters:
      B - The type of the builder instances which are used to configure the components that will be added to the component wrapped by this builder.
      Parameters:
      builders - An array of builder instances whose JComponents ought to be added to the one wrapped by this builder.
      Returns:
      This very instance, which enables builder-style method chaining.

    • add

      public final UIForList<E,L> add(List<JComponent> components)
      This builder class expects its implementations to be builder types for anything which can be built in a nested tree-like structure. Implementations of this abstract method ought to enable support for nested building.

      Parameters:
      components - A list of component instances which ought to be added to the wrapped component type.
      Returns:
      This very instance, which enables builder-style method chaining.

    • _addBuildersTo

      @SafeVarargs protected final <B extends swingtree.UIForAnything<?, ?, JComponent>> void _addBuildersTo(L thisComponent, B... builders)

    • _addComponentsTo

      @SafeVarargs protected final void _addComponentsTo(L thisComponent, JComponent... componentsToBeAdded)

    • _addBuilderTo

      protected final void _addBuilderTo(L thisComponent, swingtree.UIForAnything<?,?,?> builder, @Nullable Object conf)

    • _with

      protected final swingtree.UIForAnything<UIForList<E,L>,L,JComponent> _with(Consumer<L> componentMutator)
      Creates a new builder with the provided component mutation applied to the wrapped component.
      Note that the SwingTree builders are immutable, which means that this method does not mutate the current builder instance, but instead creates a new builder instance with a new BuilderState which contains the provided component mutation (see BuilderState.withMutator(Consumer)). Also see _newBuilderWithState(BuilderState).
      Parameters:
      componentMutator - A consumer lambda which receives the wrapped component and is then used to apply some builder action to it.
      Returns:
      A new builder instance with the provided component mutation applied to the wrapped component.

    • _runInUI

      protected final void _runInUI(Runnable action)
      A convenient shortcut to the EventProcessor.registerUIEvent(Runnable) method to the current EventProcessor attached to the current BuilderState. In practice, this method will ultimately just delegate tasks to the AWT Event Dispatch Thread (EDT).
      Parameters:
      action - An action which should be executed by the UI thread, which is determined by implementations of the EventProcessor, also see UIFactoryMethods.use(EventProcessor, Supplier).
      Usually the UI thread is AWT's Event Dispatch Thread (EDT).

    • _runInApp

      protected final void _runInApp(Runnable action)
      A convenient delegate to the EventProcessor.registerAppEvent(Runnable) method, which allows you to execute an action on the current application thread. To configure the current EventProcessor see UIFactoryMethods.use(EventProcessor, Supplier) or the underlying SwingTree.setEventProcessor(EventProcessor) method.
      Parameters:
      action - An action which should be executed by the application thread, which is determined by implementations of the current EventProcessor, also see UIFactoryMethods.use(EventProcessor, Supplier).

    • _runInApp

      protected final <T> void _runInApp(T value, Consumer<T> action)
      A convenient delegate to the EventProcessor.registerAppEvent(Runnable) method, which allows you to execute an action on the current application thread. Which thread executes these tasks is determined by the current EventProcessor. Usually this is the EventProcessor.COUPLED or EventProcessor.COUPLED_STRICT event processor.
      Type Parameters:
      T - The type of the value.
      Parameters:
      value - A value which should be captured and then passed to the provided action on the current application thread (see EventProcessor and UIFactoryMethods.use(EventProcessor, Supplier)).
      action - A consumer lambda which is executed by the application thread and receives the provided value.

    • _onShow

      protected final <T> void _onShow(sprouts.Val<T> val, L thisComponent, BiConsumer<L,T> displayAction)
      Use this to register a state change listener for the provided property which will be executed by the UI thread (see EventProcessor).
      Type Parameters:
      T - The type of the item wrapped by the provided property.
      Parameters:
      val - A property whose state changes should be listened to on the UI thread.
      thisComponent - The component which is wrapped by this builder.
      displayAction - A consumer lambda receiving the provided value and is then executed by the UI thread.

    • _withOnShow

      protected final <T> swingtree.UIForAnything<UIForList<E,L>,L,JComponent> _withOnShow(sprouts.Val<T> val, BiConsumer<L,T> displayAction)

    • _onShow

      protected final <T> void _onShow(sprouts.Vals<T> vals, L c, BiConsumer<L,sprouts.ValsDelegate<T>> displayAction)
      Use this to register a state change listener for the provided property list which will be executed by the UI thread (see EventProcessor).
      Type Parameters:
      T - The type of the items wrapped by the provided property list.
      Parameters:
      vals - A property list whose state changes should be listened to on the UI thread.
      c - The component which is wrapped by this builder.
      displayAction - A consumer lambda receiving the action delegate and is then executed by the UI thread.

    • _withOnShow

      protected final <T> swingtree.UIForAnything<UIForList<E,L>,L,JComponent> _withOnShow(sprouts.Vals<T> vals, BiConsumer<L,sprouts.ValsDelegate<T>> displayAction)

    • _this

      protected final UIForList<E,L> _this()
      Exposes the this-pointer of the builder instance cast to the I type parameter of the builder class.
      This is done to reduce the amount of type casting and warnings in the codebase.
      Returns:
      The builder instance itself based on the type parameter <I>.

    • _disposeState

      protected final void _disposeState()
      This method is used to dispose of the state of the builder, which means that the builder state disposes of its reference to either the wrapped component or the wrapped component or the composite of component factories which are used to build the wrapped component eagerly each time the wrapped component is accessed.
      This is important to avoid memory leaks, as a component is typically part of a tree of components, and if one component is not garbage collected, then the whole tree is not garbage collected.

    • hashCode

      public final int hashCode()
      Overrides:
      hashCode in class Object

    • equals

      public final boolean equals(Object obj)
      Overrides:
      equals in class Object

    • toString

      public final String toString()
      Overrides:
      toString in class Object