eclipse-windowbuilder / eclipse-windowbuilder/windowbuilder
Harmonize TableWrapLayout2 and TableWrapData2 with Forms classes
- Dominant language
- Java
- Stars
- 97
- Forks
- 34
- Avg merge
- 21h 38m
- Merged PRs (30d)
- 29
Description
Both the [TableWrapLayout2](https://github.com/eclipse-windowbuilder/windowbuilder/blob/master/org.eclipse.wb.rcp/src/org/eclipse/wb/internal/rcp/model/forms/layout/table/TableWrapLayout2.java) and [TableWrapData2](https://github.com/eclipse-windowbuilder/windowbuilder/blob/master/org.eclipse.wb.rcp/src/org/eclipse/wb/internal/rcp/model/forms/layout/table/TableWrapData2.java) are pretty old copies of the Forms classes which we have extended to store additional information during the layout.
We should separate the designer information from the layout algorithm to make sure that our implementation matches the actual implementation.
Contributor guide
Research direction
Start by comparing TableWrapLayout2.java and TableWrapData2.java with the corresponding Forms classes, then identify which information is used by the layout algorithm and which is designer-specific. Define the separation boundary before changing the implementation, and verify that layout behavior matches the actual Forms implementation while designer information remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100