swingx
  1. swingx
  2. SWINGX-837

Property Keys in SwingX Components

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: 0.9.0
    • Fix Version/s: 1.6.3
    • Component/s: Misc Component
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      837

      Description

      JXTaskPane contains static Strings for each property that it contains. This is
      the way that JTree operates as well.

      Most Swing components do not provide property keys, but a few do. We're
      inconsistant about it in SwingX.

      We should decide to either use them or not and then have all components comply
      with that decision.

        Activity

        Hide
        kleopatra added a comment -

        1. I wouldn't see it as a defect, maybe as an enhancement
        2. there is no strict rule followed in core Swing, so whatever we decide is
        bound to be inconsistent with part of core
        3. it doesn't really matter, IMO So my suggestion is to reduce priority
        4. personally I would go for plain strings in the setters
        5. fire up a thread (my guess is that it'll draw lots of comments

        Jeanette

        Show
        kleopatra added a comment - 1. I wouldn't see it as a defect, maybe as an enhancement 2. there is no strict rule followed in core Swing, so whatever we decide is bound to be inconsistent with part of core 3. it doesn't really matter, IMO So my suggestion is to reduce priority 4. personally I would go for plain strings in the setters 5. fire up a thread (my guess is that it'll draw lots of comments Jeanette
        Hide
        rah003 added a comment -

        Moving all open 0.9.3 issues to 0.9.x

        Show
        rah003 added a comment - Moving all open 0.9.3 issues to 0.9.x
        Hide
        rah003 added a comment -

        Moving all open issues from 0.9.4 to the next version.

        Show
        rah003 added a comment - Moving all open issues from 0.9.4 to the next version.
        Hide
        rah003 added a comment -

        Moving all open issues to the next version.

        Show
        rah003 added a comment - Moving all open issues to the next version.
        Hide
        rah003 added a comment -

        Changing type and target.

        Show
        rah003 added a comment - Changing type and target.
        Hide
        kleopatra added a comment -

        what's the status of this - did we a public discussion and if so, what was the
        outcome?

        My suggestion (didn't change my mind <g>) is to close this as wontfix as there
        is no obvious best practice, IMO.

        CU
        Jeanette

        Show
        kleopatra added a comment - what's the status of this - did we a public discussion and if so, what was the outcome? My suggestion (didn't change my mind <g>) is to close this as wontfix as there is no obvious best practice, IMO. CU Jeanette
        Hide
        Karl Schaefer added a comment -

        Closing as won't fix. I don't think we should have them, but we're not going to remove the ones that already exist.

        Show
        Karl Schaefer added a comment - Closing as won't fix. I don't think we should have them, but we're not going to remove the ones that already exist.

          People

          • Assignee:
            Karl Schaefer
            Reporter:
            Karl Schaefer
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: