Following up on @ngosang's comment on #653 (the amule/amulegui GUI is very dated IMHO) — opening this as a dedicated place to scope that rather than continuing on a closed, unrelated ticket.
What's already in motion
#180 started exactly this kind of work: replacing legacy wxListCtrl usage with wxDataViewCtrl, which is native on macOS/GTK (better VoiceOver/Orca support, current-looking widgets) and at minimum visually neutral on Windows (generic fallback). Phase 1 (Preferences sidebar, #671) is merged. Phase 2 — the search-results tree — is the actual bulk of the visual "dated" impression: grouped results are drawn today with hand-rolled connector lines and circles instead of the control's native expand/collapse triangles.
Proposed immediate next step: proceed with #180 Phase 2 (search-results tree) as already discussed there — cheapest, already-agreed-direction, concrete deliverable, with before/after screenshots on all three platforms as got3nks asked for phase 1.
Other concrete candidates for this tracking issue (not scoped/started yet)
Happy to keep working through this incrementally (one contained PR per phase, like #180), starting with #180 Phase 2 once you confirm that's still the right first step.
Following up on @ngosang's comment on #653 (
the amule/amulegui GUI is very dated IMHO) — opening this as a dedicated place to scope that rather than continuing on a closed, unrelated ticket.What's already in motion
#180 started exactly this kind of work: replacing legacy
wxListCtrlusage withwxDataViewCtrl, which is native on macOS/GTK (better VoiceOver/Orca support, current-looking widgets) and at minimum visually neutral on Windows (generic fallback). Phase 1 (Preferences sidebar, #671) is merged. Phase 2 — the search-results tree — is the actual bulk of the visual "dated" impression: grouped results are drawn today with hand-rolled connector lines and circles instead of the control's native expand/collapse triangles.Proposed immediate next step: proceed with #180 Phase 2 (search-results tree) as already discussed there — cheapest, already-agreed-direction, concrete deliverable, with before/after screenshots on all three platforms as got3nks asked for phase 1.
Other concrete candidates for this tracking issue (not scoped/started yet)
connButImg,amuleDlgImagesinmuuli_wdr.cpp) are still raw raster-XPM-style C arrays, while newer work (connection-status icons, Accessibility bug report: Search results list is invisible with VoiceOver on macOS #180's sidebar) already useswxArtProvider/SVG bundles, which scale cleanly on hi-DPI. Migrating the remaining hardcoded bitmaps to the same art-provider pattern would be a self-contained, low-risk follow-up once Accessibility bug report: Search results list is invisible with VoiceOver on macOS #180 lands.muuli_wdr.cppis hand-maintained (the original wxDesigner.wdrsource is gone) and shows its age in inconsistent sizer flags across similar controls — the connect-button sizing inconsistency just fixed in feat(gui): remove the global Connect/Disconnect toolbar button #663 review is a small example of the same pattern likely recurring elsewhere.Happy to keep working through this incrementally (one contained PR per phase, like #180), starting with #180 Phase 2 once you confirm that's still the right first step.