Issue 7269: UML diagram interchange: use of bounds limiting (issues) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: The use of Bounds (x, y, width, height) as layout constraints maybe acceptable for rendering diagrams, but is not very suitable for editing ones that employ other types of layout algorithms that might not necessarily use a Bounds constraint. (attributes could be laid out in their compartment using a flow layout that only considers the order of attributes in their collection to be what is relevant to the layout). Resolution: Revised Text: Actions taken: April 22, 2004: received issue Discussion: Other layout algorithm can be used to layout elements of the diagrams (like features). In this case the bounds can be ignored. But this may lead to a different layout. E.g. if the preferred font is not available on the current system it can be necessary for a readable layout. But the standard is designed to preserve the layout as it is designed by the author of the model. So if all properties are set correct the bounds of all elements (including the position of consecutive text elements, vertical or horizontal) gives an exact information to layout the diagram correctly. (Previously recommended Disposition: Resolved, no change has to be made) Based on the concerns from FTF members and the inability to develop a revised resolution within the given timeframe, this issue has been deferred and should be re-addressed in the future Diagram Interchange RTF. Disposition: Deferred End of Annotations:===== ubject: UML diagram interchange: use of bounds limiting X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Thu, 22 Apr 2004 17:46:59 -0400 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 04/22/2004 17:47:01, Serialize complete at 04/22/2004 17:47:01 The use of Bounds (x, y, width, height) as layout constraints maybe acceptable for rendering diagrams, but is not very suitable for editing ones that employ other types of layout algorithms that might not necessarily use a Bounds constraint. (attributes could be laid out in their compartment using a flow layout that only considers the order of attributes in their collection to be what is relevant to the layout). Bran Selic IBM Distinguished Engineer IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph.: (613) 591-7915 fax: (613) 599-3912 e-mail: bselic@ca.ibm.com