Note: This isn't set in stone and may not even happen at all, it's just an idea so keep that in mind.
Switch from Eto.Forms to using Avalonia.
Why?
Pros
Resizing controls in Avalonia is miles easier in comparison to Eto, which puts hard-coded limits for loads of the built-in controls.
Moving controls around should be a lot easier, where as with Eto it's an absolute pain currently. For example, currently you can't stack controls next to the Date and Time text inside of Vival without "cheating" the behavior as seen in Vival Macbar.
Proper MinSize, MaxSize, MinHeight and MaxHeight properties that actually work inside of tiling window managers.
Less need of while (true) { } (Update) loops, leading to better performance.
Better font customization
Easier merging with changes from main
Downs
Larger memory footprint
Currently: 94MB Average
W.I.P: 140MB+ Average
While this isn't really an issue on modern systems, it's still there and is one tradeoff.
Your custom configuration (be it small or large) will have to be remade, some stuff may end up not working at all and requiring you to write the stuff by hand yourself (this will most likely be the mouse callbacks on labels at the start).
Note: This isn't set in stone and may not even happen at all, it's just an idea so keep that in mind.
Switch from
Eto.Forms
to usingAvalonia
.Why?
Pros
MinSize
,MaxSize
,MinHeight
andMaxHeight
properties that actually work inside of tiling window managers.while (true) { }
(Update) loops, leading to better performance.main
Downs