feedback on the "modernize your own app" instructions

[nedtwigg]

I think these instructions are not enough to get started: https://github.com/equodev/swt-evolve?tab=readme-ov-file#modernize-your-own-app

I've tried out swt-evolve on my production app and I've also tinkered with it on an open source library.

Here's the sequence which would have been helpful to me, fwiw. Maybe you've got other changes coming up, just wanted to share my experience with it:

• move your app to SWT 4.34
• add the appropriate dev.equo:swt-evolve jars to the classpath
  • the maven url is <blah>, the platform naming convention is <blah>
    • not a big deal, but this would be a tiny bit easier if you matched the swt naming conventions for operating systems (win32 instead of windows, etc)
  • here are examples a, b, and c
• before any SWT code has a chance to get called, call dev.equo.swt.Config.defaultToEclipse().
  • this will be the "oldschool-est" it can be
  • in this mode, the only things swt-evolve is changing are ?
    • seems like Canvas gets changed still? Anything else?
• now try dev.equo.swt.Config.useEquo(Button.class) and you can see that the buttons are modernized
• modernize any control you want, or leave out the .defaultToEclipse() call and will instead default to equo for everything.

Btw, my initial impressions (as of 0.10.0) are that this is going really well, and I especially like your Config.useEquo design. Very excited to see where this goes!