Feature #6464
cleanup of some messy parts of the UI implementation
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
version:
History
#1 Updated by Greg Shah almost 2 years ago
We need to cleanup many parts of the UI implementation:
- The naming of these classes. Often we had early approaches where they were used for more than one widget type (e.g.
ScrollableSelectionListGuiImplonce supported selection-list as well as combo-box, but now it only supports combo-box). - The package structure. Early work was done in
ui/chui/and the later work was done inui/client/. Lots of common code is inui/chui/. - Improving encapsulation. There are too many places where we use
instanceofchecks or otherwise implement windget-specific logic outside of the widget. - Breaking some monolithic code (especially
ThinClient) into a better/cleaner approach. Using smaller classes that are focused on more specific tasks would help.