| 19 | * ChimeraX 1.8 |
| 20 | - Have seen a few Mac bug reports with no C stack provided by Mac crash reporter. |
| 21 | - Can tweet 1.8 release as it seems it is working fine. |
| 22 | |
| 23 | * Make distclean |
| 24 | - Greg made "make clean" not remove downloaded third-party packages (from plato archive) so if plato is down we can still build using already downloaded packages. |
| 25 | - Use "make distclean" to remove downloaded packages. |
| 26 | |
| 27 | * ChimeraX dark mode |
| 28 | - Greg has ChimeraX behaving better in operating system Dark Mode. |
| 29 | - Uses Qt 6.7 for html panels, Log, file history. |
| 30 | - Some icons are hard to see (black on transparent background), and new ones could be made. Greg will add mechanism to use a dark mode icon if one is available. |
| 31 | |
| 32 | * Python 3.12 for ChimeraX 1.9? |
| 33 | - Discussed whether to update ChimeraX to Python 3.12. |
| 34 | - Python 3.12 released October 2023 and is now at 3.12.4. |
| 35 | - Greg says Python has 3 years of support where they distribute builds with security fixes. So 3.11 from October 2022 is supported until October 2025 (3 ChimeraX releases from now). |
| 36 | - After 3 year support Python still includes security fixes for another 3 years but does not provide builds, so you have to build yourself to get those. |
| 37 | - Zach will try a Python 3.12 ChimeraX build to see how many third-party packages cause problems (not yet available for 3.12). |
| 38 | |
| 39 | * Chimera 1.18 release |
| 40 | - Chimera fails reading AlphaFold 3 mmCIF files because of a "." in some mandatory field (chain id?). |
| 41 | - Greg will make 1.18 release, no candidates, just build and release. |
| 42 | |
| 43 | * ChimeraX 1.9 roadmap |
| 44 | - Eric suggests we finally fix long atom spec parsing crashes. |
| 45 | - Greg interested in making linux flatpack use system python. |
| 46 | |
| 47 | * Linux package manager ChimeraX versions |
| 48 | - Greg would like to have ChimeraX distributed through standard Ubuntu package repository. |
| 49 | - Would require agreeing to license in a different way, e.g. on ChimeraX startup. |
| 50 | - Flatpaks also have repository want to update automatically which presents licensing issues. |
| 51 | |
| 52 | * Scan web logs for ChimeraX use statistics |
| 53 | - Greg suggests we try scanning web logs for statistics on active number of ChimeraX users for future grant applications. |