Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 195326

Summary:	refactor abstract task editor to not use ScrolledForm
Product:	z_Archived	Reporter:	Eugene Kuleshov <ekuleshov>
Component:	Mylyn	Assignee:	Robert Elves <robert.elves>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Eugene Kuleshov

2007-07-03 20:34:35 EDT

It seems like ScrolledForm has number of issues that makes it hard to deal with nested composites that need to fit to the width of the editor or use layout like RowLayout (which wrap component automatically to fit to width). Probably it would be a good idea to instead use regular Form with the nested ScrolledComposite, which doesn't have such issues.

Comment 1 Mik Kersten

2007-07-06 20:45:59 EDT

Rob: consider this when working on task editor layout.

Comment 2 Eugene Kuleshov

2007-07-07 01:06:22 EDT

Please increase priority of this one. It has huge impact on JIRA editor layout and also practically main obstacle to make task editors to shrink to the narrow width (i.e. can't use rowlayout for header section).

Comment 3 Robert Elves

2007-07-17 14:14:18 EDT

Our editor pages are based on ManagedForm which only uses ScrolledForm so it doesn't appear that we can avoid this.

Comment 4 Eugene Kuleshov

2007-07-17 14:45:45 EDT

Rob, please reconsider. Scrollable composite is a major showstopper for many UI issues.

Comment 5 Robert Elves

2007-07-18 20:44:43 EDT

Can you give me more details as to what problems this is causing... perhaps we can come up with another work around?