Skip to content

Refactoring - Unify JavaFX custom components #207

@oasuncion

Description

@oasuncion

Tradista makes use of custom graphical components in the JavaFX part. These components are used to render Tradista objects (ex: TradistaBookComboBox).
These objects are used essentially to get the right type of item (ex: TradistaBookComboBox is a ComboBox<Book> + to have the component initialized with all the available objects (ex: a TradistaBookComboBox is initialized with all books available to the end user).
This approach works, however there is a concurrent approach implemented in Tradista: for some objects, there is no dedicated class but TradistaGUIUtil offers methods to fill these components (ex: for pricing parameter sets, there is the TradistaGUIUtil#fillPricingParameterComboBox method). For some objects (ex: indexes), both approaches exist.
We need to have a unified approach for this, one or another but not a mix of two.

The target solution is not chosen yet, one of these approaches will need to be elected and be used globally in Tradista, becoming the only solution to manage Tradista objects in JavaFX graphical components.

Additional context
Consider the web part as well in this ticket. The JSF and the JavaFX parts should use a similar approach.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions