Next steps

[ajkessel]

I’ve been happy to see this module revived as I had given up hope on the original customtkinter.

A few thoughts/suggestions for next steps:

• Make it easier to find the pip repository; link https://pypi.org/project/custom2kinter/ from README.md
• Establish a regular pypi push schedule — it will be easier to test and get feedback if there are stable releases that can be installed with a normal pip (not requiring github URL)
• Fork documentation and set up new link for https://customtkinter.tomschimansky.com/documentation/ . I’d be happy to work on documentation to keep up with new features. Is documentation site also MIT licensed? I’m not seeing a license at first glance.
• More robust smoke testing. Are you interested in a fully interactive cross-platform smoke testing facility? I understand you don’t have a MacOS box handy for testing, but this could be done with CI/CD on GH or I could run smoke tests locally on all three target architectures (Windows, Mac, Linux). I envision the smoke testing would interactively operate all the widgets and also generate screenshots so you can see how your changes appear on all platforms even if you aren’t testing them locally yourself.

[FedericoSpada]

Hi,

• My plan is to add a few more new widgets, and then I'll publish v6.0.0 on PyPI.
• Regarding the documentation, my idea was to recreate it from scratch somewhere else. I've seen other libraries using ReadTheDocs. If you want to have a look at it, I would be very grateful.
• I'm open to any help I can get, especially with testing, since it's not my cup of tea.

[ajkessel]

OK, great, I'll do some noodling on the smoke test aspect. This seems especially important given the quirks with different OS and Python versions.