[SWINGX-837] Property Keys in SwingX Components Created: 01/Apr/08  Updated: 08/Mar/11  Resolved: 08/Mar/11

Status: Resolved
Project: swingx
Component/s: Misc Component
Affects Version/s: 0.9.0
Fix Version/s: 1.6.3

Type: Improvement Priority: Critical
Reporter: Karl Schaefer Assignee: Karl Schaefer
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 837


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.

Comment by kleopatra [ 01/Apr/08 ]

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


Comment by rah003 [ 09/Jun/08 ]

Moving all open 0.9.3 issues to 0.9.x

Comment by rah003 [ 13/Sep/08 ]

Moving all open issues from 0.9.4 to the next version.

Comment by rah003 [ 31/Dec/08 ]

Moving all open issues to the next version.

Comment by rah003 [ 01/Jan/09 ]

Changing type and target.

Comment by kleopatra [ 02/Sep/09 ]

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.


Comment by Karl Schaefer [ 08/Mar/11 ]

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.

Generated at Sat Jul 04 05:10:17 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.