JDK-4337186 : RFE: ComponentOrientation management
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.2.0,1.3.0,1.4.0
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic,solaris_2.5,windows_98
  • CPU: generic,x86
  • Submitted: 2000-05-10
  • Updated: 2017-05-23
Related Reports
Duplicate :  
Duplicate :  
Relates :  
With the bulk of the Swing components paying attention to their ComponentOrientation property, we now need two features to make it easier to manage the ComponentOrientation settings of an entire hierarchy of components.

1) The default setting of a component's ComponentOrientation setting should be driven from the user's locale choice.

2) It should be easy to set entire hierarchies of components to a consistent ComponentOrientation setting.

These two additional features will make ComponentOrientation a transparent (for free) feature for most programs.

Name: yyT116575			Date: 05/02/2001

java version "1.3.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0_02)
Java HotSpot(TM) Client VM (build 1.3.0_02, mixed mode)

Although the documentation for ComponentOrientation references "TR" (top-to- bottom, right-to-left) and "TL" (top-to-bottom, left-to-right) orientation, it is not possible to construct a ComponentOrientation instance that reflects these rules.  The constructor is private, and all the static fields that return an instance have the horizontal bit on.

Also, the lack of a public constructor or factory method makes it difficult to use this class with XML data binding, since these implementation often require a constructor or factory method.

Finally, although Japanese, Chinese, Korean and Mongolian are listed as top-to-bottom scripts in the ComponentOrientation documentation, isHorizontal() returns true for all locale orientations.  Either the ComponentOrientation documentation should be corrected or the locale data.
(Review ID: 123636)

EVALUATION This rfe is a restatement of the problems described by 4300548 and 4229173. It will be easier to track this single rfe than those two seperate ones. I am therefore closing those as duplicates. brian.beck@Eng 2000-05-10