Issue Details (XML | Word | Printable)

Key: SWINGX-837
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Critical Critical
Assignee: Karl Schaefer
Reporter: Karl Schaefer
Votes: 0
Watchers: 2

If you were logged in you would be able to see more operations.

Property Keys in SwingX Components

Created: 01/Apr/08 07:14 AM   Updated: 08/Mar/11 12:09 PM   Resolved: 08/Mar/11 12:09 PM
Component/s: Misc Component
Affects Version/s: 0.9.0
Fix Version/s: 1.6.3

Time Tracking:
Not Specified


Operating System: All
Platform: All

Issuezilla Id: 837
Participants: Karl Schaefer, kleopatra and rah003

 Description  « Hide

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.

Karl Schaefer added a comment - 08/Mar/11 12:09 PM

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.

kleopatra added a comment - 02/Sep/09 06:20 AM

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

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


rah003 added a comment - 01/Jan/09 12:51 PM

Changing type and target.

rah003 added a comment - 31/Dec/08 06:18 AM

Moving all open issues to the next version.

rah003 added a comment - 13/Sep/08 12:09 PM

Moving all open issues from 0.9.4 to the next version.

rah003 added a comment - 09/Jun/08 12:38 PM

Moving all open 0.9.3 issues to 0.9.x

kleopatra added a comment - 01/Apr/08 09:52 AM

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