swingx
  1. swingx
  2. SWINGX-1550

LocalizableStringValue: refactor to allow subclassing to configure the actual lookup

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.6.6
    • Component/s: Renderer
    • Labels:
      None

      Description

      currently, the lookup strategy is hard-coded in getString(...) to query the UIManager for a localized value. In different contexts, there might be other strategies - f.i. query a resource managed by an ApplicationContext (in BSAF).

      A way to support those differing contexts is to extract the actual lookup (after building the key) and let it default to looking into the UIManager. Subclasses can override to implement looking whereever they want to.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            kleopatra
            Reporter:
            kleopatra
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: